gc buffer busy
  This wait event, 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 asingle-instance database and are often the result of: 1. Hot Blocks -
multiple sessions may be requesting a block that is either not in buffer cache or is in an incompatible mode.
Deleting some of the hot rows and re-inserting them back into the table may alleviate the 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. 2. 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.Tuning queries to access
fewer blocks will often result in less contention for the same block.

十载的诸城网站建设经验，针对设计、前端、开发、售后、文案、推广等六对一服务，响应快，48小时及时工作处理。网络营销推广的优势是能够根据用户设备显示端的尺寸不同，自动调整诸城建站的显示方式，使网站能够适用不同显示终端，在浏览器中调整网站的宽度，无论在任何一种浏览器上浏览网站，都能展现优雅布局与设计，从而大程度地提升浏览体验。创新互联建站从事“诸城网站设计”,“诸城网站推广”以来，每个客户项目都认真落实执行。

本文名称：gcbufferbusy
网页链接：http://pwwzsj.com/article/pdjoch.html