Configure RMAN to purge archivelogs after applied on standby (Doc ID 728053.1)

Last updated on AUGUST 16, 2017

Applies to:

Oracle Database - Enterprise Edition - Version 10.2.0.1 and later
Information in this document applies to any platform.
Checked for relevance on 01-JUL-2015
******* Checked for relevance 16-OCT-2016 ********

Goal

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.


2)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.

http://docs.oracle.com/cd/B19306_01/backup.102/b14194/rcmsynta015.htm#sthref289


This restriction is lifted in 11g.

 

 

Solution

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