QUESTION 202-latch:row cache objects、Cursors are not being shared./The shared pool size is too small

原创于 2021-06-26 22:30:56 发布 · 136 阅读

0 ·

CC 4.0 BY-SA版权

060 专栏收录该内容

230 篇文章

订阅专栏

本文探讨了AWR报告中排名前5的定时事件，重点是DBCPU和I/O等待。其中，DBCPU占据大部分DB时间，而latch相关的等待事件如行缓存对象和共享池 latch 引起的等待也占一定比例。这可能表明并发问题和资源竞争。解决方案可能包括优化查询以减少CPU使用，增大共享池大小，以及确保游标共享以减少闩锁争用。

摘要生成于 C知道，由 DeepSeek-R1 满血版支持，前往体验 >

Examine the details of the Top 5 Timed Events from an Automatic Workload Repository (AWR) report:
Top 5 Timed Foreground Events
Event Waits Time(s) Avg wait(ms) %DB time Wait Class

DBCPU 67 98.21
db file sequential read 8371 0 0 0.52 User l/O
latch:row cache objects 16 0 8 0.19 Concurrency
Latch:shared pool 956 0 0 0.15 Concurrency
log file sync 25 0 2 0.06 Commit

What are two possible causes for the latch-related wait events?
A. A large number of COMMITS are being performed.
B. A large number of ROLLBACKS are being performed.
C. Cursors are not being shared.
D. Database block images are being read into the buffer cache, which are then modified by other sessions.
E. The shared pool size is too small.
Correct Answer: CE