latch: row cache objects等待事件
2011-08-09 10:53
344 查看
This latch comes into play when user processes are attempting to access or update the cached data dictionary values.
Solutions
Problem:
To determine if the row cache is being used efficiently, execute the following SQL. If the ratio is not close to 1 then some tuning required.
SELECT parameter, sum(gets), sum(getmisses),
100*sum(gets - getmisses) / sum(gets) pct_succ_gets,
sum(modifications) updates
FROM V$ROWCACHE
WHERE gets > 0
GROUP BY parameter;
Options for tuning row cache are so limited that some resources call it non-tunable. However if the value of the column pct_succ_gets in the above query is not close to "1" or if Ignite for Oracle shows significant waits for the "Row Cache Objects" latch, then consider increasing SHARED_POOL_SIZE.
Another way to adjust the dictionary cache is to increase the library cache. Since the dictionary cache is a part of the library cache, the increase will indirectly increase the dictionary cache. Also, consider the following:
Using Locally Managed tablespaces for application objects, especially indexes, may decrease Row Cache locks.
Review and amend database logical design. For example, try to decrease the number of indexes on tables with frequent inserts.本文出自 “Ask Maclean Liu Oracle” 博客,请务必保留此出处http://maclean.blog.51cto.com/2923249/1277935
Solutions
Problem:
To determine if the row cache is being used efficiently, execute the following SQL. If the ratio is not close to 1 then some tuning required.
SELECT parameter, sum(gets), sum(getmisses),
100*sum(gets - getmisses) / sum(gets) pct_succ_gets,
sum(modifications) updates
FROM V$ROWCACHE
WHERE gets > 0
GROUP BY parameter;
Options for tuning row cache are so limited that some resources call it non-tunable. However if the value of the column pct_succ_gets in the above query is not close to "1" or if Ignite for Oracle shows significant waits for the "Row Cache Objects" latch, then consider increasing SHARED_POOL_SIZE.
Another way to adjust the dictionary cache is to increase the library cache. Since the dictionary cache is a part of the library cache, the increase will indirectly increase the dictionary cache. Also, consider the following:
Using Locally Managed tablespaces for application objects, especially indexes, may decrease Row Cache locks.
Review and amend database logical design. For example, try to decrease the number of indexes on tables with frequent inserts.本文出自 “Ask Maclean Liu Oracle” 博客,请务必保留此出处http://maclean.blog.51cto.com/2923249/1277935
相关文章推荐
- latch: row cache objects等待事件
- latch row cache objects 等待事件 说明
- 遇到latch: row cache objects等待事件
- latch: row cache objects
- library cache latch等待事件
- Oracle latch: row cache objects系统整体慢
- latch:row cache objects
- latch: cache buffers chains (cbc)等待事件
- latch:library cache lock等待事件
- cache buffers LRU chain latch等待事件
- latch: library cache pin等待事件
- Latch Row Cache Objects基本信息的确认
- cache buffers chains latch等待事件
- Latch Row Cache Objects基本信息的确认
- library cache latch等待事件
- 等待事件:latch:cache buffer chains
- latch:library cache lock等待事件
- cache buffers LRU chain latch等待事件
- Oracle 11.2.0.3数据库CJQ进程造成row cache lock等待事件影响job无法停止问题分析
- latch: library cache pin等待事件