HP Enterprise Cluster Master Toolkit User Guide (5900-2131, December 2011)

NOTE: If you opted to store the configuration information on a local disk and propagate
the information to all nodes, ensure that pfile/spfile, the password file, and all control files
and data files are on shared storage. For this set up, you will need to set up symbolic links to
the pfile and the password file from /home/oracle/dbs as follows:
ln -s /ORACLE_TEST0/dbs/initORACLE_TEST0.ora \
${ORACLE_HOME}/dbs/initORACLE_TEST0.ora
ln -s /ORACLE_TEST0/dbs/orapwORACLE_TEST0.ora \
${ORACLE_HOME}/dbs/orapwORACLE_TEST0.ora)
• Multiple Instance Configuration
If multiple instances will be run in the same cluster, repeat the preceding steps for each
instance. For example, if a second instance (ORACLE_TEST1) is to be included in the
configuration you would:
◦ For LVM
Create a second volume group (for example, /dev/vg0_ORACLE_TEST1), logical
volume and filesystem with mount point (/ORACLE_TEST1) for the second instance.
All configuration information for ORACLE_TEST1 will reside in /ORACLE_TEST1/dbs.
Similar to ORACLE_TEST0, symbolic links need to be created for all subdirectories
(other than /ORACLE_TEST1/dbs/), to link /ORACLE_TEST1 to /home/oracle.
◦ For VxVM
Create a second disk group (example, /dev/vx/dsk/DG0_ORACLE_TEST1), logical
volume and filesystem with mount point (/ORACLE_TEST1) for the second instance.
All configuration information for ORACLE_TEST1 will reside in /ORACLE_TEST1/dbs.
Similar to ORACLE_TEST0, symbolic links need to be created for all subdirectories
(other than /ORACLE_TEST1/dbs/), to link /ORACLE_TEST1 to /home/oracle.
◦ For CFS
Create another directory /ORACLE_TEST1. Another CFS file system would then be
mounted on /ORACLE_TEST1 by the Serviceguard CFS packages. All configuration
information for ORACLE_TEST1 will reside in /ORACLE_TEST1/dbs. Similar to
ORACLE_TEST0, symbolic links need to be created for all subdirectories (other than
/ORACLE_TEST1/dbs/), to link /ORACLE_TEST1 to /home/oracle.
This configuration makes it possible to run several Oracle instances on one node,
facilitating failover or failback of Oracle packages between nodes in the cluster.
• Here is an alternate setup for Oracle 10g/11g single-instance database:
If you are using LVM or VxVM (supported on Oracle 10gR2 and 11g only):
For nodes that will run only one database instance, the configuration described
above could be simplified by installing Oracle entirely on the shared volume/file
◦
system (/ORACLE_TEST0, in our example). The installation is simplified, since no
symbolic links are required. In this case, all Oracle binaries and configuration is
migrated to the standby node on failover.
Support For Oracle Database without ASM 11