In my previous article I have shown you how to rebuild a physical standby database using RMAN full database backup. Please refer below link for same.
Rebuild Physical Standby using RMAN full backup
Rolling forward a standby using RMAN full database backup can be time consuming and take several hours based on the size of the database. RMAN offers a flexibility to take the SCN based backup that can be used to incrementally roll forward a standby database. Using RMAN incremental backup to roll forward a standby database is the easiest and quickest way to sync a standby database.
Primary server :–
Standby Server :–
NSMDB and NSMDR
- Get the current SCN from standby database, we will use this SCN for the incremental backup from primary.
- Take a control file backup from NSMDB primary.
- Create backup directory and take an incremental backup from primary, use the SCN from standby in step 1.
- Get datafile file# and name from primary database, and spool output to text file f1.txt for reference.
- Copy the backup pieces to standby hosts in the same location.
- Stop mrp at the standby.
- Get datafile file# and name from standby database, and spool output to text file f2.txt for reference.
- Bring down standby database, all instances.
- Start the standby database instance in nomount and restore the controlfile.
- Mount the standby database, stop MRP, catalog the backup pieces.
- Catalog data files and switch the files to copy.
- Recover the standby database.
- Restart MRP and ensure that recovery is progressing.