Configuring Standby for Oracle E-Business Suite R12.2

Overview of Technical concepts involved in configuring Standby in Oracle E-Business Suite R12.2

The database SID must be the same on both the primary and physical standby databases, whereas the DB_UNIQUE_NAME is different on the primary and physical standby database.

Redo data transmitted from the primary database is received by the remote file server (RFS) process on the standby system. The RFS process writes the redo data to archived log files or standby redo log files. Redo data can be applied either after the redo is written to the archived redo log file or standby redo log file, or, if real-time apply is enabled, directly from the standby redo log file as it is being filled.

Preparing the Primary Database for Standby Database Creation

• Enable Forced Logging Archive log
• Configure Oracle Net Communication to and From Standby System
• Set Up Secure Connections
• Set Primary Database Initialization Parameters

• Enable Archive Logging on Primary System & Add Standby RedoLogs
• Run the Application Tier and Database Pre-clone
• Copy APPL_TOP and Oracle E-Business Suite Tech Stacks to the Application Tier in Standby Environment.

Creating a Physical Standby Database

• Copy ORACLE_HOME and Database to the Standby Database Server (using Manual Cold/Hot backup, RMAN backup)
• Configure Oracle Net services
• Clone the Database, mount the Physical Standby and Start Processing Redo on the Standby
• Verify redo is shipping

Configuring the Application Tier: