Which are the three steps in the SQL tuning process for Oracle Database environments?

Question

Options

• ATune individual SQL statements using the SQL Tuning Advisor.
• BIdentify poorly tuned SQL statements using Automatic Database Diagnostic Monitor.
• CTest the application as a whole using tuned SQL statements.
• DTest tuned SQL statements one at a time for all statements in the application.
• EIdentify poorly tuned SQL statements using the SQL Tuning Advisor.
• FTune SQL statements as a group using the SQL Tuning and SQL Access Advisors.

• A
  89% (42)
• D
  2% (1)
• E
  6% (3)
• F
  2% (1)

Explanation

Oracle's SQL tuning process follows a three-step workflow: identify problematic statements with ADDM (B), tune them individually with the SQL Tuning Advisor (A), then test the full application with the tuned statements in place (C). ADDM is the diagnostic tool that surfaces poorly performing SQL, while the SQL Tuning Advisor does the actual optimization work - these roles are distinct, which is why E is wrong (it incorrectly assigns identification to the SQL Tuning Advisor). D is wrong because the final validation step tests the application as a whole, not statements in isolation one at a time. F is wrong because tuning is done on individual statements, not as a group - and while the SQL Access Advisor handles index/materialized view recommendations, it's not part of this three-step process definition.

Memory tip: Think "Find it, Fix it, Validate it" - ADDM finds the bad SQL, SQL Tuning Advisor fixes it, then you validate the whole application. The key trap is confusing ADDM (diagnosis) with SQL Tuning Advisor (remediation).

No community discussion yet for this question.