Testing Database Upgrades from Releases 10.2 and Higher Using Cloud Control

To test a database upgrade from Oracle Database 10g Release 2 or a newer release using SQL Performance Analyzer:

1. From the Performance menu, select SQL, then SQL Performance Analyzer.

   If the Database Login page appears, then log in as a user with administrator privileges.

   The SQL Performance Analyzer page appears.

2. Under SQL Performance Analyzer Workflows, click Upgrade from 10.2 or 11g.

   The Upgrade from 10.2 or 11g page appears.

   
   Description of the illustration spa_upgrade_102_11g.gif

3. Under Task Information:

   1. In the Task Name field, enter the name of the task.

   2. In the SQL Tuning Set field, enter the name of the SQL tuning set that was built.

      Alternatively, click the search icon to search for the SQL tuning set using the Search and Select: SQL Tuning Set window.

      The selected SQL tuning set now appears in the SQL Tuning Set field.

   3. In the Description field, optionally enter a description of the task.

4. In the Creation Method field, select:

   • Execute SQLs to generate both execution plans and statistics for each SQL statement in the SQL tuning set by actually running the SQL statements remotely on the test system over a public database link.

   • Generate Plans to create execution plans remotely on the test system over a public database link without actually running the SQL statements.

5. In the Per-SQL Time Limit list, determine the time limit for SQL execution during the trial by performing one of the following actions:

   • Select 5 minutes.

     The execution will run each SQL statement in the SQL tuning set up to 5 minutes and gather performance data.

   • Select Unlimited.

     The execution will run each SQL statement in the SQL tuning set to completion and gather performance data. Collecting execution statistics provides greater accuracy in the performance analysis but takes a longer time. Using this setting is not recommended because the task may be stalled by one SQL statement for a prolonged time period.

   • Select Customize and enter the specified number of seconds, minutes, or hours.

6. In the Database Link field, enter the global name of a public database link connecting to a user with the EXECUTE privilege for the DBMS_SQLPA package and the ADVISOR privilege on the pre-upgrade system.

   Alternatively, click the search icon to search for and select a database link, or click Create Database Link to create a database link using the Create Database Link page.

7. Under Post-upgrade Trial:

   1. Select Use the same system as in the pre-upgrade trial to use the same system for executing both the pre-upgrade and post-upgrade trials.

      Oracle recommends using this option to avoid possible errors due to different system configurations. When using this option, you will need to upgrade the test database to the higher database version before the post-upgrade trial is executed.

   2. In the Database Link field, enter the global name of a public database link connecting to a user with the EXECUTE privilege for the DBMS_SQLPA package and the ADVISOR privilege on the post-upgrade system.

8. In the Comparison Metric list, select the comparison metric to use for the comparison analysis:

   • Elapsed Time

   • CPU Time

   • User I/O Time

   • Buffer Gets

   • Physical I/O

   • Optimizer Cost

   • I/O Interconnect Bytes

   Optimizer Cost is the only comparison metric available if you generated execution plans only in the SQL trials.

   To perform the comparison analysis by using more than one comparison metric, perform separate comparison analyses by repeating this procedure with different metrics.

9. Under Schedule:

   1. In the Time Zone list, select your time zone code.

   2. Select Immediately to start the task now, or Later to schedule the task to start at a time specified using the Date and Time fields.

10. Click Submit.

    The SQL Performance Analyzer page appears.

    In the SQL Performance Analyzer Tasks section, the status of this task is displayed. To refresh the status icon, click Refresh.

    If you are using the same system to execute both the pre-upgrade and post-upgrade trials, you will need to upgrade the database after the pre-upgrade trial step is completed. After the database is upgraded, the post-upgrade trial can be executed. After the task completes, the Status field changes to Completed.

11. Under SQL Performance Analyzer Tasks, select the task and click the link in the Name column.

    The SQL Performance Analyzer Task page appears.

    This page contains the following sections:

    • SQL Tuning Set

      This section summarizes information about the SQL tuning set, including its name, owner, description, and the number of SQL statements it contains.

    • SQL Trials

      This section includes a table that lists the SQL trials used in the SQL Performance Analyzer task.

    • SQL Trial Comparisons

      This section contains a table that lists the results of the SQL trial comparisons

12. Click the icon in the Comparison Report column.

    The SQL Performance Analyzer Task Result page appears.

13. Review the results of the performance analysis, as described in "Reviewing the SQL Performance Analyzer Report Using Oracle Enterprise Manager".

    If regressed SQL statements are found following the database upgrade, tune them as described in "Tuning Regressed SQL Statements After Testing a Database Upgrade".