Configure RMAN to purge archivelogs after applied on standby
(Doc ID 728053.1)
Last updated on FEBRUARY 07, 2020
Applies to:Oracle Database - Enterprise Edition - Version 10.2.0.1 and later
Oracle Database Exadata Cloud Machine - Version N/A and later
Oracle Cloud Infrastructure - Database Service - Version N/A and later
Oracle Database Exadata Express Cloud Service - Version N/A and later
Oracle Database Cloud Exadata Service - Version N/A and later
Information in this document applies to any platform.
Checked for relevance on 01-JUL-2015
******* Checked for relevance 16-OCT-2016 ********
We need RMAN to automatically purge archivelogs from the FRA once they are applied to the standby database.
1) From bug 6216036:
In 10g, the archive log deletion policy configured using CONFIGURE command
applies only to automatic deletion of archived logs by Flash Recovery Area.
The other deletion mechanisms like DELETE ARCHIVELOG or DELETE INPUT does not
respect this configuration.
APPLIED ON STANDBY- enables flash recovery area to delete archivelogs that are applied on mandatory standby.
See Oracle Data Guard Concepts and Administration for details.
This restriction is lifted in 11g.
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