DB2 - Problem description
Problem IC71359 | Status: Closed |
DEADLATCH DURING A COMPLEX QUERY | |
product: | |
DB2 FOR LUW / DB2FORLUW / 970 - DB2 | |
Problem description: | |
One thread holds SQLP_LTRN_CHAIN__entry_latch and waits for SQLD_CHAIN__fullChainLatchNS. The second thread has the latches in the opposite order. Deadlatch occurs. This is timing related and does not always occur even with the exact same query. | |
Problem Summary: | |
**************************************************************** * USERS AFFECTED: * * Users using DB2 V9.7 FP3a and below. * **************************************************************** * PROBLEM DESCRIPTION: * * One thread holds SQLP_LTRN_CHAIN__entry_latch and waits for * * SQLD_CHAIN__fullChainLatchNS. The second thread has the * * latches in the opposite order. A deadlatch occurs. * **************************************************************** * RECOMMENDATION: * * Please upgrade to DB2 V9.7 FP4 where this APAR is fixed. * **************************************************************** | |
Local Fix: | |
available fix packs: | |
DB2 Version 9.7 Fix Pack 4 for Linux, UNIX, and Windows | |
Solution | |
This APAR is first fixed in DB2 V9.7 FP4 | |
Workaround | |
not known / see Local fix | |
BUG-Tracking | |
forerunner : APAR is sysrouted TO one or more of the following: IC71362 follow-up : | |
Timestamps | |
Date - problem reported : Date - problem closed : Date - last modified : | 21.09.2010 29.04.2011 29.04.2011 |
Problem solved at the following versions (IBM BugInfos) | |
9.7.FP4 | |
Problem solved according to the fixlist(s) of the following version(s) | |
9.7.0.4 |