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 IC82747 Status: Closed

LOCK EVENT MONITOR RETURNED "LOCK MODE HELD : NONE".

product:
DB2 FOR LUW / DB2FORLUW / 980 - DB2
Problem description:
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.
Problem Summary:
**************************************************************** 
* USERS AFFECTED:                                              * 
* ALL                                                          * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* See Error Description                                        * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Upgrade to DB2 UDB version 9.8 fixpack 5.                    * 
****************************************************************
Local Fix:
Solution
Problem was first fixed in DB2 UDB Version 9.8 Fixpack 5.
Workaround
not known / see Local fix
BUG-Tracking
forerunner  : APAR is sysrouted TO one or more of the following: IC87842 
follow-up : 
Timestamps
Date  - problem reported    :
Date  - problem closed      :
Date  - last modified       :
19.04.2012
04.07.2012
04.07.2012
Problem solved at the following versions (IBM BugInfos)
9.8.FP5
Problem solved according to the fixlist(s) of the following version(s)
9.8.0.5 FixList