DBA AWR System Time Summary – Oracle EBS SQL Report
Oracle E-Business Suite SQL report from the Enginatics Library powered by Blitz Report™. Oracle EBS module: Database Administration · all Database Administration reports
Overview
Historic system time model values from the automated workload repository showing how 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;
Run this report in Excel in seconds: download Blitz Report™ free (your first 30 reports are free) or try it in the online demo.
Report Parameters
Date From, Date To, Display Mode, 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 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
The SQL source can be run in any SQL client. Some Oracle EBS SQL reports in this library use functions from the utility package xxen_util – install it first. Blitz Report™ adds parameters, Excel output with pivots, scheduling and security on top.
Download & Import Options
| Resource | Link |
|---|---|
| Excel Example Output | DBA AWR System Time Summary 13-Jul-2018 173230.xlsx |
| Blitz Report™ XML Import | DBA_AWR_System_Time_Summary.xml |
| SQL Source | DBA AWR System Time Summary.sql |
| Full Report on Enginatics | www.enginatics.com/reports/dba-awr-system-time-summary/ |
Executive Summary
The DBA AWR System Time Summary report quantifies the absolute time spent on various database activities. While percentages are useful for composition, absolute values (seconds or microseconds) are necessary for capacity planning and quantifying the impact of changes. For example, knowing that “SQL Execution” dropped from 50,000 seconds to 20,000 seconds proves the success of a tuning exercise.
Business Challenge
- Quantifying Improvement: “We added an index. How many CPU seconds did we save per hour?”
- Capacity Planning: “Our workload is growing by 500 CPU-seconds per week. When will we max out the server?”
- Billing/Chargeback: “How much database time is the ‘Payroll’ module consuming?”
Solution
This report displays the raw values from the Oracle Time Model.
Key Features:
- DB CPU: Total CPU time used by the database.
- DB Time: Total time spent in database calls (CPU + Wait).
- Background CPU: CPU used by background processes (LGWR, DBWR).
Architecture
The report queries DBA_HIST_SYS_TIME_MODEL.
Key Tables:
DBA_HIST_SYS_TIME_MODEL: Stores cumulative time values.DBA_HIST_SNAPSHOT: Used to calculate deltas between snapshots.
Impact
- ROI Justification: Provides hard numbers to justify hardware purchases or consulting fees.
- Trend Analysis: Tracks the growth of specific workload components over months or years.
- Performance Baselines: Establishes a “normal” baseline for comparison during incidents.
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
© Enginatics GmbH