Applications: Locks and Deadlocks (DB2 UDB for UNIX and Windows)

To display information on locks and deadlocks for your selected application(s), call the DBA Cockpit.

...

1. In the navigation frame, choose Performance ®Applications.

The Application Snapshot screen appears.

2. To display more detailed information, select one or more applications and choose This graphic is explained in the accompanying text Details.

A detail Application Snapshot screen appears.

3. Choose Locks and Deadlocks.

If you have selected more than one application, you can use the page buttons on the screen to navigate between them.

Fields	Description
*Lock Waits*
Total	Total number of times that this application requested a lock, but had to wait because another application was already holding a lock on the data
Time Waited	Total amount of elapsed time in milliseconds that this application has waited for a lock to be granted
Average Time Waited	Average time in milliseconds waited for a lock
*Escalations*
Lock Escalations	Number of times that locks have been escalated from several row locks to a table lock. If the maximum allowed length of the lock list is reached, row locks are converted to table locks to save space in the lock list. This process is called "lock escalation".
Exclusive Lock Escalations	Number of times that locks have been escalated from several row locks to one exclusive table lock, or the number of times an exclusive lock on a row caused the table lock to become an exclusive lock. Exclusive locks are important to track since they can impact the concurrency of your data because other applications cannot access data held by an exclusive lock.
*Locks*
Locks Currently Held	Total number of locks currently held by the application
Deadlocks Detected	Number of deadlocks that have occurred. Deadlock situations are recognized and resolved automatically by the database. The database configuration parameter DLCHKTIME determines when a lock wait situation is resolved.
Lock Timeouts	Number of times that a request to lock an object timed out instead of being granted. The database configuration parameter LOCKTIMEOUT determines when a lock wait situation is resolved.