|
Problem IC63602
|
Status: Closed |
DB2 MAY GET HUNG DUE TO DEAD LATCH. |
| product: |
DB2 FOR LUW / DB2FORLUW / 970 - DB2 |
| Problem description: |
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. |
| Problem Summary: |
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. |
| Local Fix: |
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= |
| available fix packs: |
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
|
| Solution |
First fixed in db2 v9.7 fp3. |
| Workaround |
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= |
| Timestamps |
Date - problem reported :
Date - problem closed :
Date - last modified :
| 07.10.2009
24.09.2010
24.09.2010 |
| Problem solved at the following versions (IBM BugInfos) |
9.7.FP3
|
| Problem solved according to the fixlist(s) of the following version(s) |
| 9.7.0.3
|
 |
| 9.7.0.3
|
|
