Trace Data Specific to Deadlock Event

This topic describes the trace data that is specific to the Deadlock Event.

The Format of Deadlock-Specific Data

The following example shows the layout of Deadlock-Specific data.

COUNTER =XXXXX     WAITERS =XXXXX        
TSTAMP  =MM/DD/YY HH:MM:SS.ss            
HASH    =X'HHHHHHHH'                     
---------- BLOCKER is HOLDER ----------- 
LUW=XXXXXXXX.XXXXXXXX.XXXXXXXXXXXX       
MEMBER  =XXXXXXXX  CONNECT =XXXXXXXX     
PLANNAME=XXXXXXXX  CORRID  =XXXXXXXXXXXX 
DURATION=XXXXXXXX  PRIMAUTH=XXXXXXXX     
STATE   =XXXXX     STMTINFO=XXXXXXXX     
ENDUSER =XXXXXXXXXXXX                    
WSNAME  =XXXXXXXXXXXX                    
TRANSAC=XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX 
PROGNAME=xxxxxxxx                        
COLLID  =xxxxxxxxxxxxxxxxxx              
LOCATION=xxxxxxxxxxxxxxxx                
CONTOKEN=X'xxxxxxxxxxxxxxxx'             
STMTID  =X'xxxxxxxxxxxxxxxx'             
                                         
---------------- WAITER ---------------- 
LUW=XXXXXXXX.XXXXXXXX.XXXXXXXXXXXX       
MEMBER =XXXXXXXX   CONNECT =XXXXXXXX     
PLANNAME=XXXXXXXX  CORRID  =XXXXXXXXXXXX 
DURATION=XXXXXXXX  PRIMAUTH=XXXXXXXX     
REQUEST =XXXXXX    WORTH   =XXXXX        
STATE   =XXXXX     STMTINFO=XXXXXXXX     
ENDUSER =XXXXXXXXXXXX                    
WSNAME  =XXXXXXXXXXXX                    
TRANSAC=XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX 
PROGNAME=xxxxxxxx                        
COLLID  =xxxxxxxxxxxxxxxxxx              
LOCATION=xxxxxxxxxxxxxxxx                
CONTOKEN=X'xxxxxxxxxxxxxxxx'             
STMTID  =X'xxxxxxxxxxxxxxxx'

Field description

The individual fields have the following meaning:

COUNTER
The deadlock interval counter.
WAITERS
The number of waiters involved in the deadlock.
TSTAMP
The time when the deadlock occurred.
HASH
The lock resource hash value.
LUW
The ID of the blocker's or waiter's logical unit of work.
MEMBER
The blocker's or waiter's member name. In a non-data-sharing environment, this field contains N/P.
CONNECT
The holder's or waiter's connection name.
PLANNAME
The blocker's or waiter's plan name.
CORRID
The blocker's or waiter's correlation name.
DURATION
The lock duration of the deadlock blocker or waiter. Valid values are shown in Table 1.
Table 1. Lock Duration
Duration Description
MANUAL Varies depending on the ISOLATION parameter
MANUAL+1 Temporary change of consistency level from CS to RR during bind and DDL
COMMIT Until commit
COMMIT+1 Past commit; applies to locks needed to maintain the position for a cursor opened WITH HOLD
ALLOCATN Until deallocation
PLAN For the duration of the plan
UTILITY For the duration of the utility execution
INTEREST For the duration of P-Locks
FREE ALL Until all locks are freed
PRIMAUTH
The primary authorization ID of the thread.
REQUEST
The waiter's request, which can be one of the following:
  • LOCK
  • UNLOCK
  • CHANGE
WORTH
The waiter's worth value assigned by Db2®.
STATE
The holder's or waiter's state or mode of the lock applied to the resource. Valid values are shown in Table 2.
Table 2. Lock State
State Description
UPS Unprotected share
IS Intent share
IX Intent exclusive
S Share
U Update
SIX Share with intent exclusive
NSU Nonshared update
X Exclusive
STMTINFO
The statement information of the holder or waiter.
ENDUSER
End user's user ID. This field is not shown when this information is not present.
WSNAME
End user's workstation name. This field is not shown when this information is not present.
TRANSAC
The end user's transaction name. This field is not shown when this information is not present.
PROGNAME
The program name can be one of the following:
  • The name of the blocker's program that is currently in control at the time of the deadlock and not necessarily the program that acquired the lock.
  • The waiter’s program that is contending the resource.
COLLID
The collection identifier can be one of the following:
  • The package collection ID of the blocker's program that is currently in control at the time of the deadlock and not necessarily the program that acquired the lock.
  • The package collection ID of the waiter's program that is contending the resource.
LOCATION
The location can be one of the following:
  • The location of the blocker's program that is currently in control at the time of the deadlock and not necessarily the program that acquired the lock.
  • The location of the waiter's program that is contending the resource.
CONTOKEN
The consistency token can be one of the following:
  • The consistency token of the blocker's program that is currently in control at the time of the deadlock and not necessarily the program that acquired the lock.
  • The consistency token of the waiter's program that is contending the resource.
STMTID
The statement ID of the holder or waiter.