DB2 FOR LUW / DB2FORLUW / 970 - DB2

The DB2 server may terminate abnormally when capturing a queue 
threshold deadlock if the locking event monitor is enabled. 
The trap file produced should contain a call stack containing 
the function sqmCollectQueueDeadlock. 
 
sqmCollectDeadlockStackEntry 
sqmCollectQueueDeadlock 
sqlrwReportPotentialQueueBasedDeadlock 
sqlpFindAndNotifyApp 
sqlpReceiveGDDMessage 
sqlpldl 
sqloEDUEntry 
 
Problem occurs only when using the locking event monitor and 
thresholds.

NONE 
Please note: An alternative method can be used to identify the 
threshold and applications involved in the deadlock: 
 
- Disable collection of deadlocks using the locking event 
monitor by setting db cfg parameter to mon_deadlock to NONE 
- Turn db cfg parameter mon_lck_msg_lvl to level 2 
- Re-run application and monitor the db2diag.log or DB2 
notification log 
- A notification message will be generated when the queue 
deadlock occurs. The message will contain information regarding 
the threshold involved in the deadlock and the application 
holding the lock 
- If notification message is not enough to resolve the deadlock 
and further diagnostic is required, then please upgrade to v9.7 
Fixpack 2 and enable the lock event monitor to capture 
deadlocks.

keiner bekannt / siehe Local-Fix

This APAR is a duplicate of IC66251

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

16.02.2010
16.07.2010
16.07.2010