|
Problem IC76237
|
Status: Closed |
CREATE PROCEDURE MAY DEADLOCK WITH CREATE PROCEDURE WITH DIFFERENT BUT SIMILAR PROCEDURE NAME |
| product: |
DB2 FOR LUW / DB2FORLUW / 970 - DB2 |
| Problem description: |
CREATE PROCEDURE may deadlock with CREATE PROCEDURE with
different but similar procedure name.
Deadlock can happen between locks acquired in the catalog cache
and locks acquired for the SYSIBM.SYSROUTINES catalog table.
User can find these associated locks and tables involved in the
deadlock from the deadlock event monitor outputs:
Participant No 2 requesting lock
----------------------------------
Lock Name : 0x0200000000000000E00FE28043
Lock wait start time : 2011-02-14-09.11.10.819404
Lock wait end time : 2011-02-14-09.11.19.065928
Lock Type : CATALOG
Lock Specifics : loadingID:00000000,loadingBytes:00000000
80E20FE0
Lock Attributes : 00000000
Lock mode requested : Exclusive
Lock mode held : Exclusive
Lock Count : 255
Lock Hold Count : 0
Lock rrIID : 0
Lock Status : Waiting
Lock release flags : 40000000
Tablespace TID :
Tablespace Name :
Table FID :
Table Schema :
Table Name :
Participant No 1 requesting lock
----------------------------------
Lock Name : 0x0000160017004C000000000052
Lock wait start time : 2011-02-14-09.11.10.852327
Lock wait end time : 2011-02-14-09.11.19.065928
Lock Type : ROW
Lock Specifics : ROWID=23,DATA_PARTITION_ID=0,PAGEID=76
Lock Attributes : 00000000
Lock mode requested : Update
Lock mode held : Exclusive
Lock Count : 1
Lock Hold Count : 0
Lock rrIID : 0
Lock Status : Waiting
Lock release flags : 40000000
Tablespace TID : 0
Tablespace Name : SYSCATSPACE
Table FID : 22
Table Schema : SYSIBM
Table Name : SYSROUTINES |
| Problem Summary: |
****************************************************************
* USERS AFFECTED: *
* CREATE PROCEDURE may deadlock with CREATE PROCEDURE with *
* different but similar procedure name *
****************************************************************
* PROBLEM DESCRIPTION: *
* CREATE PROCEDURE may deadlock with CREATE PROCEDURE with *
* different but similar procedure name Deadlock can happen *
* between locks acquired in the catalog cache and locks *
* acquired for the SYSIBM.SYSROUTINES catalog table. User can *
* find these associated locks and tables involved in the *
* deadlock from the deadlock event monitor outputs: *
* Participant No 2 requesting lock *
* ---------------------------------- *
* Lock Name : 0x0200000000000000E00FE28043 *
* Lock wait start time : 2011-02-14-09.11.10.819404 *
* Lock wait end time : 2011-02-14-09.11.19.065928 *
* Lock Type : CATALOG *
* Lock Specifics : *
* loadingID:00000000,loadingBytes:00000000 80E20FE0 *
* Lock Attributes : 00000000 *
* Lock mode requested : Exclusive *
* Lock mode held : Exclusive *
* Lock Count : 255 *
* Lock Hold Count : 0 *
* Lock rrIID : 0 *
* Lock Status : Waiting *
* Lock release flags : 40000000 *
* Tablespace TID : *
* Tablespace Name : *
* Table FID : *
* Table Schema : *
* Table Name : *
* *
* Participant No 1 requesting lock *
* ---------------------------------- *
* Lock Name : 0x0000160017004C000000000052 *
* Lock wait start time : 2011-02-14-09.11.10.852327 *
* Lock wait end time : 2011-02-14-09.11.19.065928 *
* Lock Type : ROW *
* Lock Specifics : ROWID=23,DATA_PARTITION_ID=0,PAGEID=76 *
* Lock Attributes : 00000000 *
* Lock mode requested : Update *
* Lock mode held : Exclusive *
* Lock Count : 1 *
* Lock Hold Count : 0 *
* Lock rrIID : 0 *
* Lock Status : Waiting *
* Lock release flags : 40000000 *
* Tablespace TID : 0 *
* Tablespace Name : SYSCATSPACE *
* Table FID : 22 *
* Table Schema : SYSIBM *
* Table Name : SYSROUTINES *
****************************************************************
* RECOMMENDATION: *
* First fixed in DB2 9.7 fixpak 5 *
**************************************************************** |
| Local Fix: |
|
| available fix packs: |
DB2 Version 9.7 Fix Pack 5 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 6 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 7 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 8 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 9 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 9a for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 10 for Linux, UNIX, and Windows
|
| Solution |
|
| Workaround |
not known / see Local fix |
| Timestamps |
Date - problem reported :
Date - problem closed :
Date - last modified :
| 06.05.2011
02.01.2012
02.01.2012 |
| Problem solved at the following versions (IBM BugInfos) |
9.7.
|
| Problem solved according to the fixlist(s) of the following version(s) |
| 9.7.0.5
|
 |
