Professional Documents
Culture Documents
Resolving Gaps in DataGuard Apply Using Incremental RMAN Backup
Resolving Gaps in DataGuard Apply Using Incremental RMAN Backup
This shows that the standby is two and half days lagging! The data at this point
is not just stale; it must be rotten.
The next question is why it would be lagging so far back in the past. This is a
10.2 database where FAL server should automatically resolved any gaps in archive
d logs. Something must have happened that caused the FAL (fetch archived log) pr
ocess to fail. To get that answer, first, I checked the alert log of the standby
instance. I found these lines that showed the issue clearly:
11.[Standby] RMAN does not know about these files yet; so you must let it know b
y a process called cataloging. Catalog these files:
$ rman target=/
Recovery Manager: Release 10.2.0.4.0 - Production on Fri Dec 18 06:44:25 2009
Copyright (c) 1982, 2007, Oracle. All rights reserved.
connected to target database: DEL1 (DBID=846390698, not open)
RMAN> catalog start with /u01/oraback ;
using target database control file instead of recovery catalog
searching for all files that match the pattern /u01/oraback
List of Files Unknown to the Database
=====================================
File Name: /u01/oraback/DEL1_standby.ctl
File Name: /u01/oraback/06l16u1q_1_1.rmb
Do you really want to catalog the above files (enter YES or NO)? yes
cataloging files...
cataloging done
List of Cataloged Files
=======================
File Name: /u01/oraback/DEL1_standby.ctl
File Name: /u01/oraback/06l16u1q_1_1.rmb
12.Recover these files:
RMAN> recover database;
Starting recover at 18-DEC-09
using channel ORA_DISK_1
channel ORA_DISK_1: starting incremental datafile backupset restore
channel ORA_DISK_1: specifying datafile(s) to restore from backup set
destination for restore of datafile 00001: /u01/oradata/DEL2/datafile/o1_mf_syst
em_5lptww3f_.dbf
...
channel ORA_DISK_1: reading from backup piece /u01/oraback/05l16u03_1_1.rmb
channel ORA_DISK_1: restored backup piece 1
piece handle=/u01/oraback/05l16u03_1_1.rmb tag=TAG20091218T083619
channel ORA_DISK_1: restore complete, elapsed time: 00:00:07
starting media recovery
archive log thread 1 sequence 8012 is already on disk as file /u01/oradata/1_801
2_697108460.dbf
archive log thread 1 sequence 8013 is already on disk as file /u01/oradata/1_801
3_697108460.dbf
13. After some time, the recovery fails with the message:
archive log
RMAN-00571:
RMAN-00569:
RMAN-00571:
RMAN-03002: