The Latest Oracle E-Business Suite Technology News direct from
Oracle E-Business Suite Development & Product Management

Business Continuity for EBS Using Oracle 11g Physical Standby DB

Steven Chan
Senior Director
Our Applications Technology Group database architects have released two new documents covering the use of Oracle Data Guard to create physical standby databases for Oracle E-Business Suite environments:  
Architecture diagram showing how Oracle Data Guard physical standby works
What is a Standby Database? A standby database is a transactionally-consistent copy of the primary database. Using a backup copy of the primary database, you can create up to thirty standby databases and incorporate them in Data Guard configuration. There are three types of standby databases:
Physical Standby Provides a physically identical copy of the primary database, with on-disk database structures that are identical to the primary database on a block-for-block basis. The database schema, including indexes, are the same. A physical standby database is kept synchronized with the primary database by recovering the redo data received from the primary database. Logical Standby Contains the same logical information as the primary database, although the physical organization and structure of the data can be different. It is kept synchronized with the primary database by transforming the data in the redo logs received from the primary database into SQL statements and then executing the SQL statements on the standby database. Snapshot Standby A fully updatable standby database. Like a physical or logical standby database, a snapshot standby database receives and archives redo data from a primary database. Unlike a physical or logical standby database, a snapshot standby database does not apply the redo data that it receives.
These new notes detail the steps for setting up the first of these types, a Physical Standby database using Oracle Data Guard. New EBS Roadmap documentations, too Our Applications Technology Group database architects have also released two new roadmap documents covering the latest options for High Availability, Real Application Clusters, and Maximum Availability Architectures: Related Articles

Join the discussion

Comments ( 4 )
  • Francisco Tejeda Tuesday, September 21, 2010

    Hello Mr. Steven,

    We recently configured our eBusiness Suite 11i with Physical Standby DB. I would like to know if you can guide us with a procedure to apply application patches with minimal time.

    The EBS (Financial) version is 11.5.9 and the Database version is All the tiers (DB, App server, Forms/Reports services) are installed in one box.

    The remote Site is about 750km away.

    So far, what we plan to do is :

    1. Shutdown the standby site.

    2. DEFER the log_archive_dest_2.

    3. Apply the patch to main site.

    4. Clone the main site (Involves backup).

    5. Restore at standby site.

    6. Reconfigure dataguard.

    As you can see the downtime is very high. Any advice ?

    Thanks in advace,

    Francisco Tejeda

  • Steven Chan Friday, October 15, 2010

    Hello, Francisco,

    My apologies for the delay in responding to this. Your question got swallowed by my post-OpenWorld backlog.

    Note 216212.1 discusses patching EBS after implementing a DR configuration; I'd recommend reviewing that document in detail.



  • Brenna Galbraith Friday, November 12, 2010

    Hello Steven -

    Can you provide any guidance into the use of Data Guard Broker with EBS 11i? I am currently trying to configure Data Guard for an EBS instance and I am running OEM 11g and would like to use Data Guard Broker for the management of the 2 instances.

    I have heard that this may not be certified - is that the case?



  • Steven Chan Friday, November 12, 2010

    Hello, Brenna,

    The use of Data Guard Broker with the E-Business Suite isn't explicitly certified but it is supported for use. In other words, it's technically-feasible to use this set of tools with the E-Business Suite, but we don't publish E-Business Suite-specific documentation for that configuration, since it's not needed The generic Data Guard Broker documentation should suffice.

    You should note that the automatic failover doesn't work with E-Business Suite environments, since you need to run AutoConfig before bringing a standby database online. But as long as you set up your init.ora settings as per the documentation linked above, you can configure and monitor using the Data Guard Broker tools.

    Best of luck with your implementation. I'd be interested in hearing about your experiences with this tool; please feel free to drop me a line when you've got this running.



Please enter your name.Please provide a valid email address.Please enter a comment.CAPTCHA challenge response provided was incorrect. Please try again.