Applies to:

Oracle Server - Enterprise Edition - Version: 10.1 to 10.2

Information in this document applies to any platform.

Purpose

When using 'configure archive log deletion policy to applied on standby' on primary database, allow RMAN to consider *both* mandatory and optional destinations when determining which logs on primary can be deleted.

Scope and Application

RMAN backups on standby database in Data Guard environment

RMAN backups in Max Performance/Max Availability Data Guard Environment

The 10g RMAN-Data Guard paper states that 'archive log deletion policy applied on standby' only checks that a log has been applied on all mandatory standby databases.

However, Data Guard best practice for Max Performance and Max Availability modes is to *not* use mandatory standby (so that primary does not hang in the event of online logs filling up). Therefore, the following parameter must be set:

_log_deletion_policy='ALL'

This will allow RMAN to delete logs from the Flash Recovery Area on primary database host that have been applied to all standby databases (whether mandatory or optional). Database will require bounce after setting this parameter.

NOTE: To make the change in an spfile, double quotes must be used around parameter name:

alter system set "_log_deletion_policy"=ALL scope=spfile sid='*';

NOTE: attempt to set this configuration in RMAN without this parameter setting may result in error:

RMAN> configure archivelog deletion policy to applied on standby;

new RMAN configuration parameters:

CONFIGURE ARCHIVELOG DELETION POLICY TO APPLIED ON STANDBY;

new RMAN configuration parameters are successfully stored

starting full resync of recovery catalog

full resync complete

RMAN-08591: WARNING: invalid archivelog deletion policy

References

Bug 5261960 - RMAN-8591 STANDBY DESTIONATION MUST BE MANDERATORY WHILE MAX PERFORMANCE

Errors

RMAN-8591 WARNING: invalid archivelog deletion policy

http://www.itpub.net/viewthread.php?tid=957569&extra=&page=1

源文档 <http://orax.blog.sohu.com/82670533.html>