HP Serviceguard Enterprise Cluster Master Toolkit User Guide, December 2012 (5900-2145)

• To start the ASM instance on all the configured nodes, invoke cmrunpkg on the ASM MNP.
• Configure the database failover package using the ECMT Oracle scripts. You must follow HP
instructions in the READ me file.
• To start the database instance on the node, invoke cmrunpkg on the database package. For
troubleshooting, look at subdirectories for database and ASM instances under
$ORACLE_BASE/admin/, where log and trace files for these instances are deposited. Also
look at HP-UX syslog and Serviceguard package logs.
Setting up DB instance and ASM instance
This section describes the sequence of steps to be followed to set up an ASM instance or a database
instance using ASM storage.
Configuring ASM in a Serviceguard environment and creating the ASM instance
1. Configure the raw logical volumes to be used in the ASM disk groups as mentioned in the
whitepaper "High Availability Support for Oracle ASM with Serviceguard" present at: http://
www.hp.com/go/hpux-serviceguard-docs -> HP Enterprise Cluster Master Toolkit
Assign the right set of ownership and permissions to the raw logical volumes (Oracle:dba and
0660 respectively).
2. Install the ASM binaries on local storage in ASM_HOME on all the nodes. ASM can have its
own home to keep the database and ASM homes separate and to have a simpler configuration.
Install interim patches 7330611 and 7225720 on all the nodes (these patches are not required
for 11gR2). Verify that the patch is installed correctly on all the nodes. Set your current directory
to where the patch is located. Issue command opatch lsinventory to check that the
Oracle inventory is set up properly on all the nodes.
3. Create the ASM instance on one node. Create disk groups and specify the raw logical volumes
configured to be members of the disk groups on that node.
4. 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.
ASM_DISKSTRING is an initialization parameter that specifies a comma-separated list of
strings that limits the set of disks that ASM discovers.
Creating an Oracle database on an ASM disk group in a Serviceguard environment.
1. Install the Oracle binaries on local storage in ORACLE_HOME on all the nodes configured in
the cluster.
2. Create the database instance on one node. Specify the storage type as Automatic Storage
Management and provide the disk groups that the database instance is going to use.
3. Configure a listener (if required).
4. Copy the parameter file or server parameter file of the database instance to all the nodes,
because the Oracle binaries are installed on local storage on all the nodes.
5. Distribute the listener.ora file which is the listener configuration file from
$ORACLE_HOME/network/admin, if a listener is configured.
6. Copy the directories from $ORACLE_BASE/admin to all the nodes. Halt the database instance,
listener, and the ASM the instance, (if configured) on all the nodes.
Setting up DB instance and ASM instance 39