This depend on distance between primary and standby and network bandwidth. So this feature that came with 12c resolve this situation. We are preparing a database one more. This database take archivelog primary database and then send this archivelog to standbyPrimary and far sync standby database are sync, whereas far sync standby database and physical standby database are async.

Let’s begin with creating the physical standby with FAR SYNC instance in place.

First of all our  environment  information is following.

Name IP Database
Primary ORCL
Far sync ORCLFS

We continue with configuring the Far Sync instance . The Far Sync instance is not a full-fledged database. It consists only of a control file and redo logs .

As  we already configured the Far Sync Instance, Now we are going to configure standby database.

For configuring Far Sync: Click Here

Configure Primary Database: We must set some parameter for dataguard enviroinment. Before doing this you don’t forget that primary database must be archivelog mode.

  1. We edit tnsnames.ora file to reach far sync standby database. Primary database tnsnames.ora file is as following.

2. We edit some parameter for dataguard.

NOTE: If we use pfile for database we must add this parameter to pfile.

3. We create standby redo log. Oracle recommend that number of standby redo log is one more than number of redo log file.

Create Standby Database

Now we will create standby database. We will use active database duplication while creating standby database.

1) First we create tnsnames.ora file to reach far sync standby database.

2) We copy pfile and password file from primary database and edit pfile for physical standby database.

3) We create require directory.

4) We configure listener.ora file.

5) We set oracle parameter and start standby instance

6) Now we create standby database with active database duplication. We connect to ORCL database as target and  to ORCLSBY as auxiliary.

After standby database has  created we can start log applying in the standby database with following command.

After doing this we can check dataguard process in the dataguard machines.

Primary database

Far sync Standby Database

Standby database

Now we will configure DG Broker for far sync datagaurd.

Thank you for giving your valuable time to read the above information.

If you want to be updated with all our articles send us the Invitation or Follow us:

Skant Gupta’s LinkedIn:

Joel Perez’s LinkedIn:

Anuradha’s LinkedIn:

LinkedIn Group: Oracle Cloud DBAAS

Facebook Page: OracleHelp

Leave a Reply

This site uses Akismet to reduce spam. Learn how your comment data is processed.