Edit the package template files based on the description in
4.Now apply the package configuration file: : cmapplyconf
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.
:
:
:cp /opt/cmcluster/SGeRAC/toolkit/racp/* .
2.Edit the configuration file rac_dbi.conf based on the description in
3.Generate the package configuration file and control scripts for the RAC MNP.
:cmmakepkg
:cmmakepkg
Edit the package template files based on the description in
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
1.On one node of the cluster, start the RAC MNP via cmrunpkg. : cmrunpkg
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
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
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
the MNP will be started automatically when the cluster starts up or when the node joins the cluster. After the Oracle Clusterware and RAC instances are started in the MNP packages, users should not manage (halt or restart) Oracle Clusterware and RAC instances outside of the package, otherwise the package could fail.
If a node is added to the cluster and will run a RAC instance, the OC MNP and ASMDG MNP and the corresponding RAC MNP must be modified and reapplied to add the node into the package configuration. If a node running the RAC instance is deleted from the cluster, the OC MNP and ASMDG MNP and the corresponding RAC MNP must be modified and reapplied to delete the node from the package configuration.
If TKIT_SCRIPT_DIR is not set to default value, copy the new OC MNP, ASMDG MNP and RAC MNP scripts to the TKIT_SCRIPT_DIR directory from the respective location of /opt/cmcluster/SGeRAC/toolkit/ when SGeRAC upgrade is done or when an SGeRAC patch is installed.
If a node running the OC MNP and RAC MNP is to be shutdown via command /etc/shutdown, users should run "cmhaltnode
If the Oracle Clusterware or RAC software is being upgraded then it is recommended to bring down the OC MNP, ASMDG MNP (if configured) and RAC MNP packages and start Oracle Clusterware and Database using Oracle commands crsctl and srvctl. After completion of the upgrade, update (if there are any changes) the configuration files of the above mentioned packages as needed and restart the packages.
