Finding the resources involved

To find the other resources involved in a deadlock, you might have to activate a DB2 performance trace and recreate the deadlock.

Suppose that the reason for solving the deadlock is that the number of deadlocks is too high. Normally recreating the deadlock after the trace is started is a minor problem.

Limit the DB2 performance trace to the two plans indicated in the MVS log message. Limiting the trace to the two CICS transaction IDs (authorization IDs) involved can also be reasonable. Include class(06) for general locking events and class(03) for SQL events in the performance trace . The DB2 Performance Monitor (DB2PM) is a useful tool to format the trace output. The DB2PM lock contention report and the lock suspension report can assist in determining the resources involved in the deadlock.

If the output from the DB2PM reports is too large, you can develop a user program to analyze the output from the traces. The goal is to find the resources involved in the deadlock and all the SQL statements involved.



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