Different Sql_id's But Sql Is The Same Text When Sql Is Marked Hot
(Doc ID 2234171.1)
Last updated on DECEMBER 31, 2024
Applies to:
Oracle Database Exadata Cloud Machine - Version N/A and laterOracle Cloud Infrastructure - Database Service - Version N/A and later
Oracle Database Cloud Exadata Service - Version N/A and later
Oracle Database Exadata Express Cloud Service - Version N/A and later
Oracle Database Cloud Schema Service - Version N/A and later
Information in this document applies to any platform.
Symptoms
- There are different SQL_ID's for same SQL Text
- This is causing more parses
- Package Dbms_shared_pool.markhot is used to mark a sql as hot
Changes
Marked SQL statements with package dbms_shared_pool.markhot, as HOT to help reduce library cache: mutex X contention.
You can check if the statement is markhot by the PROPERTY column in view GV$DB_OBJECT_CACHE. Possible values are:
HOTCOPYnnn - An object that is a hot copy with integer identifier of 'nnn'. Examples are HOTCOPY5, HOTCOPY94 and HOTCOPY125. HOTCOPY - As above but the identifier is unknown HOT - The "root" kgl object that has been marked as hot NULL - A normal object
Cause
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
| Symptoms |
| Changes |
| Cause |
| Solution |
| References |