Deadlock detection

Deadlock information is available in the DB2 performance trace or in the MVS log.

About this task

In a normal production environment running without DB2 performance traces activated, the easiest way to get information about a deadlock is to scan the MVS™ log to find the messages shown in Figure 1.
Figure 1. Deadlock messages
 
   DSNT375I PLAN p1 WITH CORRELATION ID id1
   AND CONNECTION ID id2 IS DEADLOCKED with
   PLAN p2 WITH CORRELATION ID id3
   AND CONNECTION ID id4.
 
   DSNT501I DSNILMCL RESOURCE UNAVAILABLE
            CORRELATION-ID=id1,CONNECTION-ID=id2
            REASON=r-code
            TYPE name
            NAME name
 
From these messages, both partners in the deadlock are identified. The partners are given by both plan name and correlation ID.

Also, a second message identifies the resource that the victim could not obtain. The other resource (whether it is the same or not) is not displayed in the message.



dfhtk5j.html | Timestamp icon Last updated: Monday, 5 June 2017