看看我的绝招:
在standby中,当archivelog 的gap较多的时候,可以使用基于scn的增量备份来恢复gap;
步骤如下:
1,根据备库已apply最后一个归档日志的对应的NEXT_CHANGE# 做为增量备份的scn号
select d.FIRST_CHANGE#,d.NEXT_CHANGE# from v$archived_log d where d.SEQUENCE#=118329
2,在主库做如下的备份:
rman target /
RMAN> BACKUP DEVICE TYPE DISK INCREMENTAL FROM SCN 10174270049523 DATABASE FORMAT '/archlog/ccicdb_incr__%s_%p_%t.bk';
3,将增量备份ftp 到备库的/remotearch目录下:
在备库操作:
rman target /
RMAN> CATALOG START WITH '/remotearch/';
或者:
catalog backuppiece '/backdata/bk_307_1_746250371'
在备库恢复
RMAN> RECOVER DATABASE NOREDO;
4,备库恢复完增量备份后,在主库生产最新的控制文件ftp 到备库:
alter database recover managed standby database disconnect from session;
5,在备库使用最新的控制文件并mount和设置为恢复模式:
alter database recover managed standby database disconnect from session
观察后台的alert 日志,看需要那些归档日志,再手动安排:
FS[1]: Assigned to RFS process 323640
RFS[1]: Identified database type as 'physical standby'
Fri Mar 11 21:15:07 2011
RFS LogMiner: Client disabled from further notification
Fri Mar 11 21:15:31 2011
FAL[client]: Failed to request gap sequence
GAP - thread 1 sequence 125769-125769
DBID 3944144691 branch 665275242
FAL[client]: All defined FAL servers have been attempted.
-------------------------------------------------------------
Check that the CONTROL_FILE_RECORD_KEEP_TIME initialization
parameter is defined to a value that is sufficiently large
enough to maintain adequate log switch information to resolve
archivelog gaps.
------------------------------------------------------------