HP Serviceguard Linux Oracle-Toolkit-A.05.01.00 User Guide (696983-001, June 2012)

Oracle single instance failover packages dependent on this MNP. This configuration enables the
database instance to start up in the right order in relation to the ASM instance, and in the event
of a failover, to relocate only to a node where an ASM instance is available.
To configure Oracle database using ASM in a Serviceguard environment:
1. Configuring ASM in a Serviceguard environment and creating the ASM instance.
a. Configure logical volumes or devices to be used in the ASM disk groups.
b. Install the ASM binaries on local storage in ASM_HOME on all the nodes.
c. Create the ASM instance on one node. Create disk groups and specify the raw logical
volumes or raw devices configured to be a part of the disk groups on that node.
d. Create the ASM instance on the other nodes and specify the ASM_DISKSTRING on each
node. There is no need to create the disk groups on these nodes.
2. Creating the Oracle database in a Serviceguard environment.
a. Install the Oracle binaries on local storage in ORACLE_HOME on all the nodes configured
in the cluster.
b. Create the database instance on one node.
c. Specify the storage type as ASM and provide the disk groups that the database instance
will use.
d. Optional: Configure a listener.
e. Copy the parameter file or server parameter file of the database instance to all the nodes.
f. Distribute the listener configuration file, listener.ora from $ORACLE_HOME/network/
admin if you configure a listener.
g. Copy the directories from $ORACLE_BASE/admin to all the nodes.
h. Halt the ASM instance, database instance, and the listener (if configured) on all the nodes.
10 Supported configuration