V$CACHE_LOCK
is deprecated. The information that was provided in this view is now provided in the V$INSTANCE_CACHE_TRANSFER
and V$SEGMENT_STATISTICS
views.
Column | Datatype | Description |
---|---|---|
FILE# |
NUMBER |
Datafile identifier number (to find filename, query DBA_DATA_FILES or V$DBFILE ) |
BLOCK# |
NUMBER |
Block number |
STATUS |
VARCHAR2(6) |
Status of the block:
|
XNC |
NUMBER |
Number of parallel cache management (PCM) lock conversions due to contention with another instance |
NAME |
VARCHAR2(30) |
Name of the database object containing the block |
KIND |
VARCHAR2(12) |
Type of database object:
|
OWNER# |
NUMBER |
Owner number |
LOCK_ELEMENT_ADDR |
RAW(4 | 8) |
Address of the lock element that contains the PCM lock that is covering the buffer. If more than one buffer has the same address, then these buffers are covered by the same PCM lock. |
LOCK_ELEMENT_NAME |
NUMBER |
Address of the lock element that contains the PCM lock that is covering the buffer. If more than one buffer has the same address, then these buffers are covered by the same PCM lock. |
FORCED_READS |
NUMBER |
Number of times the block had to be reread from the cache because another instance has forced it out of this instance's cache by requesting the lock on the block in exclusive mode |
FORCED_WRITES |
NUMBER |
Number of times GCS had to write this block to cache because this instance had used the block and another instance had requested the lock on the block in a conflicting mode |
INDX |
NUMBER |
Platform-specific lock manager identifier |
CLASS |
NUMBER |
Platform-specific lock manager identifier |