Databases Reference
In-Depth Information
In steps 5 and 6 we observe the Latch Sleep breakdown and Latch Miss Sources to get
information on the events with the highest misses and the related source, as shown in the
next screenshot:
Using this section of the statspack report we can identify the events that are causing the
highest misses. In the above example, there were 341 misses (and 56 sleeps) on requests
involving latches on the shared pool, and 149 misses (and 2 sleeps) on requests for latches
on row cache objects.
There's more...
There are several types of latches on which we may experience contention. The most
common are the shared pool latches, identifying a problem related to the application.
Maybe the cursor cache is too small or we are explicitly closing cursors too soon—for
example after each execution.
 
Search WWH ::




Custom Search