DB2 - Problem description
Problem IC98282 | Status: Closed |
ON SOME RARE OCASIONS, LOCKING EVENT MONITOR MIGHT FAIL TO REPORT ALL PARTICIPANTS OF A DEADLOCK | |
product: | |
DB2 FOR LUW / DB2FORLUW / A10 - DB2 | |
Problem description: | |
Under intensive operations, an EVENT MONITOR ... FOR LOCKING might report a 3 way deadlock but only gather information for two of the participants. | |
Problem Summary: | |
**************************************************************** * USERS AFFECTED: * * Using lock event monitor * **************************************************************** * PROBLEM DESCRIPTION: * * See Error Description * **************************************************************** * RECOMMENDATION: * * Upgrade to version 10.1 fix pack 4 * **************************************************************** | |
Local Fix: | |
available fix packs: | |
DB2 Version 10.1 Fix Pack 4 for Linux, UNIX, and Windows | |
Solution | |
First fixed in version 10.1 fix pack 4 | |
Workaround | |
not known / see Local fix | |
BUG-Tracking | |
forerunner : APAR is sysrouted TO one or more of the following: IC98284 IC98395 follow-up : | |
Timestamps | |
Date - problem reported : Date - problem closed : Date - last modified : | 12.12.2013 02.06.2014 02.06.2014 |
Problem solved at the following versions (IBM BugInfos) | |
Problem solved according to the fixlist(s) of the following version(s) | |
10.1.0.4 |