11g Steps to perform for Rolling Forward a Physical Standby Database using RMAN Incremental Backup.
(Doc ID 836986.1)
Last updated on AUGUST 28, 2023
Applies to:
Oracle Database - Enterprise Edition - Version 10.2.0.1 to 11.2.0.4 [Release 10.2 to 11.2]Information in this document applies to any platform.
Goal
The steps in this section can used to resolve problems of missing or corrupted archive log file, an unresolvable archive gap, or the need to roll the standby forward in time without applying a large number of archivelog files.
Solution
To view full details, sign in with your My Oracle Support account. |
|
Don't have a My Oracle Support account? Click to get started! |
In this Document
| Goal |
| Solution |
| 1) Stop the managed recovery process (MRP) on the STANDBY database |
| 2) Determine the SCN of the STANDBY database. |
| 3) Take an incremental backup off the PRIMARY database |
| 4) Transfer all backup sets to STANDBY server |
| 5) Catalog the backups in STANDBY controlfile. |
| 6) Recover the STANDBY database with the cataloged incremental backup: |
| 7) In RMAN, connect to the PRIMARY database and create a standby control file backup: |
| 8) Copy the standby control file backup to the STANDBY system. If the backup is written to NFS device, this step can be skipped. |
| 9) Capture datafile information in STANDBY database. |
| 10) From RMAN, connect to STANDBY database and restore the standby control file: |
| 11) Mount the standby: |
| 12) Catalog datafiles in STANDBY if location/name of datafiles is different |
| 13) Configure the STANDBY database to use flashback (optional) |
| 14) On STANDBY database, clear all standby redo log groups: |
| 15) On the STANDBY database, start the MRP |
| References |