Steps to perform for Rolling forward a standby database using RMAN incremental backup when datafile is added to primary (Doc ID 1531031.1)

Last updated on JULY 03, 2023

Applies to:

Oracle Database - Enterprise Edition - Version 10.2.0.1 to 11.2.0.3 [Release 10.2 to 11.2]
Oracle Database - Enterprise Edition - Version 11.2.0.4 to 11.2.0.4 [Release 11.2]
Oracle Database - Enterprise Edition - Version 12.1.0.2 to 12.1.0.2 [Release 12.1]
Oracle Database Cloud Schema Service - Version N/A and later
Oracle Database Exadata Cloud Machine - Version N/A and later
Information in this document applies to any platform.

Goal

The steps in this section can used to resolve problems if a physical standby database has lost or corrupted archived redo data or has an unresolveable archive gap.

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

1) On the standby database, stop the managed recovery process (MRP)

2) On the standby database, find the SCN which will be used for the incremental backup at the primary database:

3) In sqlplus, connect to the primary database and identify datafiles added:

4) Using rman, create backup of missing datafiles and an incremental backup using the SCN derived in the previous step:

5) Transfer all backup sets created on the primary system to the standby system.

6) Restore new controlfile and catalog the backup transfered in step #5:

7) Restore missing datafiles:

8) Rename the datafiles in new standby controlfile

9) Recover the standby database with the cataloged incremental backup:

10) If the standby database needs to be configured for FLASHBACK use the below step to enable.

11) On standby database, clear all standby redo log groups:

12) On the standby database, start the MRP

My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.