1. Synchronize using Dbvisit Sync feature

1.1 Introduction

This section will provide you with an overview of the Synchronize Standby Database feature in Multiplatform.

This option is to assist in two particular scenarios:

Resolving unrecoverable archive log gaps
- This can happen when archive logs were lost or deleted by accident before they were transferred and applied to the standby database. This way we can roll the standby database forward using RMAN incremental backups, instead of recreating it.
Fixing logical corruption on the standby database due to nologging operations that were performed on the primary
- When nologging operations are performed on a primary database, there is no redo available that can be used to update the standby database. The effect is logical corruption on the standby database.
- We recommend that FORCE LOGGING be enabled for the primary database

The Sync feature, in summary, does the following:

Detect the current standby database SCN number
Compares this with the Primary database and then starts an incremental backup on the primary for all blocks from this SCN number.
The backup process can take a similar time to a full RMAN backup based on the time the standby was out of sync with primary and the changes that happened during the timeframe.
The backup should, however, be small - depending on the difference between the primary and standby
The backup is then transferred to the standby database server
From there a recovery process is started that will use this incremental backup to roll forward the standby database.
During this process, the standby controlfile is recreated

1 1. Synchronize using Dbvisit Sync feature
- 1.1 1.1 Introduction
- 1.2 1.2 Synchronize Standby Database
2 2. Synchronize standby DB manually
- 2.1 2.1 Prerequisites
- 2.2 2.2 Performing Incremental backup sync manually

1.2 Synchronize Standby Database

In the section below we will show you how you can run the Sync feature for both options to recover from unrecoverable archive log gap, as well as fix logical corruption due to nologging operations.

It may happen that an archivelog was removed by backups before it was shipped to the standby, or if the standby database is far behind the primary for some reason - it is then possible to make use of the Synchronize Standby Database feature provided by Dbvisit Multiplatform. This method can be used instead of the traditional rebuild of the standby database using the CSD (Create Standby Database) feature.
During this process, Dbvisit Multiplatform will perform an incremental backup on the primary database backing up the required changed blocks from the SCN number where the standby is currently and then ship this backup to the standby and then use RMAN to recover the standby using this backup. The result is that the standby database is "rolled forward" past this missing archived log. The process is easy and described in the steps below.

Choose the configuration for which you need to synchronise the standby database.

( 1 ) The primary and standby details are displayed including the SCN and timestamp the Primary and standby are at and also the time gap between them

( 2 ) By default, the Synchronize Lag option is selected.

( 3 ) We can use the transportable media option for the destination so that the external media can be used to take backup in source and we could resume the sync once the media has been attached in the standby.

( 4 ) Specify the temporary backup location where the incremental backup will be created on the primary database server. It is important that this location must be able to hold at least a full compressed backup of the primary database (RMAN compressed backupset). If you do not have sufficient disk space, the Synchronize Standby process will fail. Note that the backup in most cases will be much smaller than a normal full backup as only the blocks needed to recover the standby database will be backed up. Make sure this location has correct permission and that the Oracle software owner has full read-write permission on this folder. This is the temporary location on the standby database server where the temporary incremental backup will be copied. It is recommended that this location have sufficient space to hold a full compressed backup of the primary database to ensure you do not run into any space-related issues during this process. This location must exist on the standby database server and the Oracle software owner must have full read/write permission on this folder.

( 5 ) Once you have provided the source and destination temporary backup locations, you can click on start to start the process.

The progress of the synchronize standby can be seen from the tasks .

Once the process is completed, the automatic standby update can be enabled and the archivelogs would automatically be shipped from primary and applied on standby.

2. Synchronize standby DB manually

It is possible to use directly RMAN to synchronize standby database with incremental backups without using streamlined Dbvisit "Synchronize" process. Below are the steps needed for manual incremental backup synchronization of your standby database if you can't use the streamlined automated process for any reason.

NOTE: This process should be performed only by an Oracle DBA as it requires Oracle database knowledge. Whenever possible, use and prefer the streamlined synchronize process as described on Oracle: Synchronize standby

2.1 Prerequisites

A. Standby database must be mounted. Verify this by running on standby:

[oracle@czlin0212 oracle]$ sqlplus / as sysdba
 
select open_mode,database_role from v$database;
 
OPEN_MODE            DATABASE_ROLE
-------------------- ----------------
MOUNTED              PHYSICAL STANDBY

If your standby database is not MOUNTED or can't be MOUNTED, it's very likely in no shape for Incremental backup sync and you should recreate it from the scratch: Create DR Database for Oracle

B. Standby database has no datafile errors. On standby run:

[oracle@czlin0212 oracle]$ sqlplus / as sysdba
 
select file#, name, status from v$datafile
where status = 'RECOVER' or status = 'OFFLINE' or status = 'SYSOFF';

The result must return no rows, otherwise your standby database is likely in no condition for Incremental backup sync (recreate from the scratch).

C. Standby database has all datafiles which primary database has and is on the same incarnation. On primary and standby run:

[oracle@czlin0211 oracle]$ sqlplus / as sysdba
 
select file#,name from v$datafile;
select * from v$database_incarnation;

The results must match. It's possible to have different paths and names on primary and standby (for example when using OMF and ASM to filesystem conversion), but otherwise the datafiles need to be equal.

D. You need to ensure no archivelog will be deleted on primary from the point in time you start with the process, until the point in time when apply of the incremental backup is finished.

2.2 Performing Incremental backup sync manually

1. Find out the lowest needed recovery SCN on standby database:

The con_id <> 2 condition is to skip PDB$SEED datafiles.

2. Run incremental backup on your primary database:

Be sure to have backup directory ready (in this case /u02/app/oracle/dbvisit_backup). There's unfortunately no way how to predict the size of the incremental backup - all depends on number of changes done to your primary database since last synchronization with standby database.

3. Copy all backup files to standby server:

Copy all files located in /u02/app/oracle/dbvisit_backup to same location on standby server via scp

4. Restore controlfile on your standby server:

5. Catalog standby database datafiles on standby:

This step is necessary to perform if using OMF and/or different datafile locations on primary and standby

You will need to catalog datafiles for each separate location, for example if you would have datafiles in /u02/app/oracle/oradata/MEGA you would need to catalog datafiles in that location as well.

example output:

6. Switch database to copy on standby:

example output:

ALL datafiles need to be switched successfully.

Dbvisit Standby MP User Guide

Oracle: Synchronize standby