RMAN backups in Max Performance/Max Availability Data Guard Environment [ID 331924.1]
2011-09-30 14:11
381 查看
RMAN backups in Max Performance/Max Availability Data Guard Environment [ID 331924.1] | ||
Modified 28-DEC-2010 Type BULLETIN Status PUBLISHED |
Purpose
Scope
and Application
RMAN
backups in Max Performance/Max Availability Data Guard Environment
References
Applies to:
Oracle Server - Enterprise Edition - Version: 10.1.0.2 to 10.2.0.1 - Release: 10.1 to 10.2Information 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 environmentRMAN 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 mandatorystandby 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 DESTINATION MUST BE MANDATORY WHILE MAX PERFORMANCE---------------------------------------------------------------------------------------------------
相关文章推荐
- RMAN backups in Max Performance/Max Availability Data Guard Environment [ID 331924.1]
- Using Flashback in a Data Guard Environment
- Collecting Diagnostic Data for Performance Issues in Oracle E-Business Suite (文档 ID 1121043.1)
- Troubleshooting gc block lost and Poor Network Performance in a RAC Environment (Doc ID 563566.1)
- 如何使用 RMAN 增量备份恢复 data guard log gap(日志断档)
- RMAN-20201: datafile not found in the recovery catalog
- Design Tradeoffs for Data Deduplication Performance in Backup Workloads
- 怎样使用 RMAN 增量备份恢复 data guard log gap(日志断档)
- IMPLEMENTING FAST-START FAILOVER IN 10GR2 DATAGUARD BROKER ENVIRONMENT [ID 359555.1]
- RMAN Restore Database Slow / How To Improve RMAN Restore Performance [ID 467694.1]
- RMAN 'Duplicate From Active Database' Feature in 11G [ID 452868.1]
- DataNode: java.io.IOException: Incompatible namespaceIDs in /dfs/dfs/data: namenode namespaceID = 69
- Pre 11.2 Database Issues in 11gR2 Grid Infrastructure Environment (文档 ID 948456.1)
- 转载:Data Guard Physical Standby Setup in Oracle Database 11g Release 2
- Advise On How To Improve Rman Performance [ID 579158.1]
- Role Transitions for Data Guard Configurations Using Mixed Oracle Binaries [ID 414043.1]
- Interaction Between the Data Guard Broker and a Data Guard Configuration [ID 249703.1]
- mysql5.7.12/13在安装新实例时报错:InnoDB: auto-extending data file ./ibdata1 is of a different size 640 pages (rounded down to MB) than specified in the .cnf file: initial 768 pages, max 0 (relevant if non-zero
- Troubleshooting ORA-29740 in a RAC Environment (Doc ID 219361.1)
- How to Configure RMAN I/O Block Size to Improve Backup and Recovery Performance [ID 107213.1]