What is Data Guard far sync?

What is Data Guard far sync?

New in Oracle Database 12c, Active Data Guard Far Sync provides the ability to perform a zero data loss failover to a remote standby database without requiring a second standby database or complex operation. A Far Sync instance can also forward redo to the new Oracle Database Backup, Logging, and Recovery Appliance1.

What is far sync standby database?

Far SYNC is a feature introduced with 12c. It is the dummy instance that sends the Redos from the Primary Database to other Standby Databases in the Data Guard configuration. By sending redos to the nearby location as SYNC, it guarantees zero data loss. It also preserves the availability of the Primary Database.

How do I know if Data Guard is in sync?

1. Step 1 : Check the status of database on both server.
2. Step 2 : Check for GAP on Standby.
3. Step 3 & 4: Check redo received and applied on standby.
4. Step 5: Identify the missing archive log file.
5. Step 6: Copy missing archive log file.
6. Step 7: Register archive logfile with standby.

How do I sync my primary standby database?

Steps to bring the standby database in sync with Primary Database are listed below.

1. Find the current SCN of standby database.
2. On the primary database – create the needed incremental backup from the above SCN.
3. create a new standby controlfile from production.
4. Cancel managed recovery on standby.

What is Farsync?

5 Far Sync. An Oracle Data Guard far sync instance is a remote Oracle Data Guard destination that accepts redo from the primary database and then ships that redo to other members of the Oracle Data Guard configuration.

How do I know if Data Guard is working?

Data Guard is a replay of a redo stream from the primary database against a standby database. The easiest way to validate that Data Guard is working would be to connect to the broker and show database . It’ll show you the apply lag which an indication of how far behind the standby database is.

What is Data Guard lag apply?

APPLY LAG – Apply lag is a measure of the degree to which the data in a standby database lags behind the data in the primary database, due to delays in propagating and applying redo to the standby database.

How do I restore a physical standby database?

Steps to recover a physical standby database by using an incremental RMAN backup

1. Step 1: Check the sync status of primary and standby site.
2. Step 2: Simulate a gap between the primary and standby.
3. Step 3: Incremental backup.
4. Step 4: Back up the standby control file.
5. Step 5: Ship the backups across to the standby site.

How do I rebuild my standby database?

Rebuild Physical Standby using RMAN full backup

1. run { allocate channel c1 device type disk format ‘/backup/nsmdb/NSMDB_%U’;
2. rman target / backup current controlfile for standby format ‘/backup/nsmdb/NSMDB_stby_ctl’;
3. rman target / startup nomount.
4. SQL> alter database mount standby database;
5. run {
6. set lines 150.