DB2 FOR LUW / DB2FORLUW / 970 - DB2

When dropping indexes from a given table, if there is a DML 
statement running concurrently referencing the same table, it is 
possible to encounter a deadlock. 
 
This can only happen during the compilation stage of the DML 
statement, and is a small timing window in which it can cause a 
deadlock with the DROP INDEX statement.

DROP INDEX STATEMENTS MAY DEADLOCK WITH DML ISSUED AGAINST THE 
SAME TABLE

Workaround: 
 
Serialize DDL on a given table, ensuring to commit after each 
statement. Attempt to have DML statements issued after the DDL 
work has been completed.  If dropping indexes is a common 
scenario for tables that are being accessed by DML, then it is 
best to apply this APAR to your environment. 
 
Defect: wsdbu00398698

DB2 Version 9.7 Fix Pack 1 for Linux, UNIX, and Windows
 DB2 Version 9.7 Fix Pack 2 for Linux, UNIX, and Windows
 DB2 Version 9.7 Fix Pack 3 for Linux, UNIX, and Windows
 DB2 Version 9.7 Fix Pack 3a for Linux, UNIX, and Windows
 DB2 Version 9.7 Fix Pack 4 for Linux, UNIX, and Windows
 DB2 Version 9.7 Fix Pack 5 for Linux, UNIX, and Windows
 DB2 Version 9.7 Fix Pack 7 for Linux, UNIX, and Windows
 DB2 Version 9.7 Fix Pack 9a for Linux, UNIX, and Windows
 DB2 Version 9.7 Fix Pack 6 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 10 for Linux, UNIX, and Windows
 

First Fixed in DB2 LUW v9.7 Fixpack 1 and later.

keiner bekannt / siehe Local-Fix

Datum - Problem gemeldet    :
Datum - Problem geschlossen :
Datum - der letzten Änderung:

25.06.2009
15.12.2009
15.12.2009

9.7.FP1