The type of lock being
held. If the mode is unknown, the value of this monitor element is
NULL.
Table 2. Snapshot Monitoring InformationSnapshot Level |
Logical Data Grouping |
Monitor Switch |
Application |
appl |
Lock |
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
This mode can help you determine
the source of contention for resources.
This element indicates
one of the following, depending on the type of monitor information
being examined:
- The type of lock another application holds on the object that
this application is waiting to lock (for application-monitoring and
deadlock-monitoring levels).
- The type of lock held on the object by this application (for object-lock
levels).
The possible values for this field are:
Mode |
Type of Lock |
API Constant |
|
No Lock |
SQLM_LNON |
IS |
Intention Share Lock |
SQLM_LOIS |
IX |
Intention Exclusive Lock |
SQLM_LOIX |
S |
Share Lock |
SQLM_LOOS |
SIX |
Share with Intention Exclusive Lock |
SQLM_LSIX |
X |
Exclusive Lock |
SQLM_LOOX |
IN |
Intent None |
SQLM_LOIN |
Z |
Super Exclusive Lock |
SQLM_LOOZ |
U |
Update Lock |
SQLM_LOOU |
NS |
Scan
Share Lock |
SQLM_LONS |
NW |
Next Key Weak Exclusive Lock |
SQLM_LONW |