Rman Deletes Archive Log On Primary Database Not Applied On Physical Standby (Doc ID 1324759.1)

Last updated on JULY 01, 2016

Applies to:

Oracle Database - Enterprise Edition - Version 11.2.0.1 to 11.2.0.3 [Release 11.2]
Information in this document applies to any platform.
***Checked for relevance on 14-Aug-2013***

Symptoms

If CONFIGURE ARCHIVELOG DELETION POLICY TO APPLIED ON ALL STANDBY
and then backing up archived logs with option NOT BACKED UP <n> TIMES DELETE INPUT is executed from Primary,
archived logs which have been backed up and not yet APPLIED on Standby are incorrectly deleted.

The configured ARCHIVELOG DELETION POLICY is ignored.


From RMAN output we see the archives are deleted after backup:

RMAN> backup archivelog all not backed up 1 times delete input;
...
RMAN-8071: channel ORA_DISK_1: deleting archived log(s)
name=/u01/orcl/FRA/STRL/archivelog/2010_09_16/o1_mf_1_37_693ykknr_.arc


We also see RMAN configuration showing:

CONFIGURE ARCHIVELOG DELETION POLICY TO APPLIED ON ALL STANDBY;



From primary we see on V$ARCHIVED_LOG the archivelogs having APPLIED column in NO, but still Deleted:

SQL> select sequence#,thread#,creator,archived,applied,deleted,status
     from v$archived_log where sequence#=1621 and thread#=1;

SEQUENCE# THREAD# CREATOR ARCHIVED APPLIED DELETED STATUS

1621            1    ARCH      YES      NO     YES      D

Cause

Sign In with your My Oracle Support account

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

My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms