gc cr request等待事件

简介:

The session is looking for a consistent read version of data but cannot find it in the local cache. The local instance has made a request to other RAC instances for the data and is waiting on its return. Solutions Collect more information about the average time the instances are waiting for this type of request: select b1.inst_id, b2.value 'GCS CR BLOCKS RECEIVED', b1.value 'GCS CR BLOCK RECEIVE TIME', ((b1.value / b2.value) * 10) 'AVG CR BLOCK RECEIVE TIME (ms)' from gv$sysstat b1, gv$sysstat b2 where b1.name = 'global cache cr block receive time' and b2.name = 'global cache cr blocks received' and b1.inst_id = b2.inst_id; If the average cr block receive time is more than 15 milliseconds, this implies the session is waiting excessively for the block request to be satisfied by other instances. If the average time is less, that implies an excessive amount of block requests are occurring.


本文转自maclean_007 51CTO博客,原文链接:http://blog.51cto.com/maclean/1277928

相关文章
|
9月前
运行项目错误:资源繁忙或者锁定Error: EBUSY:resource busy or locked.lstat
运行项目错误:资源繁忙或者锁定Error: EBUSY:resource busy or locked.lstat
169 0
|
10月前
|
存储 算法 Java
CMS 触发GC(Allocation Failure)解析
针对GC中发生的"Allocation Failure"
441 0
|
SQL 索引 关系型数据库
生产 latch: cache buffers chains等待事件分析
生产 latch: cache buffers chains等待事件分析 一,表面现象:某库CPU冲高,大量latch: cache buffers chains等待事件。
1066 0
|
Java 数据库管理 关系型数据库
|
SQL 关系型数据库 Oracle