DATAGUARD环境下主库配置归档日志删除策略如下出现RMAN-08591报错
RMAN> CONFIGURE ARCHIVELOG DELETION POLICY TO APPLIED ON STANDBY;
RMAN-08591: WARNING: invalid archived log deletion policy
有三种解决方法
1.主库配置rman加个ALL字
RMAN> CONFIGURE ARCHIVELOG DELETION POLICY TO APPLIED ON ALL STANDBY;
2.主库取消db_recovery_file_dest的设置
SQL> alter system set db_recovery_file_dest='';
3.主库配置备库归档路径log_archive_dest_2时加上mandatory参数
产生 RMAN-08591具体可以查看官方文档1984064.1
CAUSE
The RMAN archivelog deletion policy determines when archivelogs stored in the fast recovery area (FRA) may be removed from the database fast recovery area automatically when the database starts experiencing space pressure in the FRA.
In cases where the RMAN archivelog deletion policy is being set to "applied on standby" at least one of the destination standby site(s) MUST be set as a "MANDATORY" destination
SOLUTION
To eliminate the RMAN warning message when setting the deletion policy for archivelogs, at least one archive destination must be set as a mandatory destination.
实验过上面三种解决方法，lgwr async模式下的备库，备库网络中断，看主库正常归档吗，主库会hang住吗
第1种情况下，主库正常归档不会hang住， backup database format 'DATA_%U' plus archivelog format 'ARCH_%U' delete all input时 没有传输到备库的归档日志不会被删除，
会报错RMAN-08120: WARNING: archived log not deleted, not yet applied by standby
第2种情况下，主库正常归档不会hang住， backup database format 'DATA_%U' plus archivelog format 'ARCH_%U' delete all input时 没有传输到备库的归档日志不会被删除，
会报错RMAN-08120: WARNING: archived log not deleted, not yet applied by standby
第3种情况下，主库不能正常归档，归档时报错ORA-16014: log 3 sequence# 94 not archived, no available destinations， 长时间后会hang住
当然就算是主库没上面三种解决方法，在配置rman时出现了RMAN-08591报警，没有传输到备库的归档日志在主库也不会被正常删除掉
通过RMAN> delete archivelog all;操作，主库没有传输到备库的归档日志不会被删除
主库通过backup database format 'DATA_%U' plus archivelog format 'ARCH_%U' delete all input时没有传输到备库的归档日志也不会被删除，
会报错RMAN-08120: WARNING: archived log not deleted, not yet applied by standby，并且rman备份的最后会出现一句RMAN-08591: WARNING: invalid archived log deletion policy
RMAN> CONFIGURE ARCHIVELOG DELETION POLICY TO APPLIED ON STANDBY;
RMAN-08591: WARNING: invalid archived log deletion policy
有三种解决方法
1.主库配置rman加个ALL字
RMAN> CONFIGURE ARCHIVELOG DELETION POLICY TO APPLIED ON ALL STANDBY;
2.主库取消db_recovery_file_dest的设置
SQL> alter system set db_recovery_file_dest='';
3.主库配置备库归档路径log_archive_dest_2时加上mandatory参数
产生 RMAN-08591具体可以查看官方文档1984064.1
CAUSE
The RMAN archivelog deletion policy determines when archivelogs stored in the fast recovery area (FRA) may be removed from the database fast recovery area automatically when the database starts experiencing space pressure in the FRA.
In cases where the RMAN archivelog deletion policy is being set to "applied on standby" at least one of the destination standby site(s) MUST be set as a "MANDATORY" destination
SOLUTION
To eliminate the RMAN warning message when setting the deletion policy for archivelogs, at least one archive destination must be set as a mandatory destination.
实验过上面三种解决方法，lgwr async模式下的备库，备库网络中断，看主库正常归档吗，主库会hang住吗
第1种情况下，主库正常归档不会hang住， backup database format 'DATA_%U' plus archivelog format 'ARCH_%U' delete all input时 没有传输到备库的归档日志不会被删除，
会报错RMAN-08120: WARNING: archived log not deleted, not yet applied by standby
第2种情况下，主库正常归档不会hang住， backup database format 'DATA_%U' plus archivelog format 'ARCH_%U' delete all input时 没有传输到备库的归档日志不会被删除，
会报错RMAN-08120: WARNING: archived log not deleted, not yet applied by standby
第3种情况下，主库不能正常归档，归档时报错ORA-16014: log 3 sequence# 94 not archived, no available destinations， 长时间后会hang住
当然就算是主库没上面三种解决方法，在配置rman时出现了RMAN-08591报警，没有传输到备库的归档日志在主库也不会被正常删除掉
通过RMAN> delete archivelog all;操作，主库没有传输到备库的归档日志不会被删除
主库通过backup database format 'DATA_%U' plus archivelog format 'ARCH_%U' delete all input时没有传输到备库的归档日志也不会被删除，
会报错RMAN-08120: WARNING: archived log not deleted, not yet applied by standby，并且rman备份的最后会出现一句RMAN-08591: WARNING: invalid archived log deletion policy
来自 “ ITPUB博客 ” ，链接：http://blog.itpub.net/30126024/viewspace-2128317/，如需转载，请注明出处，否则将追究法律责任。
转载于:http://blog.itpub.net/30126024/viewspace-2128317/
被折叠的 条评论
为什么被折叠?
到【灌水乐园】发言
