A user session executes a query and the plan for the query is shown in the Exhibit as Plan-1. After verifying with the SQL Access advisor, an index is created on the table in the JOB_ID column and the query is executed again. A new plan is generated against the second query shown in the Exhibit as Plan-2. When explaining the plan for the second query, you observe that the optimizer uses the first plan instead of the second. The following parameters are set for the user session:

OPTIMIZER_CAPTURE_SQL_PLAN_BASELINES=TRUE OPTIMIZER_USE_SQL_PLAN_BASELINES=TRUE SQLTUNE_CATEGORY=DEFAULT Why does the optimizer not use the second plan?

Question

A user session executes a query and the plan for the query is shown in the Exhibit as Plan-1. After verifying with the SQL Access advisor, an index is created on the table in the JOB_ID column and the query is executed again. A new plan is generated against the second query shown in the Exhibit as Plan-2. When explaining the plan for the second query, you observe that the optimizer uses the first plan instead of the second. The following parameters are set for the user session:

OPTIMIZER_CAPTURE_SQL_PLAN_BASELINES=TRUE OPTIMIZER_USE_SQL_PLAN_BASELINES=TRUE SQLTUNE_CATEGORY=DEFAULT Why does the optimizer not use the second plan?

Accepted Answer

A. because the second plan is not verified

Answer

B. because the second plan is not part of the SQL plan baseline

Answer

C. because the SQLTUNE_CATEGORY parameter is set to DEFAULT

Answer

D. because the explain plan option in the user session does not allow the new plan because

A user session executes a query and the plan for the query is shown in the Exhibit as Plan-1. After verifying with the SQL Access advisor, an index is created on the table in the JOB_ID column and…

Question

Exhibit

Options

How the community answered

Community Discussion