Skip to Main Content

License Details

Buttons

License Details Container

Feature
SQL Plan Management
Functional Category
Manageability
Available On
Oracle Database FREE (Yes)
Standard Edition 2 (Yes)
Enterprise Edition (Yes)
Oracle Database Appliance (Yes)
Exadata (Yes)
Exadata Database Service on Dedicated Infrastructure / Cloud@Customer (Yes)
Oracle Base Database Service Standard Edition (Yes)
Oracle Base Database Service Enterprise Edition (Yes)
Oracle Base Database Service Enterprise Edition - High Performance (Yes)
Oracle Base Database Service Enterprise Edition - Extreme Performance (Yes)
Notes

SQL Plan Management does not require a license for Oracle Diagnostics Pack or Oracle Tuning Pack

SE2 and BaseDB SE: This feature is available in the SE2 and BaseDB SE offerings starting with Oracle Database 18c. Only one SQL plan baseline per SQL statement is allowed and SQL plan evolution is disabled.

Details:

  1. SQL plan baselines can be created or captured using the following methods:
    • Auto capture (OPTIMIZER_CAPTURE_SQL_PLAN_BASELINE=TRUE)
    • Manual loading from the cursor cache (DBMS_SPM.LOAD_PLANS_FROM CURSOR_CACHE)
    • Migration from stored outlines (DBMS_SPM.MIGRATE_STORED_OUTLINE)
    • Import using DBMS_SPM.UNPACK_STGTAB_BASELINE
  2. All capture and creation methods store only one SQL plan baseline per SQL statement.
  3. SQL plan baselines can be exported and imported using DBMS_SPM.CREATE_STGTAB_BASELINE, DBMS_SPM.PACK_STGTAB_BASELINE, and DBMS_SPM.UNPACK_STGTAB_BASELINE.
  4. Unused SQL plan baselines are not auto-purged.
  5. Alternative SQL execution plans for SQL statements are not added to the SQL plan history.
  6. SQL plan baselines can be altered and dropped (DBMS_SPM.ALTER_SQL_PLAN_BASELINE and DBMS_SPM.DROP_SQL_PLAN_BASELINE).
  7. The following DBMS_SPM functions and procedures are not allowed: CONFIGURE, LOAD_PLANS_FROM_AWR, LOAD_PLANS_FROM_SQLSET, and all functions and procedures associated with SQL plan evolution.