|
Problem IC74239
|
Status: Closed |
TWO DROP TABLE STATEMENTS ON TWO DIFFERENT TABLES MAY RUN INTO A DEADLOCK |
| product: |
DB2 FOR LUW / DB2FORLUW / 970 - DB2 |
| Problem description: |
Running two DROP TABLE statements concurrently on two different
tables, but with similar naming, may hit a deadlock among system
catalog tables.
User can find these associated locks and tables involved in the
deadlock from the deadlock event monitor outputs:
Application 1 performing DROP TABLE ABCD_02.
Lock Name : 0x0000010C00000000000C000B52
Lock Attributes : 0x00000010
Release Flags : 0x40000000
Table of lock waited on : SYSDEPENDENCIES
Type of lock: Row
Mode of lock: U - Update
Mode application requested on lock: U - Update
Database partition : 0
Lock Name : 0x0000000900000000003A000552
Lock Attributes : 0x00000030
Release Flags : 0x40000000
Lock Count : 1
Hold Count : 0
Lock Object Name : 3801093
Object Type : Row
Tablespace Name : SYSCATSPACE
Table Schema : SYSIBM
Table Name : SYSINDEXCOLUSE
Data partition id : 0
Mode : X - Exclusive
Application 2 performing DROP TABLE ABCD_01
Lock Name : 0x0000000900000000003A000552
Lock Attributes : 0x00000010
Release Flags : 0x40000000
Table of lock waited on : SYSINDEXCOLUSE
Type of lock: Row
Mode of lock: X - Exclusive
Mode application requested on lock: U - Update
Database partition : 0
Lock Name : 0x0000010C00000000000C000B52
Lock Attributes : 0x00000010
Release Flags : 0x40000000
Lock Count : 1
Hold Count : 0
Lock Object Name : 786443
Object Type : Row
Tablespace Name : SYSCATSPACE
Table Schema : SYSIBM
Table Name : SYSDEPENDENCIES
Data partition id : 0
Mode : U - Update |
| 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. *
**************************************************************** |
| Local Fix: |
Run the DROP TABLE statements sequentially or only perform
concurrent DROP on two tables with very different naming. |
| 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 |
Problem was first fixed in DB2 UDB Version 9.7 FixPack 5. |
| Workaround |
not known / see Local fix |
| BUG-Tracking |
forerunner : APAR is sysrouted TO one or more of the following: IC80020
follow-up : |
| Timestamps |
Date - problem reported :
Date - problem closed :
Date - last modified :
| 01.02.2011
16.12.2011
16.12.2011 |
| Problem solved at the following versions (IBM BugInfos) |
9.7.FP5
|
| Problem solved according to the fixlist(s) of the following version(s) |
| 9.7.0.5
|
 |
