DBA SGA CPU Load (active session history) – Oracle EBS SQL Report
Oracle E-Business Suite SQL report from the Enginatics Library powered by Blitz Report™.
Overview
Aggregates active sessions by snapshot time to identify times with high CPU load over a specific ‘CPU Sessions From’ threshold value.
Report Parameters
From Time, To Time, CPU Sessions From, Session Type, Instance Id, Diagnostic Pack enabled
Oracle EBS Tables Used
Report Categories
Related Reports
DBA SGA Wait Event Summary (active session history), DBA SGA Blocking Session Summary, DBA AWR Blocking Session Summary, DBA AWR Active Session History, DBA SGA Active Session History, Blitz Report History, DBA SGA SQL Performance Summary, DBA Blitz Report ORDS Configuration, DBA ORDS Configuration Validation
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 SGA CPU Load (active session history) 22-Dec-2025 084512.xlsx |
| Blitz Report™ XML Import | DBA_SGA_CPU_Load_active_session_history.xml |
| Full SQL on Enginatics | www.enginatics.com/reports/dba-sga-cpu-load-active-session-history/ |
Case Study & Technical Analysis
Abstract
The DBA SGA CPU Load (active session history) report is a specialized view of ASH data designed to visualize CPU consumption over time. By aggregating the count of active sessions that are ON CPU per sample time, it reconstructs a load profile that can be compared against the server’s physical CPU core count. This helps identify specific intervals where the database was CPU-bound.
Technical Analysis
Core Logic
- Filter: Selects records from
GV$ACTIVE_SESSION_HISTORYwhereSESSION_STATE = 'ON CPU'. - Aggregation: Counts distinct session IDs per
SAMPLE_TIME. - Threshold: The
CPU Sessions Fromparameter allows filtering for spikes where the load exceeded a certain number of concurrent active sessions (e.g., greater than the number of CPU cores).
Interpretation
- Load < Cores: The system is generally healthy; CPU is not the bottleneck.
- Load > Cores: The system is CPU-bound. Sessions are runnable but waiting for CPU time (run queue). Latency increases.
Key View
GV$ACTIVE_SESSION_HISTORY: The source of the CPU usage samples.
Operational Use Cases
- Capacity Planning: Determining if the server needs more CPUs to handle peak loads.
- Spike Analysis: Correlating a CPU spike at 10:00 AM with a specific SQL_ID or Module.
- Resource Manager: Validating if Resource Manager plans are effectively throttling CPU-hungry consumer groups.
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