You need to migrate database from oracle Database 10g to 11g. You want the SQL workload to
start the 10g plans in the 11g database instance and evolve better plans.
Examine the following steps:
1. Capture the pre-Oracle Database 11g plans in a SQL Tuning Set (STS)
2. Export the STS from the 10g system.
3. Import the STS into Oracle Database 11g.
4. Set the OPTIMIZER_FEATURES_ENABLE parameter to 10.2.0.
5. Run SQL Performance Analyzer for the STS.
6. Set the OPTIMIZER_FEATURES_ENABLE parameter to 11.2.0.
7. Rerun the SQL Performance Analyzer for the STS.
8. Set OPTIMIZER_CAPTURE_SQL_PLAN_BASELINE to TRUE.
9. Use DBMS_SPM.EVOLVE_SQL_BASELINE function to evolve the plans.
10. Set the OPTIMIZER_USE_SQL_PLAN_BASELINE to TRUE.
Identify the required steps in the correct order.
A.
1, 2, 3, 4, 5, 6, 7,
B.
4, 8, 10
C.
1, 2, 3, 4, 8, 10
D.
1, 2, 3, 6, 9, 5
E.
1, 2, 3, 5, 9, 10
Explanation:
Step 1: (1)
Step 2: (2)
Step 3: (3)
Step 4: (4)
By setting the parameter OPTIMIZER_FEATURES_ENABLE to the 10g version used before the
upgrade, you should be able to revert back to the same execution plans you had prior to the
upgrade.
Step 5: (8)
OPTIMIZER_CAPTURE_SQL_PLAN_BASELINES
In Oracle Database 11g a new feature called SQL Plan Management (SPM) has been introduced
to guarantees any plan changes that do occur lead to better performance. When
OPTIMIZER_CAPTURE_SQL_PLAN_BASELINES is set to TRUE (default FALSE) Oracle will
automatically capture a SQL plan baseline for every repeatable SQL statement on the system.
The execution plan found at parse time will be added to the SQL plan baseline as an accepted
plan.
Step 6: (10)
OPTIMIZER_USE_SQL_PLAN_BASELINES enables or disables the use of SQL plan baselines
stored in SQL Management Base. When enabled, the optimizer looks for a SQL plan baseline for
the SQL statement being compiled. If one is found in SQL Management Base, then the optimizer
will cost each of the baseline plans and pick one with the lowest cost.
А (The answer should be 1,2,3,4,5,6,7,8).
From the Sql Tuning Workshop:
A variation of the first method described in the previous slide is through the use of SQL Performance Analyzer. You can capture pre–Oracle Database 11g plans in an STS (step 1,2) and import them into Oracle Database 11g (step 3). Then set the optimizer_features_enable (O_F_E) initialization parameter to 10.1.0 (step 4) to make the optimizer behave as if this were a 10g Oracle Database. Next run SQL Performance Analyzer for the STS (step 5). When that is complete, set the optimizer_features_enable initialization parameter back to 11.2.0 (step 6) and rerun SQL Performance Analyzer for the STS (step 7). SQL Performance Analyzer produces a report that lists a SQL statement whose plan has regressed from 10g to 11g. For those SQL statements that are shown by SQL Performance Analyzer to incur performance regression due to the new optimizer version, you can capture their plans (step 8) using an STS and then load them into the SMB.
An STS includes:
Associated execution plans and row source statistics for each SQL statement (optional)
A