DBA Archive / Redo Log Rate – Oracle EBS SQL Report
Oracle E-Business Suite SQL report from the Enginatics Library powered by Blitz Report™.
Overview
If the database is running in ARCHIVELOG mode, the amount of generated archive log is shown. For databases on NOARCHIVELOG, the approximate amount of generated redo is calculated by the number of log switches per hour and log file size. Note that this log rate is just an approximated maximum as switches could also occur without the log files being full.
Redo log files are located here: select * from sys.v_$logfile
Report Parameters
Days
Oracle EBS Tables Used
v$database, dual, gv$instance, gv$archived_log, gv$log_history, gv$log
Report Categories
Related Reports
FND Concurrent Requests 11i, FND Concurrent Requests, DBA Log Switches, DBA Redo Log Files, DBA SGA Active Session History, DBA AWR Blocking Session Summary, DBA AWR Active Session History, DBA AWR System Metrics Summary, DBA SGA+PGA Memory Configuration
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 Archive Redo Log Rate 13-Jul-2018 173740.xlsx |
| Blitz Report™ XML Import | DBA_Archive_Redo_Log_Rate.xml |
| Full SQL on Enginatics | www.enginatics.com/reports/dba-archive-redo-log-rate/ |
Executive Summary
The DBA Archive / Redo Log Rate report analyzes the volume of Redo Log generation over time. This metric is a fundamental indicator of database activity and write intensity. It is essential for sizing backup storage, planning network bandwidth for Data Guard (Disaster Recovery), and identifying abnormal spikes in database workload.
Business Challenge
- Capacity Planning: “How much disk space do we need for our archive log destination?”
- DR Bandwidth: “Do we have enough network throughput to replicate changes to the standby site in real-time?”
- Performance Spikes: “Why was the system slow at 10 AM? Was there a massive data load?”
Solution
The report calculates the log generation rate based on historical log switches.
Key Features:
- Archivelog Mode: Uses
GV$ARCHIVED_LOGfor precise volume measurement. - NoArchivelog Mode: Estimates volume based on
GV$LOG_HISTORY(switch frequency) and log file size. - Trend Analysis: Shows the daily or hourly generation rate.
Architecture
The report queries the instance history views.
Key Tables:
GV$ARCHIVED_LOG: History of archived logs.GV$LOG_HISTORY: History of log switches.GV$LOG: Current log configuration.
Impact
- Infrastructure Sizing: Prevents “disk full” outages by accurately forecasting storage needs.
- Disaster Recovery: Ensures the DR strategy is viable by validating network requirements.
- Workload Characterization: Helps DBAs understand the “personality” of the database (write-heavy vs. read-heavy).
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