1Z0-054 · Question #38
You used SQL Tuning Advisor for a long-running SQL statement that suggested a SQL profile which can be used by the query subsequently for a better execution plan. After implementing the profile, you…
The correct answer is C. The SQLTUNE_CATEGORY parameter is set to DEFAULT for the user session. See the full explanation below for the reasoning.
Question
You used SQL Tuning Advisor for a long-running SQL statement that suggested a SQL profile which can be used by the query subsequently for a better execution plan. After implementing the profile, you altered the profile to include it in a category as follows:
SQL> EXEC DBMS_SQLTUNE.ALTER_SQL_PROFILE ( name=> 'SYS_SQLPROF_0146ced728214000, attribute_name => 'CATEGORY', value => 'DEV2'). But the performance has not improved for the user session. The profile is enabled and on investigating the query plan, you find that the query from the user session does not use the SQL profile. View the Exhibit and examine the parameters for the user session. What could be the reason for this?
Exhibit
Options
- AThe CONTROL_MANAGEMENT_PACK_ACCESS parameter is not set to DEV2.
- BThe OPTIMIZER_MODE parameter is set to ALL_ROWS for the user session.
- CThe SQLTUNE_CATEGORY parameter is set to DEFAULT for the user session.
- DThe OPTIMIZER_USE_PLAN_BASELINES parameter is set to TRUE for the user session.
How the community answered
(28 responses)- A11% (3)
- B4% (1)
- C82% (23)
- D4% (1)
Community Discussion
No community discussion yet for this question.
