Rman Deletes Archive Log On Primary Database Not Applied On Physical Standby
(Doc ID 1324759.1)
Last updated on JANUARY 30, 2022
Applies to:Oracle Database - Enterprise Edition - Version 188.8.131.52 to 184.108.40.206 [Release 11.2]
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.
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)
We also see RMAN configuration showing:
From primary we see on V$ARCHIVED_LOG the archivelogs having APPLIED column in NO, but still Deleted:
from v$archived_log where sequence#=1621 and thread#=1;
SEQUENCE# THREAD# CREATOR ARCHIVED APPLIED DELETED STATUS
1621 1 ARCH YES NO YES D
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