standby database ,rman incremental standby recovery

The  situation of  standby database lagging behind to primary database due to network outage can be tacked, without rebuild in Oracle 10g environment by following the below steps. The database version must be greater than 10.1.0.4 and and in a situation where scping of thousands of archives logs is not feasible
Steps to bring the standby database in sync with Primary Database is listed below.

1. Find the current SCN of standby database.

select current_scn from v$database;
CURRENT_SCN
———–
4793543

2. On the primary database – create the needed incremental backup from the above SCN

rman target /
RMAN> BACKUP DEVICE TYPE DISK INCREMENTAL FROM SCN 4793543 DATABASE FORMAT ‘\opt\bkup_%U’;

3. create a new standby controlfile from production

sqlplus> alter database create standby controlfile ‘stdby’;

4.cancel managed recovery on standby
sqlplus> recover managed standby database cancel;

5. Move your incremental backup from (2) to the standby server (empty folder) and catalog it
rman target /
rman> catalog start with ‘\opt\backup\’;

6. recover your standby from the incremental backup
rman> recover database noredo;

7. shutdown the standby and replace the controlfile with the one you backup in (3)

8.startup the standby and put it back into managed recovery mode
sqlplus> startup mount
sqlplus> alter database recover  managed standby database disconnect;