DBA AWR System Time Percentages – Oracle EBS SQL Report
Oracle E-Business Suite SQL report from the Enginatics Library powered by Blitz Report™.
Overview
Historic system time model values from the automated workload repository showing a breakdown of how much percent of the database time was spent e.g. on excuting SQL, PL/SQL or Java code, parsing statements etc..
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, Time Split, Diagnostic Pack enabled, Container Data
Oracle EBS Tables Used
dba_hist_snapshot, dba_hist_sys_time_model
Report Categories
Related Reports
DBA AWR CPU vs Wait Time Summary, DBA AWR System Time Summary, 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 System Time Percentages 22-Dec-2025 083614.xlsx |
| Blitz Report™ XML Import | DBA_AWR_System_Time_Percentages.xml |
| Full SQL on Enginatics | www.enginatics.com/reports/dba-awr-system-time-percentages/ |
Executive Summary
The DBA AWR System Time Percentages report provides a proportional breakdown of how the database spends its time. Instead of raw seconds, it shows percentages (e.g., “80% SQL Execution, 10% Parsing, 5% PL/SQL”). This is crucial for understanding the nature of the workload. For example, a system spending 40% of its time on “Hard Parse” indicates a code quality issue (lack of bind variables), whereas 90% “SQL Execution” suggests a need for SQL tuning or more hardware.
Business Challenge
- Workload Characterization: “Is our system mostly doing calculation (CPU) or waiting for data (I/O)?”
- Code Quality Audit: “Are we wasting resources on overhead tasks like parsing and connection management?”
- Tuning Focus: “Should we focus on optimizing PL/SQL loops or SQL queries?”
Solution
This report calculates the percentage contribution of each time model statistic to the total DB Time.
Key Features:
- SQL Execution Time %: Time spent actually running queries.
- Parse Time %: Time spent compiling SQL (Hard vs. Soft).
- PL/SQL Execution Time %: Time spent in procedural logic.
- Connection Management %: Time spent logging on/off.
Architecture
The report queries DBA_HIST_SYS_TIME_MODEL.
Key Tables:
DBA_HIST_SYS_TIME_MODEL: Historical time model statistics.
Impact
- Strategic Tuning: Directs tuning efforts to the area with the biggest potential ROI (e.g., fixing parsing issues can double throughput).
- Application Profiling: Helps developers understand the behavior of their application code.
- Anomaly Detection: A sudden spike in “Sequence Load” or “Failed Parse” indicates a specific application bug.
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