Different Sql_id's But Sql Is The Same Text When Sql Is Marked Hot
Last updated on JUNE 23, 2018
Applies to:Oracle Database - Enterprise Edition - Version 18.104.22.168 and later
Information in this document applies to any platform.
- 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
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
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