DBA AWR PGA History – 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
History of database PGA size and other statistics from v$pgastat in megabytes
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, Diagnostic Pack enabled, Container Data
Oracle EBS Tables Used
dba_hist_snapshot, dba_hist_pgastat
Report Categories
Related Reports
DBA SGA+PGA Memory Configuration, DBA AWR CPU vs Wait Time Summary, DBA AWR System Time Percentages, DBA AWR Blocking Session Summary, DBA AWR Latch Summary, DBA AWR Wait Class by Time, DBA AWR SQL Performance Summary, DBA AWR Wait Event Summary, DBA AWR System Metrics 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 PGA History 29-Jul-2018 094718.xlsx |
| Blitz Report™ XML Import | DBA_AWR_PGA_History.xml |
| SQL Source | DBA AWR PGA History.sql |
| Full Report on Enginatics | www.enginatics.com/reports/dba-awr-pga-history/ |
Executive Summary
The DBA AWR PGA History report tracks the usage of the Program Global Area (PGA) over time. The PGA is the memory region reserved for each server process to perform non-shared operations, primarily sorting and hashing. Unlike the SGA (which is fixed), the PGA grows and shrinks dynamically. This report helps DBAs understand if the PGA_AGGREGATE_TARGET is sized correctly.
Business Challenge
- Memory Leaks: “Why does the database server run out of RAM every Friday?”
- Performance Tuning: “Are we doing too many disk sorts because the PGA is too small?”
- Sizing: “How much memory do we need to allocate to PGA to support 500 concurrent users?”
Solution
This report displays historical PGA statistics from AWR.
Key Features:
- Total PGA Allocated: The total amount of memory currently used by all processes.
- Cache Hit %: The percentage of work areas (sorts/hashes) that ran entirely in memory (Optimal) vs. spilling to disk (One-pass/Multipass).
- Over-allocation Count: Number of times the system failed to honor the target limit.
Architecture
The report queries DBA_HIST_PGASTAT.
Key Tables:
DBA_HIST_PGASTAT: Historical PGA statistics.DBA_HIST_SNAPSHOT: Snapshot timing.
Impact
- Stability: Prevents ORA-4030 (out of process memory) errors.
- Performance: Maximizes in-memory sorting, which is orders of magnitude faster than disk sorting.
- Cost Efficiency: Ensures RAM is allocated where it’s needed most (SGA vs. PGA).
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