Using the Oracle Toolkit in a HP Serviceguard Cluster README Revision: B.06.00, August 2010

To use CFS, you must install the appropriate version of HP
Serviceguard Storage Management Suite.
For more details please refer to the Serviceguard Release Notes at:
http://www.hp.com/go/hpux-serviceguard-docs -> HP Enterprise Cluster
Master Toolkit
NOTE:
This toolkit supports Oracle 10g Release 2 ASM and 11g R1 and 11g R2
ASM on LVM only. Oracle 10g Release 2 ASM and 11g R1 and 11g R2 is
not supported with CFS.
C. Support For Oracle Database without ASM
Oracle must be installed in the same location on all cluster nodes
that will run the package. All database instance parameters are
stored in an instance parameter file init${SID_NAME}.ora (commonly
referred to as "pfile"), where "SID_NAME" refers to the database
instance session ID. The text version of the parameter file is
referred to as a pfile, while the binary format is called the spfile.
At startup, Oracle reads the initialization parameters from the
pfile. During execution, as parameters are dynamically altered,
Oracle saves the new values to an spfile. 'pfile' and 'spfile' can
be created from one to the other. Oracle needs to start the instance
for the first time (database creation time) using the pfile, then the
spfile can be created.
The database server can be configured in two different ways:
* (local configuration) by putting the configuration files on a
single node, then replicating the files to all other nodes in the
cluster
* (shared configuration) with configuration files in a shared file
system
Local Configuration
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
If you choose to store the configuration files on a local disk, the
configuration MUST be replicated to local disks on all nodes
configured to run the package. The Oracle binaries reside on
the local storage. If any change is made to the configuration,
the file must be copied to all nodes. The user is responsible to
ensure that the system configurations remain synchronized.
Shared Configuration
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Here, the configuration and database files are on shared disks,
visible to all nodes with the Oracle binaries on the shared or local
storage. Since the storage is shared, there is no additional work