How does this impact the created SQL profile?

You ran a high load SQL statement that used an index through the SQL Tuning Advisor and
accepted its recommendation for SQL profile creation. Subsequently you noticed that there has
been a 2% growth in number of rows in the tables used by the SQL statement and database
statistics have also been refreshed.
How does this impact the created SQL profile?

You ran a high load SQL statement that used an index through the SQL Tuning Advisor and
accepted its recommendation for SQL profile creation. Subsequently you noticed that there has
been a 2% growth in number of rows in the tables used by the SQL statement and database
statistics have also been refreshed.
How does this impact the created SQL profile?

A.
It becomes invalid and no longer used the optimizer.

B.
It remains valid and ensures that the optimizer always use the execution plan that was created
before the changes happened.

C.
It remains and allows the optimizer to pick a different plan required.

D.
It becomes invalid and a new SQL profile is created for the statement by the auto tuning task.

Explanation:

Show Hint

Leave a Reply 1

Your email address will not be published. Required fields are marked *

raka

raka

Agree with C

Explain here:

https://docs.oracle.com/database/121/TGSQL/tgsql_profiles.htm#TGSQL599

If either the optimizer environment or SQL profile change, then the optimizer can create a new plan. As tables grow, or as indexes are created or dropped, the plan for a SQL profile can change. The profile continues to be relevant even if the data distribution or access path of the corresponding statement changes. In general, you do not need to refresh SQL profiles.

Reply