Which statement is true about an SQL plan baselines that are fixed?

Question

Options

• ANew plans are added automatically by the optimizer to the baseline and are automatically evolved.
• BNew, better plans are added automatically as a fixed plan baseline.
• CNew plan can be manually loaded to the baseline from the cursor cache or a SQL tuning set.
• DNew plans can be added as fixed plans to the baseline by using the SQL Tuning Advisor to generate a

• A
  6% (2)
• B
  10% (3)
• C
  3% (1)
• D
  81% (25)

Explanation

When a SQL statement with a fixed SQL plan baseline is tuned using the SQL Tuning Advisor, a SQL profile recommendation has special meaning. When the SQL profile is accepted, the tuned plan is added to the fixed SQL plan baseline as a non-fixed plan. However, as described above, the optimizer will not use the tuned plan as long as a reproducible fixed plan is present. Therefore, the benefit of SQL tuning may not be realized. To enable the use of the tuned plan, manually alter the tuned plan to a fixed plan by setting its FIXED attribute to YES. It is also possible to influence the optimizer's choice of plan when it is selecting a plan from a SQL plan baseline. SQL plan baselines can be marked as fixed. Fixed SQL plan baselines indicate to the optimizer that they are preferred. If the optimizer is costing SQL plan baselines and one of the plans is fixed, the optimizer will only cost the fixed plan and go with that if it is reproducible. If the fixed plan(s) are not reproducible the optimizer will go back and cost the remaining SQL plan baselines and select the one with the lowest cost. Note that costing a plan is nowhere near as expensive as a hard parse. The optimizer is not looking at all possible access methods but at one specific access path.

No community discussion yet for this question.