IBM Support

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

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as fixed if next.

Error 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
    

Local fix

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                              *
    ****************************************************************
    

Problem conclusion

Temporary fix

Comments

APAR Information

  • APAR number

    IC76237

  • Reported component name

    DB2 FOR LUW

  • Reported component ID

    DB2FORLUW

  • Reported release

    970

  • Status

    CLOSED FIN

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt

  • Submitted date

    2011-05-06

  • Closed date

    2012-01-02

  • Last modified date

    2012-01-02

  • APAR is sysrouted FROM one or more of the following:

  • APAR is sysrouted TO one or more of the following:

Fix information

Applicable component levels

  • R970 PSN

       UP

  • R970 PSY

       UP

[{"Business Unit":{"code":"BU048","label":"IBM Software"},"Product":{"code":"SSEPGG","label":"DB2 for Linux, UNIX and Windows"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"9.7","Edition":"","Line of Business":{"code":"LOB10","label":"Data and AI"}}]

Document Information

Modified date:
02 January 2012