V$FALSE_PING

V$FALSE_PING is a Real Application Clusters view. This view displays buffers that may be getting false pings. That is, buffers pinged more than 10 times that are protected by the same lock as another buffer that pinged more than 10 times. Buffers identified as getting false pings can be remapped in "GC_FILES_TO_LOCKS" to reduce lock collisions.

Column	Datatype	Description
`FILE#`	`NUMBER`	Datafile identifier number (to find the filename, query `DBA_DATA_FILES` or `V$DBFILE`)
`BLOCK#`	`NUMBER`	Block number
`STATUS`	`VARCHAR2(6)`	Status of the block: `free` - Not currently in use `xcur` - Exclusive `scur` - Shared current `cr` - Consistent read `read` - Being read from disk `mrec` - In media recovery mode `irec` - In instance recovery mode
`XNC`	`NUMBER`	Number of PCM lock conversions from Exclusive mode due to contention with another instance. This column is obsolete and maintained for backward compatibility.
`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
`NAME`	`VARCHAR2(30)`	Name of the database object containing the block
`PARTITION_NAME`	`VARCHAR2(30)`	NULL for non-partitioned objects
`KIND`	`VARCHAR2(15)`	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`	Name of the lock that contains the PCM lock that is covering the buffer
`LOCK_ELEMENT_CLASS`	`NUMBER`	Lock element class

See Also:

"GC_FILES_TO_LOCKS" and Oracle Real Application Clusters Installation and Configuration Guide