My Oracle Support Banner

RMAN Deleting Archive Logs Without Backing Them Up First (Doc ID 2127258.1)

Last updated on FEBRUARY 16, 2019

Applies to:

Oracle Database - Enterprise Edition - Version and later
Oracle Database Cloud Schema Service - Version N/A and later
Oracle Database Exadata Cloud Machine - Version N/A and later
Oracle Database Exadata Express Cloud Service - Version N/A and later
Oracle Cloud Infrastructure - Database Service - Version N/A and later
Information in this document applies to any platform.


ARCHIVE logs are being deleted before they are backed up.  This is happening in 4 of our RAC production databases and they are on different RAC servers.
The databases are part of a Data Guard configuration and all the archive logs are shipped.  The archive logs that were not not backed up can be identified by running below query.  This example will focus on thread=2 and sequence=111612

  SQL> select thread#, sequence# from v$archived_log where creator='ARCH' and backup_count=0 and deleted='YES' order by 1,2;


To view full details, sign in with your My Oracle Support account.

Don't have a My Oracle Support account? Click to get started!

In this Document

My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.