Using Serviceguard Extension for RAC, 10th Edition, April 2011

NOTE: To configure another ASMDG MNP package to manage the ASM disk group
used by a different RAC Database, repeat the steps in F-6 and F-7.
F-8. RAC MNP creation procedures [For Modular Package]:
1. On one node of the cluster, create a RAC MNP working directory under
/etc/cmcluster.
: mkdir /etc/cmcluster/YourOwn-RACMNP-Dir
2. Go to step 3 if you don't want to test the rac_dbi.conf before configuring
the RAC MNP. Otherwise copy the RAC MNP configuration file located in the
Toolkit directory /opt/cmcluster/SGeRAC/toolkit/racp to the RAC MNP
working directory. Then edit and test the configuration file rac_dbi.conf
based on the description in E-2 to suit your Oracle environment.
: cd /etc/cmcluster/YourOwn-RACMNP-Dir
: cp /opt/cmcluster/SGeRAC/toolkit/racp/rac_dbi.conf .
3. Generate the package configuration file for the RAC MNP.
If rac_dbi.conf is configured and tested in step 2, use the following
command to create the package configuration file:
: cmmakepkg -m sg/multi_node_all -m sgerac/erac_tk_rac -t rac_dbi.conf
pkgConfigFile
Otherwise, create the package configuration file and set the Oracle
Clusterware parameters in this file directly:
: cmmakepkg -m sg/multi_node_all -m sgerac/erac_tk_rac pkgConfigFile
Edit the package template files based on the description in E-1.
4. Now apply the package configuration file:
: cmapplyconf -P pkgConfigFile
F-9. RAC MNP creation procedures [For Legacy Packages]:
1. On one node of the cluster, create a RAC MNP working directory
under /etc/cmcluster and copy over the files in the Toolkit
directory /opt/cmcluster/SGeRAC/toolkit/racp.
: mkdir /etc/cmcluster/YourOwn-RACMNP-Dir
: cd /etc/cmcluster/YourOwn-RACMNP-Dir
: cp /opt/cmcluster/SGeRAC/toolkit/racp/* .
2. Edit the configuration file rac_dbi.conf based on the description in E-2
to suit your Oracle environment.
3. Generate the package configuration file and control scripts for the RAC
MNP.
: cmmakepkg -p pkgConfigFile
: cmmakepkg -s pkgControlScript
Edit the package template files based on the description in E-1-2 and
E-1-3, and make sure that the pkgControlScript is executable.
4. Create the RAC MNP working directory on all other participating nodes.
Distribute the edited package configuration file, package control
script, and the Toolkit scripts created in steps 2 and 3 to all nodes. Now
apply the package configuration file from one node :
: cmapplyconf -P pkgConfigFile
F-10 Oracle RAC MNP startup procedures: [For both Modular and Legacy packages]
1. On one node of the cluster, start the RAC MNP via cmrunpkg.
: cmrunpkg Your-RACMNP-Name
Use cmviewcl to check the package status.
2. After the package is up and running, verify that the RAC instance is
running.
On one node of the cluster, login as the Oracle administrator and enter:
:$ORACLE_HOME/bin/srvctl status instance -d $databaseName -i $instanceName
Messages like the following should be seen:
Instance <InstanceName> is running on node <NodeName>
3. If more than one RAC database is configured in the cluster and the RAC
instances are to be managed in the RAC MNP, repeat the steps in F-9 and
steps 1 and 2 in F-10 for each RAC database.
G. SGeRAC Toolkit Administration
The Toolkit OC MNP and RAC MNP and ASMDG MNP are administrated using
Serviceguard package commands. To start the MNP when the SG/SGeRAC cluster
is up and running, use cmrunpkg or cmmodpkg to start all instances, or use
cmrunpkg or cmmodpkg with the option "-n nodeName" to start a single instance
Support for the SGeRAC Toolkit 109