Deadlocks are usually difficult to solve because only one side of the resource conflict is presented by the DB2 deadlock message, DSNT375I. However, a snapshot of the full deadlock resource conflict is available if you are running statistics class 3 traces. These traces reportedly require very little overhead to remain active and are very useful for analyzing deadlock problems.
If the trace is active, a record is placed into the DB2 trace files (usually SMF files) for each deadlock. The record contains the user IDs, plans, and both resources involved in the conflict. An example of the type of output from a performance monitor is provided in the documentation for DB2PMt. Most performance monitors have similar reports that outline both sides of the conflict.
|
Copyright © 2013 CA.
All rights reserved.
|
|