You want to upgrade your pre-12c database to an Oracle 12c database. You set up the test environment and replay the captured workload from the production database on the test machine twice with a…

Reviewing raw database time consumed per period is a function of standard ADDM or AWR snapshot reports; the Compare Period ADDM is designed to analyze the difference between periods, not report absolute time values for each.

Comparing initialization parameter changes between runs is handled through AWR comparison or DBA_HIST_PARAMETER views, not through the Compare Period ADDM report, which focuses on workload performance differences.

The Compare Period ADDM report specifically identifies SQL statements that appear in both capture periods and reports on their relative resource consumption, allowing reviewers to see which shared workloads improved or worsened.

A primary purpose of the Compare Period ADDM report is to surface findings about performance improvements and degradations caused by the change - such as an upgrade or configuration difference - making it directly suited for this upgrade validation scenario.

The Compare Period ADDM report includes a side-by-side comparison of hardware resource utilization such as CPU, I/O throughput, and memory across the two replay periods, revealing whether the upgrade altered the resource profile.

Ranking the top SQL statements by resource usage within each individual period is a standard ADDM or AWR Top SQL function; Compare Period ADDM focuses on SQL common to both periods and overall differential findings rather than per-period top lists.