List Backup of Archivelog All: Oracle RMAN Command Guide

calendar Feb 9, 2026 / · 4 min read · Oracle RMAN Backup Archive Logs Database Administration Recovery DBA Scripts  ·
Share on: linkedin copy

List Backup of Archivelog All: Oracle RMAN Command Guide

Purpose

The LIST BACKUP OF ARCHIVELOG ALL command in Oracle Recovery Manager (RMAN) displays all existing backups of archived redo log files stored in the RMAN repository. This command helps database administrators track and manage archived log backups, verify backup completion, and plan recovery operations. Archive log backups are essential for point-in-time recovery and maintaining database consistency during restore operations.

Breakdown of Code

Command

1list backup of archivelog all;

Command Structure

The command consists of three main components that work together to query the RMAN repository:

  • LIST BACKUP: The base command that queries backup information from the RMAN catalog or control file
  • OF ARCHIVELOG: Specifies that you want to see backups of archived redo log files only
  • ALL: Shows all archived log backups without any filtering or time restrictions

Key Points

  • The command displays all archived redo log backups regardless of sequence number, date, or backup destination
  • Output includes backup set details, completion time, status, and storage location for each archived log backup
  • Works with both disk-based backups and tape backups (SBT) when no device type is specified
  • Requires connection to either the target database control file or a recovery catalog
  • Shows backups that are still available and have not been deleted from the repository
  • Can be combined with additional options like SUMMARY for condensed output or filtering by date

Command Variations

You can modify the basic command to filter results based on specific needs:

 1-- List backups in summary format (tabular view)
 2list backup of archivelog all summary;
 3
 4-- List backups by specific sequence number
 5list backup of archivelog sequence 192;
 6
 7-- List backups between sequence ranges
 8list backup of archivelog sequence between 186 and 192;
 9
10-- List backups until a specific sequence
11list backup of archivelog until sequence 192;
12
13-- List backups from a specific sequence onward
14list backup of archivelog from sequence 186;
15
16-- List backups completed within a date range
17list backup of archivelog all completed between 'sysdate-7' and 'sysdate';

Insights and Explanations

When to Use This Command

Database administrators use this command in several common scenarios:

  1. Backup Verification: After completing a backup job, verify that archived logs were successfully backed up
  2. Recovery Planning: Before performing database recovery, identify which archived log backups are available
  3. Space Management: Review archived log backup history to plan retention policies and cleanup operations
  4. Compliance Auditing: Generate reports showing backup coverage for archived redo logs

Understanding the Output

The command output provides detailed information about each archived log backup:

  • Backup Set Key: Unique identifier for the backup set in the repository
  • Status: Shows whether the backup is AVAILABLE, EXPIRED, or UNAVAILABLE
  • Device Type: Indicates DISK or SBT_TAPE storage location
  • Completion Time: Timestamp when the backup finished
  • Archive Log Details: Thread number, sequence number, and log file identifiers

Best Practices

When working with archived log backups, follow these guidelines:

  • Run this command regularly to monitor backup health and ensure archive logs are being protected
  • Use the SUMMARY option when you need quick overview information without verbose details
  • Combine with date filters to focus on recent backups or identify old backups for deletion
  • If using a recovery catalog, the catalog stores longer backup history than the control file alone
  • Configure automatic archiving mode (ARCHIVELOG) before taking archive log backups

Recovery Catalog vs Control File

RMAN stores backup metadata in two possible locations:

  • Control File: Default storage location with limited retention (typically 7-30 days depending on CONTROL_FILE_RECORD_KEEP_TIME)
  • Recovery Catalog: Separate database that stores extended backup history and enables advanced features like stored scripts and cross-database recovery

When connected to a recovery catalog, the LIST command queries catalog tables instead of the control file, providing access to historical backup information that may have aged out of the control file.

References

Posts in this series