|
Problem IC73053
|
Status: Closed |
DROP AND CALL PROCEDURE STATEMENTS RUNNING CONCURRENTLY MAY DEADLOCK |
| product: |
DB2 FOR LUW / DB2FORLUW / 950 - DB2 |
| Problem description: |
While having two or more connections to the database if an
attempt is made to drop a procedure, while another connection is
calling or creating a procedure with the same name, though in a
different schema, a deadlock may occur. This is to complete
previous fix. |
| Problem Summary: |
****************************************************************
* USERS AFFECTED: *
* All DB2 for Linux, Unix and Windows Version 9.5 GA through *
* Fix Pack 7 servers where concurrent create/drop stored *
* procedures are running. *
****************************************************************
* PROBLEM DESCRIPTION: *
* Creating and dropping SQL procedures with the same name may *
* hit deadlocks. The internal catalog access/locking strategy *
* causes these issues. *
****************************************************************
* RECOMMENDATION: *
* Update your instance to DB2 Version 9.5 Fix Pack 8 or avoid *
* creating and dropping SQL procedures concurrently. *
**************************************************************** |
| Local Fix: |
Avoid "drop and create procedure with same name" at same time. |
| available fix packs: |
DB2 Version 9.5 Fix Pack 8 for Linux, UNIX, and Windows
DB2 Version 9.5 Fix Pack 9 for Linux, UNIX, and Windows
DB2 Version 9.5 Fix Pack 10 for Linux, UNIX, and Windows
|
| Solution |
Problem is first fixed in DB2 Version 9.5 Fix Pack 8 and all
subsequent Fix Packs. |
| Workaround |
not known / see Local fix |
| BUG-Tracking |
forerunner : APAR is sysrouted TO one or more of the following: IC73327 IC73328
follow-up : |
| Timestamps |
Date - problem reported :
Date - problem closed :
Date - last modified :
| 06.12.2010
04.08.2011
04.08.2011 |
| Problem solved at the following versions (IBM BugInfos) |
9.5.FP8
|
| Problem solved according to the fixlist(s) of the following version(s) |
| 9.5.0.8
|
 |
