OracleAS 10gR2 Disaster Recovery Using AS Guard: Middle and Collocated Infrastructure Tiers on the Same Server
(Doc ID 420824.1)
Last updated on FEBRUARY 04, 2022
Applies to:Oracle Fusion Middleware - Version 10.1.2.0.0 to 10.1.4.0.1 [Release AS10gR2]
Oracle Fusion Middleware High Availability - Version 10.1.2.0.0 to 10.1.4.0.1 [Release AS10gR2]
Information in this document applies to any platform.
Oracle Application Server 10g Enterprise Edition - Version: 10.1.2.0.0 to 10.1.4.0.1
The purpose of this article is to demonstrate a simple symmetric OracleAS 10g Rel 2 Disaster Recovery environment using AS Guard.
The configuration in this note should not be attempted for new Disaster Recovery Setups.
There has been a significant change in the recommended approach for implementing OracleAS Disaster Recovery. In this respect the existing OracleAS AS Guard functionality is being removed in the future release of Fusion Middleware. To quote from
Oracle® Application Server Disaster Recovery Guide 10g Release 3 (10.1.3.3.0)
1.2.1 Oracle Application Server Disaster Recovery Architecture Overview
Oracle Application Server product binaries, configuration, and metadata files
Use disk replication technologies.
Use Oracle Data Guard for Oracle databases (and vendor-recommended solutions for third party databases).
Therefore for new OracleAS Disaster Recovery builds it is now recommended to implement a solution based on Data Guard and non-Oracle disk replication technologies rather than using AS Guard. This solution is discussed in the documentation reference above.
<Note:779070.1> What is the Recommended Approach to Disaster Recovery for Oracle AS 10g?
The intended audience is Oracle Application Server 10g R2 Administrators
The steps outlined below were tested in the following environment:
Primary and <STANDBY SHORT HOSTNAME> sites have a single Linux 32bit Red Hat AS 4 machines hosting:
* A OracleAS 10g Rel 2 Infrastructure (co-located Metadata Repository and Identity Management)
* A OracleAS 10g Rel 2 J2EE and Webcache middle tier
All Oracle Homes were patched to Oracle Application Server 10.1.2.2.
All hostname resolution on Primary and <STANDBY SHORT HOSTNAME> servers is performed via /etc/hosts. DNS is disabled on both servers.
Note: It is a prerequisite that in any DR setup, all Oracle homes be patched to 10.1.2.2 before embarking on the Disaster Recovery commands. At the very least, if you choose not to install the full 10.1.2.2 patchset, then 10.1.2.2 ASGuard needs to be installed into all Oracle homes (download from OTN). If you choose to install ASGuard 10.1.2.2 only, see <Note 429530.1> Unable To Login To Asg Using Asgctl.Sh As Ias_admin After Upgrading to 10.1.2.2
To view full details, sign in with your My Oracle Support account.
Don't have a My Oracle Support account? Click to get started!
In this Document
|A: Preparing the Primary and <STANDBY SHORT HOSTNAME> Servers for Installation|
|B: Installing Oracle Application Server|
|C: Configuring and Testing Disaster Recovery|
C1: Discovering the Topology
|C2: Switchover Operations|
|C3: Failover Operations|