DB2 - Problem description
| Problem IC98395 | Status: Closed | 
| ON SOME RARE OCASIONS, LOCKING EVENT MONITOR MIGHT FAIL TO REPORT ALL PARTICIPANTS OF A DEADLOCK | |
| product: | |
| DB2 FOR LUW / DB2FORLUW / A50 - DB2 | |
| Problem description: | |
| Under intensive operations, an EVENT MONITOR ... FOR LOCKING might report a 3 way deadlock but only gather information for 2 two of the participants. | |
| Problem Summary: | |
| **************************************************************** * USERS AFFECTED: * * All using lock event monitor * **************************************************************** * PROBLEM DESCRIPTION: * * See Error Description * **************************************************************** * RECOMMENDATION: * * Upgrade to version 10.5 Fixpack 4 * **************************************************************** | |
| Local Fix: | |
| available fix packs: | |
| DB2 Cancun Release 10.5.0.4 (also known as Fix Pack 4) for Linux, UNIX, and Windows | |
| Solution | |
| First fixed in version 10.5 Fixpack 4 | |
| Workaround | |
| not known / see Local fix | |
| Timestamps | |
| Date - problem reported : Date - problem closed : Date - last modified : | 18.12.2013 28.07.2014 28.07.2014 | 
| Problem solved at the following versions (IBM BugInfos) | |
| Problem solved according to the fixlist(s) of the following version(s) | |
| 10.5.0.4 |  | 







 
