Analyzing lock contention
Although locking problems must usually be resolved at the application level, the first indication of problems—and the simplest identification of the applications and resources involved—can best be seen at the system level.
To view locking problems in one DB2 (without data sharing)
If you are not sure whether you are having much lock contention, you might want to review the lockout and suspension counts and rates first in the STRATE view.
- From EZDB2, hyperlink on Activity Rates.A certain number of lock suspensions (and even an occasional timeout or deadlock) is to be expected in an active DB2 system. However, because more frequent lockout conditions (timeouts or deadlocks) might be cause for concern because they might terminate associated SQL statements.
- Press F3 to return to EZDB2.
Select Locking Menu.The DB2 Locking easy menu EZDLOCK is displayed (PTF BPD4875 applied).
DB2 Locking Menu
DB2 Target ---> 1210
Currently Held Locks +----------------------+ Lock Statistics
. Suspended Threads | Place cursor on | . Lock Counts-One DB2
. Resources with Waiters | menu item and | . Lock Counts-Data Shar.
. Locks Held / Threads | press ENTER |
. Locks Held / Resources +----------------------+
Lockouts - One DB2 < Lockout analysis > Lockouts-Data Sharing
. Lockout Events by Time . Resource Cont. Summary . Lockout Events by Time
. Blocker/Waiter Summary . Conntype Cont. Summary . Blocker/Waiter Summary
. Blk/Wt Summ by AuthID . Blk/Wt Summ by AuthID
Summary by PlanName
Contention Analysis . Blocker Summary
. Lock Wizard Dialog . Waiter Summary . Return... .
Summary by AUTHID
. Blocker Summary
Total Locks overview . Waiter Summary Total Locks summaryAlthough you might have analyzed lockout conditions one at a time before, the windows mode views provide additional analysis capabilities. They are available through the hyperlinks in EZDLOCK.
This section contains the following topics:
Related topic
Tip: For faster searching, add an asterisk to the end of your partial query. Example: cert*