How To -- Step by step guide for creating Disaster Recovery site for Oracle Apps R12

In this article, I tried to explain Disaster Recovery [DR] site creation for R12 in elaborate manner. It's a very much practical hands on article. By, following each steps carefully any one can create a R12 Disaster Recovery site. I tried to avoid theoretical details about Disaster Recovery unless required for practical implementation. Here I have given a real DR site creation process.


[By following this document any one create a physical standby Data guard site of oracle 11g database also].

Problems which can be Occur in Switching Over to a Standby Database

 Below are some common problem arrives when we commit switch over the 

most common problems are as follows

Switchover Fails Because Redo Data Was Not Transmitted

If the switchover does not complete successfully, you can query the SEQUENCE# column in the V$ARCHIVED_LOG view to see if the last redo data transmitted from the original primary database was applied on the standby database. If the last redo data was not transmitted to the standby database, you can manually copy the archived redo log file containing the redo data from the original primary database to the old standby database and register it with the SQL ALTER DATABASE REGISTER LOGFILE file_specification statement. If you then start log apply services, the archived redo log file will be applied automatically. Query the

Handling Logical Standby Database Failures

An significant device for management ordered standby database flops is the  

DBMS_LOGSTDBY.SKIP_ERROR procedure. Depending on how significant a table is, 

you might desire to manage one of the following:

• Ignore flops for a table or exact DDL
• Associate a retained method with a filter so at runtime a conclusion can be                                        made about skipping the declaration, executing this declaration, or executing a                         replacement statement

Taking one of these activities stops SQL Apply from stopping. Later, you can query the DBA_LOGSTDBY_EVENTS outlook to find and correct any difficulties that exist.