Accessing Workload Replay Reports Using Enterprise Manager

From the Enterprise menu of the Enterprise Manager Cloud Control console, select Quality Management, then Database Replay.

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

The Database Replay page appears.

Click the Replay Tasks tab, then select a replay for which you want to access reports.

Click the Reports tab to gain access to individual reports.

There are several types of reports you can view for a completed workload replay:

• Database Replay

  Use this report to view complete replay statistics in a tabular format, including replay divergence and the workload profile.

  
  Description of the illustration dbr_replay_replay_rep.gif

• Compare Period ADDM

  Use this report to perform a high-level comparison of one workload replay to its capture or to another replay of the same capture. Only workload replays that contain at least 5 minutes of database time can be compared using this report.

  
  Description of the illustration dbr_replay_addm_rep.gif

  Examine the following sections of the report to understand the performance change between the two periods and the cause of the change:

  • Overview

    This portion of the report shows SQL commonality, which is the comparability between the base and comparison periods based on the average resource consumption of the SQL statements common to both periods.

    A commonality value of 100% means that the workload "signature" in both time periods is identical. A commonality of 100% is expected for this use case, because the workload being replayed is the same (assuming that you are not using replay filters). A value of 0% means that the two time periods have no items in common for the specific workload dimension.

    Commonality is based on the type of input (that is, which SQL is executing) as well as the load of the executing SQL statements. Consequently, SQL statements running in only one time period, but not consuming significant time, do not affect commonality. Therefore, two workloads could have a commonality of 100% even if some SQL statements are running only in one of the two periods, provided that these SQL statements do not consume significant resources.

  • Configuration

    The information displayed shows base period and comparison period values for various parameters categorized by instance, host, and database.

  • Findings

    The findings can show performance improvements and identify the major performance differences caused by system changes. For negative outcomes, if you understand and remove the cause, the negative outcome can be eliminated.

    The values shown for the Base Period and Comparison Period represent performance with regard to database time.

    The Change Impact value represents a measurement of the scale of a change in performance from one time period to another. It is applicable to issues or items measured by the total database time they consumed in each time period. The absolute values are sorted in descending order.

    If the value is positive, an improvement has occurred, and if the value is negative, a regression has occurred. For instance, a change impact of -200% means that period 2 is three times as slow as period 1.

    You can run performance tuning tools, such as ADDM and the SQL Tuning Advisor, to fix issues in the comparison period to improve general system performance.

  • Resources

    The information shown provides a summary of the division of database time for both time periods, and shows the resource usage for CPU, memory, I/O, and interconnect (Oracle RAC only).

• SQL Performance Analyzer

  Use this report to compare a SQL tuning set from a workload capture to another SQL tuning set from a workload replay, or two SQL tuning sets from two workload replays. Comparing SQL tuning sets with Database Replay provides more information than SQL Performance Analyzer test-execute, because it considers and shows all execution plans for each SQL statement, while SQL Performance Analyzer test-execute generates only one execution plan per SQL statement for each SQL trial.

• Replay Compare Period

  Use this report to compare the AWR data from one workload replay to its capture or to another replay of the same capture. Before running this report, AWR data for the captured or replayed workload must have been previously exported.

  
  Description of the illustration dbr_replay_compare_per_rep.gif

  For information about using this report, see "Reviewing Replay Compare Period Reports". For information about how to interpret replay compare period reports, see Oracle Database 2 Day + Performance Tuning Guide.

• Replay ASH Analytics

  The Replay ASH Analytics report contains active session history (ASH) information for a specified duration of a workload that was replayed for the category you selected in the drop-down menu. Before running this report, AWR data must have been previously exported from the captured or replayed workload.

  
  Description of the illustration dbr_replay_ash_anal_rep.gif

  The chart shows workload activity breakdown values for wait classes, and provides detailed statistics for the top activity sessions that are adversely affecting the system.

  You can optionally use the Load Map for a graphical view of system activity. The Load Map is useful for viewing activity in a single- or multi-dimensional layout when you are not interested in seeing how activity has changed over time within the selected period.

  For more information about this report, see the Oracle Database 2 Day + Performance Tuning Guide.