Applying RMAN Incremental Backup To Standby Database

Data Guard
We can use RMAN incremental backup to roll forward the physical standby database in the following situations:
1. when an archive sequence is missing
2. when lots of archives needs to be appliedSteps:

1. Take the current SCN of the standby database

SQL> select to_char(current_scn) scn from v$database;
SCN
—————
23339995

2. Stop the redo apply on the standby database

SQL> alter database recover managed standby database cancel;

3. Take the incremental backup of the production database from the current SCN of the standby database

RMAN> run {
allocate channel c1 type disk format ‘/backup/%d_incr_s%s_p%p’ maxpiecesize 2g;
allocate channel c2 type disk format ‘/backup/%d_incr_s%s_p%p’ maxpiecesize 2g;
allocate channel c3 type disk format ‘/backup/%d_incr_s%s_p%p’ maxpiecesize 2g;
allocate channel c4 type disk format ‘/backup/%d_incr_s%s_p%p’ maxpiecesize 2g;
backup as compressed backupset incremental from scn 23339995 database;
}

4. Transfer the incremental backup to the standby system

$ scp /backup/* [email protected]:/tmp/

5. Catalog all the incremental backup pieces to the standby database

RMAN> catalog start with ‘/tmp/’ ;

6. Apply incremental backup to the standby database

RMAN> recover database noredo;

7. Create new standby controlfile at the production database, copy this to standby system and replace current standby controlfile with this new one.

SQL> alter database create standby controlfile as ‘/backup/standby_incr.ctl’;

8. Start redo apply on the physical standby database

SQL> alter database recover managed standby database disconnect;

Note:
If you have added new datafile to the production and if it is not at created at standby you have to restore the datafile.
RAMN> restore datafile 56,57,58;