Lock Interval (PI_PILO)
- Organization of this page
Function
The Lock Interval (PI_PILO) record stores performance data, taken at specific intervals, about locks. PFM - Agent for Oracle creates one record for each lock in an instance. This is a multi-instance record.
If you cannot view the performance data in this record, create Oracle's static data dictionary view DBA_WAITERS. To create this view, you must execute the CATBLOCK.SQL script that is provided by Oracle.
When Log is set to Yes, if you collect history over a long period of time, because of the short lifetime, it is not summarized in units of years or months. All instances are retained, resulting in a bloa ted store database. In addition, when the collected history is summarized, more memory is used than necessary. The memory shortage might cause monitoring to stop. If you want to collect history over a long period of time, use the Lock (PD_PDLD) record for monitoring.
Default and changeable values
|
Item |
Default value |
Changeable |
|---|---|---|
|
Collection Interval |
600 |
Y |
|
Collection Offset |
55 |
Y |
|
Log |
No |
Y |
|
LOGIF |
(Blank) |
Y |
|
Over 10 Sec Collection Time |
No |
N |
ODBC key fields
-
PI_PILO_ADDR
-
PI_PILO_SID
Lifetime
From the activation to release of a lock
Record size
-
Fixed part: 678 bytes
-
Variable part: 217 bytes
Fields
|
PFM - View name (PFM - Manager name) |
Description |
Summary |
Format |
Delta |
Supported version |
Data source |
|---|---|---|---|---|---|---|
|
Addr (ADDR) |
Lock address#1 |
COPY |
string(16) |
No |
All |
V$LOCK.KADDR |
|
Blocking (BLOCKING) |
Whether this lock blocks another lock (If it does, the value in this field is 1. Otherwise, the value is 0.)#1 |
COPY |
short |
No |
All |
V$LOCK.BLOCK |
|
Blocking Sessions (BLOCKING_SESSIONS) |
Number of sessions that are blocked because they are waiting for a lock to be released#1 |
COPY |
ulong |
No |
All |
count(WAITING_SESSION) from DBA_WAITERS where DBA_WAITERS.LOCK_ID1 = ID1 and DBA_WAITERS.LOCK_ID2 = ID2 and DBA_WAITERS.HOLDING_SESSION = SID and DBA_WAITERS.MODE_HELD = LOCK_MODE |
|
Current Mode Time (CURRENT_MODE_TIME) |
Time since the current mode was authorized#2 |
AVG |
ulong |
Yes |
All |
V$LOCK.CTIME |
|
ID1 (ID1) |
Lock ID 1#1 |
COPY |
double |
No |
All |
V$LOCK.ID1 |
|
ID2 (ID2) |
Lock ID 2#1 |
COPY |
double |
No |
All |
V$LOCK.ID2 |
|
Lock Mode (LOCK_MODE) |
Lock mode. The following are the valid values for this field: Null, Row-S (SS), Row-X (SX), Share, S/Row-X (SSX), and Exclusive. The following are the values of the fields that are displayed as abbreviations : Row-S (SS) : row share Row-X (SX) : row exclusive S/Row-X (SSX) : share row exclusive#1 |
COPY |
string(20) |
No |
All |
V$LOCK.LMODE |
|
Program (PROGRAM) |
Name of the program being executed#1 |
COPY |
string(48) |
No |
All |
V$SESSION.PROGRAM where V$LOCK.SID = V$SESSION.SID |
|
Record Time (RECORD_TIME) |
Collection termination time for the performance data stored in the record#1 |
COPY |
time_t |
No |
All |
Agent Collector |
|
Record Type (INPUT_RECORD_TYPE) |
Record name (always PILO)#1 |
COPY |
string(4) |
No |
All |
Agent Collector |
|
Request Mode (REQUEST_MODE) |
Requested lock mode. The following are the valid values for this field: Null, Row-S (SS), Row-X (SX), Share, S/Row-X (SSX), and Exclusive. The following are the values of the fields that are displayed as abbreviations : Row-S (SS) : row share Row-X (SX) : row exclusive S/Row-X (SSX) : share row exclusive#1 |
COPY |
string(20) |
No |
All |
V$LOCK.REQUEST |
|
SID (SID) |
Session ID holding or having the lock#1 |
COPY |
ulong |
No |
All |
V$LOCK.SID |
|
Start Time (START_TIME) |
Collection start time for the performance data stored in the record#1 |
COPY |
time_t |
No |
All |
Agent Collector |
|
Type (TYPE) |
Lock type#1 |
COPY |
string(2) |
No |
All |
V$LOCK.TYPE |
|
Type Text (TYPE_TEXT) |
Details of lock type#1 |
COPY |
string(32) |
No |
All |
V$LOCK.TYPE |
|
User (USERNAME) |
Oracle user name#1 |
COPY |
string(30) |
No |
All |
V$SESSION.USERNAME where V$LOCK.SID = V$SESSION.SID |