How to Use SQL Plan Management (SPM) - Plan Stability Worked Example (Doc ID 456518.1)

Last updated on FEBRUARY 10, 2017

Applies to:

Oracle Database - Enterprise Edition - Version 11.1.0.6 and later
Information in this document applies to any platform.

Goal

SQL Plan management (SPM) is a preventative mechanism that records and evaluates the execution plans of SQL statements over time. SPM builds SQL plan baselines composed of a set of existing plans that are known to be efficient. The SQL plan baselines are then used to preserve performance of corresponding SQL statements, regardless of changes occurring in the system, providing "plan stability".

Common usage scenarios where SQL plan management can improve or preserve SQL performance include:

If you have a good plan in the cursor cache, then you can load these into SPM so that you can use this baseline to preserve the performance. The following example command illustrates this:

set serveroutput on

var n number
begin
:n:=dbms_spm.load_plans_from_cursor_cache(sql_id=>'&sql_id', plan_hash_value=>&plan_hash_value, fixed =>'NO', enabled=>'YES');
end;
/

EXEC dbms_output.put_line('Number of plans loaded: ' || :n);

After enabling the SPM, for those SQL ID's that have SQL plan management baselines, the database will not collect new access plans (even after SPM is disabled - assuming the baseline is active)

The purpose of this Document is to show an example of SQL PLAN MANAGEMENT.

NOTE: The steps to accept and un-accept the baseline have changed in 11gR2. For information on how to run these steps in 11gR2, please see:

<Document 1309799.1> How to Accept & Unaccept the plans in sql baselines in 11.2.0.1

 

Solution

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