Here will build a physical standby setup. Our assumption is primary database is already up and running fine And ORACLE_HOME is installed on standby server.




Make sure database is archive log mode, and enable force logging.

[PRIMARY]Add standby logfiles;


            In standby setup, archives log from primary shipped to standby and applied there. But if the primary database crashes, then the online redo logs will stay in primary side. As these logs hasn’t been archives, means those won’t be applied to standby, Which results in data loss. So if we add standby logfile, Data guard writes the Primary’s current redo log to a “standby redo log” allowing complete recovery in case of Primary site is lost.


[PRIMARY]create password file

[PRIMARY]Configure listener and tns entries as below.

[PRIMARY]Do below changes in spfile of primary

[PRIMARY]So after the changes the spfile in primary will look as below.


 [STANDBY] Create directory structure same as that of primary

[STANDBY]pfile and password file creation in $ORACLE_HOME/dbs location:

   [STANDBY] Listener and tns setup  

[STANDBY]start the standby database in nomount state:

[STANDBY]Now check the connectivity between primary and standby using sys password

[STANDBY]Now connect to rman and run the duplicate command as mentioned below.

[STANDBY]Once duplication is done. Start the recovery

If you wish you open the standby with read only mode as active dataguard, then use below one.

The physical standby setup is ready for use.