HP Serviceguard Toolkit for Oracle on Linux User Guide Version A.12.00.00

3 Supported configuration
This section explains the following supported configurations for Oracle database toolkit packages:
• Without Automatic Storage Management (ASM)
• With Automatic Storage Management
Without Automatic Storage Management
This section explains how to configure an Oracle database instance package without ASM in a
Serviceguard environment. You can configure Oracle database instance package using one of
the following ways:
• Shared configuration
• Multiple instance configuration
Shared configuration
In this configuration method, the configuration and database files are kept on shared disks but you
can place the Oracle binaries on the local storage. Since the configuration files and data files
reside on a shared location, you need not ensure that all the nodes have the same configuration.
Alternatively, you can place the Oracle binaries too on the shared location along with the
configuration and database files.
A password file that is, orapw${SID_NAME} must be created for each Oracle instance in the
configuration directory. The password file is created via the orapwd utility.
To use HP Serviceguard toolkit for Oracle with Oracle 10g, ensure that all the Oracle binaries
reside locally on each cluster node and do not reside on a shared volume group. You can use one
of the following steps:
• Install Oracle 10g and 11g software on all the cluster nodes. Ensure that the database related
files (that is, all control files, data files, and log files) reside on a shared volume group. The
Oracle binaries however, reside locally on each node.
• Install Oracle 10g and 11g software on all the cluster nodes. Place the Oracle binaries as
well as the database related files on a shared volume group.
NOTE:
• The Oracle binaries can reside on a shared disk for Oracle 11g. For Oracle 11g, if the
binaries are located on shared disk, then do not configure Oracle ASM on that node.
• If multiple Oracle database instances are configured, you cannot use shared storage to keep
the Oracle binaries. If you are configuring multiple instances of Oracle db, HP recommends
that you keep the Oracle binaries only on a local storage.
• HP recommends that you use local storage for Oracle binary installation. During a Oracle
patch update, the toolkit allows users to run the oracle instance on any other package nodes
during a failure.
Multiple instance configuration
Oracle supports multiple DB instances running on a node, simultaneously. This allows you to move
one instance from its own node while leaving another instance up. Each node runs several instances.
Each Oracle package corresponds to a separate Oracle database server instance with its own
SID_NAME, unique volume group, logical volume, and file system for storing control files, data
files, and redo-log files. The configuration details for each instance must be identical for each node
configured to run that instance.
10 Supported configuration