My Oracle Support Banner

How to Use ASH Report to Identify Hot Object for Dbms_shared_pool.markhot (Doc ID 2194448.1)

Last updated on MAY 26, 2023

Applies to:

Oracle Database - Enterprise Edition - Version 11.2.0.3 and later
Oracle Database Cloud Schema Service - Version N/A and later
Oracle Database Exadata Cloud Machine - Version N/A and later
Oracle Cloud Infrastructure - Database Service - Version N/A and later
Oracle Database Exadata Express Cloud Service - Version N/A and later
Information in this document applies to any platform.

Goal

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.

Solution

To view full details, sign in with your My Oracle Support account.

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

In this Document
Goal
Solution
References


My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.