How to Use ASH Report to Identify Hot Object for Dbms_shared_pool.markhot

(Doc ID 2194448.1)

Last updated on OCTOBER 24, 2016

Applies to:

Oracle Database - Enterprise Edition - Version and later
Information in this document applies to any platform.


The wait events on mutex contention and library cache latches/lock often have common root causes.

Sometimes this kind of contention can be caused by "hot" object issues, meaning the application just makes too many calls to a cursor or PL/SQL procedure.


Sign In with your My Oracle Support account

Don't have a My Oracle Support account? Click to get started

My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms