Oracle 视图 V$CACHE_LOCK 官方解释,作用,如何使用详细说明
本站中文解释
_DATA
V$CACHE_LOCK_DATA视图可以提供缓存中锁定数据的信息,帮助用户识别存在的锁定,确定锁定的原因及影响。
V$CACHE_LOCK_DATA视图主要涉及以下几列:
ADDR : 指向锁定数据的指针地址;
HASH_VALUE : 用来计算缓存锁的唯一散列值;
KADDR1、KADDR2 : 指向两个锁定持有者的指针地址;
REQUEST : 指定数据库锁的请求模式;
TYPE : 指定数据库锁的类型;
SID : 会话ID,持有该锁的会话编号;
SERIAL# : 序列号,关联的会话的事务号。
如果要使用V$CACHE_LOCK_DATA视图,必须拥有全局以及调试资格(SELECT ANY DICTIONARY系统权限),并且赋予V$SESSION_LONGOPS视图,V$SESSION视图,V$SESSION_WAIT视图的权限。此外,该视图只能由SYSDBA用户查询,因此,用户必须拥有这种权限。
使用V$CACHE_LOCK_DATA视图前,可以通过V$CACHE_LOCK_DATA动态性能视图,来查询缓存中锁定数据的资源数据,从而识别并分析存在的锁定,有助于确定锁定的原因及影响,从而帮助应用程序的优化。
官方英文解释
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 |
---|---|---|
|
|
Data file identifier number (to find file name, query |
|
|
Block number |
|
|
Status of the block:
|
|
|
Number of parallel cache management (PCM) lock conversions due to contention with another instance |
|
|
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 |
|
|
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 |
|
|
Name of the database object containing the block |
|
|
Type of database object:
|
|
|
Owner 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. |
|
|
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. |
|
|
Platform-specific lock manager identifier |
|
|
Platform-specific lock manager identifier |
|
|
The ID of the container to which the data pertains. Possible values include:
|