home clear 64x64
en blue 200x116 de orange 200x116 info letter User
suche 36x36
Latest versionsfixlist
11.1.0.7 FixList
10.5.0.9 FixList
10.1.0.6 FixList
9.8.0.5 FixList
9.7.0.11 FixList
9.5.0.10 FixList
9.1.0.12 FixList
Have problems? - contact us.
Register for free anmeldung-x26
Contact form kontakt-x26

DB2 - Problem description

Problem IC82043 Status: Closed

INCOMPLETE DEADLOCK INFORMATION RECORDED FOR DEADLOCK PARTICIPANTS ON
DIFFERENT MEMBERS

product:
DB2 FOR LUW / DB2FORLUW / 980 - DB2
Problem description:
Information may be missing from an event monitor which has 
been created with the "for locking write to unformatted event 
table" options if the lock event participants are on different 
members. 
 
  Selecting from the event table may show some records 
generated, but because there are records missing for some of the 
participants, the db2evmonfmt java program cannot format the 
deadlock events properly and no output may be generated.
Problem Summary:
**************************************************************** 
* USERS AFFECTED:                                              * 
* All                                                          * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* See Error Description                                        * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Upgrade to db2 Version 9.8 FixPak 5                          * 
****************************************************************
Local Fix:
To activate a deadlocks with details event monitor.
Solution
Problem was first fixed in Version 9.8 FixPak 5
Workaround
not known / see Local fix
BUG-Tracking
forerunner  : APAR is sysrouted TO one or more of the following: IC87840 
follow-up : 
Timestamps
Date  - problem reported    :
Date  - problem closed      :
Date  - last modified       :
15.03.2012
17.06.2012
17.06.2012
Problem solved at the following versions (IBM BugInfos)
9.8.
Problem solved according to the fixlist(s) of the following version(s)
9.8.0.5 FixList