Skip to content

DBA Redo Log Files

Directory actions

More options

Directory actions

More options

Latest commit

 

History

History

DBA Redo Log Files

Folders and files

NameName
Last commit message
Last commit date

parent directory

..
DBA Redo Log Files.sql
DBA Redo Log Files.sql
 
 
DESCRIPTION.md
DESCRIPTION.md
 
 
README.md
README.md
 
 

README.md

layout default
title DBA Redo Log Files | Oracle EBS SQL Report
description – Oracle E-Business Suite SQL report
keywords Oracle EBS, Oracle E-Business Suite, SQL report, Blitz Report, Enginatics, DBA, Redo, Log, Files, gv$log, gv$logfile
permalink /DBA%20Redo%20Log%20Files/

DBA Redo Log Files – Oracle EBS SQL Report

Oracle E-Business Suite SQL report from the Enginatics Library powered by Blitz Report™.

Overview

None

Report Parameters

Oracle EBS Tables Used

gv$log, gv$logfile

Report Categories

Enginatics

Related Reports

FND Concurrent Requests, FND Concurrent Requests 11i, DBA Archive / Redo Log Rate, DBA Log Switches, FND User Login History, DBA Result Cache Statistics, DBA Result Cache Objects and Dependencies, DBA Parameters, DBA Blocking Sessions

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 Redo Log Files 22-Dec-2025 084346.xlsx
Blitz Report™ XML Import DBA_Redo_Log_Files.xml
Full SQL on Enginatics www.enginatics.com/reports/dba-redo-log-files/

Executive Summary

The DBA Redo Log Files report details the physical configuration of the Online Redo Logs. Redo logs are critical for data integrity; if they are lost, the database cannot recover from a crash. This report verifies that logs are properly multiplexed (mirrored) and located on appropriate storage.

Business Challenge

  • Availability: "Do we have at least two members for each redo log group to protect against disk failure?"
  • Performance: "Are the redo logs on the fastest available disk (e.g., SSD or NVMe)?"
  • Configuration: "How large are our log files? Do we need to resize them?"

Solution

This report joins GV$LOG and GV$LOGFILE.

Key Features:

  • Group Status: CURRENT, ACTIVE, or INACTIVE.
  • Member Path: The full file system path to the log file.
  • Size: The size of the log file in bytes.

Architecture

The report queries GV$LOG and GV$LOGFILE.

Key Tables:

  • GV$LOG: Log group metadata (Sequence #, Size).
  • GV$LOGFILE: Physical file locations.

Impact

  • Data Protection: Ensures that a single disk failure won't cause data loss or downtime.
  • Write Performance: Confirms that redo logs are isolated from other heavy I/O workloads.
  • Recovery: Essential information for performing media recovery.

Useful Links

© 2026 Enginatics