Indicates whether the application
waiting to acquire this lock was a result of a lock escalation request.
The possible values are Y (Yes) and N (No).
Table 2. Snapshot Monitoring InformationSnapshot Level |
Logical Data Grouping |
Monitor Switch |
Lock |
lock |
Lock |
Lock |
lock_wait |
Lock |
Table 3. Event Monitoring InformationEvent Type |
Logical Data Grouping |
Monitor Switch |
Locking |
- |
- |
Deadlocks1 |
lock |
- |
Deadlocks1 |
event_dlconn |
- |
Deadlocks with Details1 |
event_detailed_dlconn |
- |
- 1
- This option has been deprecated. Its
use is no longer recommended and might be removed in a future release.
Use the CREATE EVENT MONITOR FOR LOCKING statement to monitor lock-related
events, such as lock timeouts, lock waits, and deadlocks.
Usage
Use this element to better understand
the cause of deadlocks. If you experience a deadlock that involves
applications doing lock escalation, you may want to increase the amount
of lock memory or change the percentage of locks that any one application
can request.