Execution Plan Missing when SQL Tuning Set Transferred to a SQL Plan Baseline in Another Database
(Doc ID 1918196.1)
Last updated on NOVEMBER 07, 2023
Applies to:
Oracle Database - Enterprise Edition - Version 10.2.0.5 to 12.1.0.2 [Release 10.2 to 12.1]Oracle Database Cloud Schema Service - Version N/A and later
Gen 1 Exadata Cloud at Customer (Oracle Exadata Database Cloud Machine) - Version N/A and later
Oracle Cloud Infrastructure - Database Service - Version N/A and later
Oracle Database Backup Service - Version N/A and later
Information in this document applies to any platform.
Symptoms
- SQL tuning set is being used to transfer a specific execution plan from a source database into a SQL plan baseline of a target database using the method explain in:
<Document 801033.1> How to Load SQL Execution Plans in to a STS so that they can be Transferred (to 11g) and Loaded into a SQL Plan Baseline
- As the range of AWR snapshots during which time the query ran well is known, you extract the execution plan from the relevant AWR snapshots on the source database as follows:
The output above shows that the SQL_ID and Plan Hash Value (PHV) do, in fact, exist. However, as shown above, the "plan is missing," and "plans loaded=0."
Changes
None
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 |