What can be the three possible causes for the latch-related wait events?

View the Exhibit and examine the details of the Top 5 Timed Events from an Automatic Workload
Repository (AWR) report.

What can be the three possible causes for the latch-related wait events? (Choose three.)

View the Exhibit and examine the details of the Top 5 Timed Events from an Automatic Workload
Repository (AWR) report.

What can be the three possible causes for the latch-related wait events? (Choose three.)

A.
Shared pool size is too small.

B.
Cursors are not being shared.

C.
There are frequent logons/logoffs.

D.
A large number of COMMITs are being performed.

E.
A large number of data definition language (DDL) and query statements are being executed
simultaneously by different sessions.



Leave a Reply 4

Your email address will not be published. Required fields are marked *


shklifo

shklifo

For me are for sure A,B and E.
Those latch are always related to small shared pool size, not cursor sharing (hard parse) and contentions on library cache.

L. Zhu

L. Zhu

A is right
B is right. not shared, Latch: share pool
C is wrong.
D is wrong. commit?
E is right. concurrency

domq

domq

freq logon/logoff aren`t combine with dc_users in v$rowcache?