User Tools

Site Tools


middleware:db2deadlocks

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revision Previous revision
middleware:db2deadlocks [2014/08/08 09:24]
ap [db2pd]
middleware:db2deadlocks [2014/08/08 12:57] (current)
ap
Line 91: Line 91:
  
 When DB2_CAPTURE_LOCKTIMEOUT is set to ON, DB2 automatically creates a report file for each lock timeout occurrence. The report file is written to the directory where the DIAGPATH database manager configuration (DBM CFG) parameter points, to and contains information about, the date and time of the lock timeout, the problematic lock, the lock requester, and the lock owner. When DB2_CAPTURE_LOCKTIMEOUT is set to ON, DB2 automatically creates a report file for each lock timeout occurrence. The report file is written to the directory where the DIAGPATH database manager configuration (DBM CFG) parameter points, to and contains information about, the date and time of the lock timeout, the problematic lock, the lock requester, and the lock owner.
 +
 +==== Find the SQL statements locking ====
 +
 +  - Find the AppHandl of the locked apps ''​db2pd -db $MYDB -locks wait''​
 +  - With ''​db2pd -applications -dynamic -db $MYDB''​ find the L-AnchID of the found AppHandl'​s and with that search the output for the SQL statement.
middleware/db2deadlocks.txt · Last modified: 2014/08/08 12:57 by ap

Informativa sui cookie