Latest versionsfixlist
11.1.0.6 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
Question in the chat LiveZilla Live Help

DB2 - Problem description

Problem IC67306 Status: Closed

DEADLATCH DURING EVENT MONITOR PROCESSING CAUSES NODE HANG

product:
DB2 FOR LUW / DB2FORLUW / 950 - DB2
Problem description:
A deadlatch should happen when "flush event monitor" and 
activity event monitor tries to capture the data at the same 
time. This deadlatch causes db2fcmr hang and it results Node 
hang. The stack traceback of db2fcmr could be: 
 
getConflictComplex__17SQLO_SLATCH_CAS64FCUl 
getConflict__17SQLO_SLATCH_CAS64FCUl 
getConflict__17SQLO_SLATCH_CAS64FCUl@glueF4 
CreateAppl__14sqeAppServicesFP18SQLE_CRT_APPL_PARM 
sqlePdbProcessRequest__FP11sqkfChannelPv 
RouteInboundBuffer__19sqkfFastCommManagerFRP10sqkfBufferP17SQLKF 
_SESSION_HDLiT3 
HandleDataEvent__15sqkfRecvConduitFUl 
RunEDU__15sqkfRecvConduitFv 
EDUDriver__9sqzEDUObjFv 
sqloEDUEntry 
 
db2pd -latches reports the deadlatch situation as follows: 
 
Database Partition 1 -- Active -- Up 0 days 05:43:54 
 
Latches: 
Address            Holder  Waiter  Filename        LOC 
LatchType 
  : 
0x07800000002304F8 20183   1800    sqlmemon.C      2629 
SQLO_LT_sqeAppServices__m_appServLatch 
0x0780000000C8ECF8 20183   20697   sqlmemgr.C      3900 
SQLO_LT_sqm_evmon_mgr__em_list_latch 
0x07800000002304F8 20697   1800    sqlrw_wlm_tf.C  4887 
SQLO_LT_sqeAppServices__m_appServLatch 
0x07800000013DA48C 20697   20183   sqlrw_wlm_tf.C  4911 
SQLO_LT_sqeApplication__masterAppLatch 
 
In this case, db2fcmr(edu id 1800) is wating on a latch held by 
edu id 20183 and 20697, but those edus are deadlatched.
Problem Summary:
**************************************************************** 
* USERS AFFECTED:                                              * 
* DB2 Version 9.5                                              * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* See Error description field for more information.            * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Upgrade to Version 9.5 FixPack 6.                            * 
****************************************************************
Local Fix:
available fix packs:
DB2 Version 9.5 Fix Pack 6a for Linux, UNIX, and Windows
DB2 Version 9.5 Fix Pack 7 for Linux, UNIX, and Windows
DB2 Version 9.5 Fix Pack 8 for Linux, UNIX, and Windows
DB2 Version 9.5 Fix Pack 9 for Linux, UNIX, and Windows
DB2 Version 9.5 Fix Pack 10 for Linux, UNIX, and Windows

Solution
Problem was first fixed in DB2 Version 9.5 FixPack 6.
Workaround
not known / see Local fix
BUG-Tracking
forerunner  : APAR is sysrouted TO one or more of the following: IC68249 IC68250 
follow-up : 
Timestamps
Date  - problem reported    :
Date  - problem closed      :
Date  - last modified       :
18.03.2010
10.06.2010
10.06.2010
Problem solved at the following versions (IBM BugInfos)
9.5.FP6
Problem solved according to the fixlist(s) of the following version(s)
This site uses cookies to make it easier for us to provide you with our services. By using our site you agree to the use of cookies.