DBA AWR CPU vs Wait Time Summary – Oracle EBS SQL Report
Oracle E-Business Suite SQL report from the Enginatics Library powered by Blitz Report™.
Overview
Summary of database CPU vs. wait times and average active sessions for a specified time frame
To see data in this report based on dba_hist_sys_time_model, set the following: alter session set container=PDB1; alter system set awr_pdb_autoflush_enabled=true;
https://www.enginatics.com/blog/updated-dba-awr-blitz-reports-now-work-with-plugglable-databases/
Report Parameters
Date From, Date To, Level of Detail, Request Id (Time Restriction), Time Restriction, Diagnostic Pack enabled, Container Data
Oracle EBS Tables Used
dba_hist_snapshot, dba_hist_sys_time_model
Report Categories
Related Reports
DBA AWR System Time Summary, DBA AWR System Time Percentages, DBA AWR Blocking Session Summary, DBA AWR SQL Performance Summary, DBA AWR Settings, DBA SGA+PGA Memory Configuration, DBA AWR Active Session History, DBA AWR System Metrics Summary, DBA AWR Wait Event Summary
Running This SQL Without Blitz Report
Some Oracle EBS SQL reports in this library require functions from the utility package xxen_util. Install it before running the SQL directly against your Oracle EBS database.
Download & Import Options
| Resource | Link |
|---|---|
| Excel Example Output | DBA AWR CPU vs Wait Time Summary 22-Dec-2025 083306.xlsx |
| Blitz Report™ XML Import | DBA_AWR_CPU_vs_Wait_Time_Summary.xml |
| Full SQL on Enginatics | www.enginatics.com/reports/dba-awr-cpu-vs-wait-time-summary/ |
Executive Summary
The DBA AWR CPU vs Wait Time Summary report provides a high-level “health check” of the database workload. It compares the time spent on CPU (doing work) versus the time spent waiting (for I/O, locks, network, etc.). This ratio is the fundamental starting point for any performance tuning exercise: “Is the problem that we are doing too much work (CPU), or that we are waiting too long for resources (Wait)?”
Business Challenge
- Problem Classification: “Is the database slow because of slow disks (Wait) or inefficient code (CPU)?”
- Workload Profiling: Understanding if the system is “CPU Bound” or “I/O Bound”.
- Trend Analysis: Seeing how the workload profile changes over time (e.g., after a storage migration).
Solution
This report summarizes the “System Time Model” statistics from AWR.
Key Features:
- DB Time Breakdown: Shows the total “DB Time” split into CPU Time and Wait Time.
- Average Active Sessions (AAS): Calculates the AAS metric, a key indicator of system load relative to capacity.
- PDB Support: Can report on Pluggable Databases (PDBs) if configured.
Architecture
The report queries DBA_HIST_SYS_TIME_MODEL.
Key Tables:
DBA_HIST_SYS_TIME_MODEL: Stores system-wide time statistics.DBA_HIST_SNAPSHOT: Snapshot timing details.
Impact
- Strategic Tuning: Directs tuning efforts to the right area (e.g., don’t buy faster disks if the problem is 90% CPU).
- Performance Baselines: Establishes a baseline for “normal” behavior to compare against during incidents.
- Executive Reporting: Provides a simple, high-level metric (CPU vs. Wait) that is easy to explain to management.
Useful Links
- Blitz Report™ – World’s Fastest Oracle EBS Reporting Tool
- Oracle Discoverer Replacement – Import Worksheets into Blitz Report™
- Oracle EBS Reporting Toolkits by Blitz Report™
- Blitz Report™ FAQ & Community Q&A
- Supply Chain Hub by Blitz Report™
- Blitz Report™ Customer Case Studies
- Oracle EBS Reporting Blog
- Oracle EBS Reporting Resource Centre
© 2026 Enginatics