DB2 FOR LUW / DB2FORLUW / 970 - DB2

This deadlatch is related to the DB2_CAPTURE_LOCKTIMEOUT 
registry variable. 
 
Application1 running snapshot monitor is holding the 
masterAppLatch and requesting the lock hash-table latch. 
Application2 doing an index operation is holding the hash-table 
latch, it's lock request times out so it calls 
sqlpLockTimeoutInfo to dump more information (because 
DB2_CAPTURE_LOCKTIMEOUT is enabled) and this requests the 
masterAppLatch.

This deadlatch is related to the DB2_CAPTURE_LOCKTIMEOUT 
registry variable. 
 
Application1 running snapshot monitor is holding the 
masterAppLatch and requesting the lock hash-table latch. 
Application2 doing an index operation is holding the hash-table 
latch, it's lock request times out so it calls 
sqlpLockTimeoutInfo to dump more information (because 
DB2_CAPTURE_LOCKTIMEOUT is enabled) and this requests the 
masterAppLatch.

For the time being, to avoid this deadlatch customer can disable 
DB2_CAPTURE_LOCKTIMEOUT (recycling the instance is not 
required).  As the informational collected when this registry 
variable is enabled is only informational, it should not be a 
problem for customer to disable this temporarily. 
 
To disable lock timeout reporting, issue the following command: 
db2set DB2_CAPTURE_LOCKTIMEOUT=

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

First fixed in db2 v9.7 fp3.

For the time being, to avoid this deadlatch customer can disable 
DB2_CAPTURE_LOCKTIMEOUT (recycling the instance is not 
required). As the informational collected when this registry 
variable is enabled is only informational, it should not be a 
problem for customer to disable this temporarily. 
 
To disable lock timeout reporting, issue the following command: 
db2set DB2_CAPTURE_LOCKTIMEOUT=

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

07.10.2009
24.09.2010
24.09.2010

9.7.FP3