IBM Support

IC75031: DEADLOCK MAY OCCUR WHEN RUNNING TWO ALTER TABLE ATTACH PARTITION COMMANDS CONCURRENTLY

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • When the ATTACH PARTITION command is executed in a high
    concurrency level, deadlock may occur if the table being
    attached as the new partition has index defined on it. The
    deadlock is between the two catalog tables, SYSDEPENDENCIES and
    SYSINDEXAUTH.
    
    You will see the below records from the deadlock event monitor
    output:
    
    Application 1:
    
    Lock requested: U lock on SYSDEPENDENCIES
    Lock Held:
          Lock Name                   : 0x00000014000000000004000552
          Lock Attributes             : 0x00000020
          Release Flags               : 0x40000000
          Lock Count                  : 1
          Hold Count                  : 0
          Lock Object Name            : 262149
          Object Type                 : Row
          Tablespace Name             : SYSCATSPACE
          Table Schema                : SYSIBM
          Table Name                  : SYSINDEXAUTH
          Data partition id           : 0
          Mode                        : X   - Exclusive
    
    Application 2:
    
    Lock requested: NS on SYSINDEXAUTH
    Lock Held:
    
          Lock Name                   : 0x0000010C00000000000C001252
          Lock Attributes             : 0x00000010
          Release Flags               : 0x40000000
          Lock Count                  : 2
          Hold Count                  : 0
          Lock Object Name            : 786450
          Object Type                 : Row
          Tablespace Name             : SYSCATSPACE
          Table Schema                : SYSIBM
          Table Name                  : SYSDEPENDENCIES
          Data partition id           : 0
          Mode                        : U   - Update
    

Local fix

  • Run the ALTER TABLE ATTACH PARTITION commands in sequence rather
    than in parallel.
    

Problem summary

  • ****************************************************************
    * USERS AFFECTED:                                              *
    * DB2 UDB Version 9.7                                          *
    ****************************************************************
    * PROBLEM DESCRIPTION:                                         *
    * See Error description field for more information.            *
    ****************************************************************
    * RECOMMENDATION:                                              *
    * Upgrade to Version 9.7 FixPack 5.                            *
    ****************************************************************
    

Problem conclusion

  • Problem was first fixed in DB2 UDB Version 9.7 FixPack 5.
    

Temporary fix

Comments

APAR Information

  • APAR number

    IC75031

  • Reported component name

    DB2 FOR LUW

  • Reported component ID

    DB2FORLUW

  • Reported release

    970

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt

  • Submitted date

    2011-03-15

  • Closed date

    2011-12-16

  • Last modified date

    2011-12-16

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

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

Fix information

  • Fixed component name

    DB2 FOR LUW

  • Fixed component ID

    DB2FORLUW

Applicable component levels

  • R970 PSN

       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:
16 December 2011