home clear 64x64
en blue 200x116 de orange 200x116 info letter User
suche 36x36
Neueste VersionenFixList
11.1.0.7 FixList
10.5.0.9 FixList
10.1.0.6 FixList
9.8.0.5 FixList
9.7.0.11 FixList
9.5.0.10 FixList
9.1.0.12 FixList
Haben Sie Probleme? - Kontaktieren Sie uns.
Kostenlos registrieren anmeldung-x26
Kontaktformular kontakt-x26

DB2 - Problembeschreibung

Problem IC76237 Status: Geschlossen

CREATE PROCEDURE MAY DEADLOCK WITH CREATE PROCEDURE WITH DIFFERENT BUT
SIMILAR PROCEDURE NAME

Produkt:
DB2 FOR LUW / DB2FORLUW / 970 - DB2
Problembeschreibung:
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-Zusammenfassung:
**************************************************************** 
* 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:
verfügbare FixPacks:
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

Lösung
Workaround
keiner bekannt / siehe Local-Fix
Weitere Daten
Datum - Problem gemeldet    :
Datum - Problem geschlossen :
Datum - der letzten Änderung:
06.05.2011
02.01.2012
02.01.2012
Problem behoben ab folgender Versionen (IBM BugInfos)
9.7.
Problem behoben lt. FixList in der Version
9.7.0.5 FixList