DB2 FOR LUW / DB2FORLUW / 980 - DB2

Lock mode held none in the event monitor output should be 
incorrect. 
Incorrect Lock mode held output from db2evmonfmt. 
 
Here is the extract of the event monitor. 
 
As follows, when they couldn't catch the information of Lock 
Owner,  "Lock mode held none" was output in the event monitor. 
======================== 
------------------------------------------------------- 
Event ID               : 2 
Event Type             : LOCKTIMEOUT 
Event Timestamp        : 2012-03-15-20.53.25.932328 
Partition of detection : 0 
------------------------------------------------------- 
 
Participant No 1 requesting lock 
---------------------------------- 
Lock Name            : 0x00020004000000000000000054 
Lock wait start time : 2012-03-15-20.53.20.931148 
Lock wait end time   : 2012-03-15-20.53.25.932328 
Lock Type            : TABLE 
Lock Specifics       : 
Lock Attributes      : 00603000 
Lock mode requested  : Exclusive 
Lock mode held       : none 
Lock Count           : 1 
Lock Hold Count      : 0 
Lock rrIID           : 0 
Lock Status          : Converting 
Lock release flags   : 40000000 
Tablespace TID       : 2 
Tablespace Name      : USERSPACE1 
Table FID            : 4 
Table Schema         : DB2INST1 
Table Name           : TABLE1 
 
The problem only happen if the lock owner is not in the same 
member of the requester.

**************************************************************** 
* USERS AFFECTED:                                              * 
* ALL                                                          * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* See Error Description                                        * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Upgrade to DB2 UDB version 9.8 fixpack 5.                    * 
****************************************************************

Problem was first fixed in DB2 UDB Version 9.8 Fixpack 5.

keiner bekannt / siehe Local-Fix

Vorgänger  : APAR is sysrouted TO one or more of the following: IC87842 
Nachfolger : 

Datum - Problem gemeldet    :
Datum - Problem geschlossen :
Datum - der letzten Änderung:

19.04.2012
04.07.2012
04.07.2012

9.8.FP5