How To Install An Oracle Database In An Active/Passive Configuration Without RAC? [ID 734361.1]

Applies to:

Oracle Server - Enterprise Edition - Version: 9.2.0.1 to 11.2.0.2 - Release: 9.2 to 11.2
Information in this document applies to any platform.

Goal

How to install an Oracle database in a 2-node active/passive environment without using RAC.

Solution

The set up of an active/passive failover system is fairly straightforward.

It consists of the following main parts:

1. Install an Oracle Home locally on cluster node A.
   
2. Install an identical Oracle Home locally on cluster node B.
   
   The identical Home can either be installed using the OUI or can be cloned according to the appropriate cloning procedures as summarized in
   - How To Clone An Existing RDBMS Installation Using OUI
   
   Using the cloning procedures, the Home will also have its own oraInventory entry which is required for any further install or patch actions.
   
3. Create/use the database located on shared storage under $ORACLE_BASE/oradata/ that can be accessed from both server A and B.
   
   The database can initially be created from either server A or B.
   
4. The only database configuration files that are needed locally on both server A and B are those stored under the respective $ORACLE_HOME/dbs directories (or the database directory for Windows).
   
   That means, these files must be copied from the server where the database was created to the initially passive cluster node.
   
   The relevant files are, for example, the pfile/spfile and the passwordfile.
   
5. Other files that may have to be copied/adapted could be /etc/oratab, the Oracle Net configuration files in $ORACLE_HOME/network/admin and perhaps instance specific directories and files under $ORACLE_BASE/admin. However, some of these may also be located on shared storage.
   
6. To use the active/passive setup, only one instance must be up at any time.

NOTE:

1. There is no special certification needed for an active/passive setup as it is regarded as a single instance installation.
2. Configuration files copied from the one server to the other may require modification for the new host name. (example: The host name in listener.ora on the second node need to be corrected.)
3. Oracle as such does not support any automatic failover system as provided by the OS vendor or others.
   For support for that, please contact the appropriate vendor.

References

- How To Clone An Existing RDBMS Installation Using OUI
[@more@]