Last updated on OCTOBER 31, 2016
Applies to:Oracle Database - Enterprise Edition - Version 18.104.22.168 and later
Information in this document applies to any platform.
***Checked for relevance on 21-May-2015***
RMAN command 'backup archivelog all delete input' does not delete archivelogs after they have been backed up and issues a warning instead:
archive log filename=/ora03/oraflsh/RMANCCB/1_3740_580667843.dbf thread=1
The database is part of a Data Guard configuration and the backup is being run at the Primary database site. Atlhough the archivelogs are backed up they are not deleted so the archivelog directory is in danger of filling up - if this happens the database will hang as it will not be able to archive any more logs.
New or 'current' archivelogs are being shipped to the Standby site successfully.
If you query v$archived_log on the primary , you will find at least one archivelog with APPLIED=NO:
select recid, dest_id, thread#, sequence#, first_time, completion_time, creator, registrar, archived, applied, deleted, status from v$archived_log where standby_dest='YES' and status='A';
Sign In with your My Oracle Support account
Don't have a My Oracle Support account? Click to get started
Million Knowledge Articles and hundreds of Community platforms