gc buffer busy等待事件
原创maclean_007 ©著作权
©著作权归作者所有:来自51CTO博客作者maclean_007的原创作品,请联系作者获取转载授权,否则将追究法律责任
This wait, also known as global cache buffer busy prior to Oracle 10g, specifies the time the remote instance locally spends accessing the requested data block. This wait event is very similar to the buffer busy waits wait event in a single-instance database.
Problem
High wait times on this event are often the result of:
Hot Blocks - multiple sessions may be requesting a block that is either not in buffer cache or is in an incompatible mode.
Inefficient Queries- as with the gc cr request wait event, the more blocks requested from the buffer cache the more likelihood of a session having to wait for other sessions.
Solutions
Deleting some of the hot rows and re-inserting them back into the table may alleviate a Hot Block problem. Most of the time the rows will be placed into a different block and reduce contention on the block. The DBA may also need to adjust the pctfree and/or pctused parameters for the table to ensure the rows are placed into a different block.
Tuning queries to access fewer blocks in buffer cache will often result in less contention for the same block.
提问和评论都可以,用心的回复会被更多人看到
评论
发布评论
相关文章
-
【Oracle数据库技术支持】RAC性能分析 - gc buffer busy acquire 等待事件
ion#...
数据库 oracle 解决方法 -
Oracle RAC 全局等待事件 gc current block busy 和 gc cr multi block request 说明
一.RAC 全局等待事件说明在RAC环境中,和全局调整缓存相关的最常见的等待事件
oracle cache session buffer asynchronous