HP Serviceguard Extension for RAC (SGeRAC) manual Asmtkitdir

OC_TKIT_DIR

Set to the OC MNP working directory. When MAINTENANCE_FLAG is yes, the RAC MNP uses this parameter to check the OC MNP maintenance status: If the OC MNP MAINTENANCE_FLAG is set to yes and oc.debug is in the OC_TKIT_DIR directory, the RAC MNP knows the OC MNP on the same node is in maintenance mode. In this case, because of the dependency on the OC MNP, the RAC MNP will go into maintenance mode as well regardless of the presence of its debug file.

If the MAINTENANCE_FLAG is set to no, OC_TKIT_DIR is not required, and the RAC MNP will not check the OC MNP's maintenance status.

ASM_TKIT_DIR

Note: this parameter should be set only if the new ASM DG MNP is being used. Set this to the ASM MNP working directory. When the MAINTENANCE_FLAG is yes, it is used to check the ASMDG MNP maintenance status.

F. SGeRAC Toolkit configuration Procedures

To use the SGeRAC Toolkit in an environment running with SGeRAC and Oracle 10g R2 or later version/revision of RAC, you must disable the automatic start feature for the Oracle Clusterware and the RAC instances which are configured and managed in the Toolkit MNP. Since both modular and legacy package formats

are supported in SGeRAC A.11.19 and later, the guidelines for configuring and using the SGeRAC Toolkit in the combined stack environment are described in several

steps.

The sequence for the modular package setup are F-1, F-2, F-4, F-5, F-8 and F-10. The sequence for the legacy package setup are F-1, F-3, F-4, F-9 and F-10.

The steps are as follows:

F-1. SGeRAC Toolkit pre-setup [For both modular and legacy packages]

1.Install and configure the SGeRAC cluster. Refer to the HP manual "Managing Serviceguard" for more details.

2.Prepare storage for Oracle Clusterware and RAC database. Refer to HP manual "Using Serviceguard Extension for RAC" for more details. For the configuration of ASM over SLVM logical volumes, refer to HP whitepaper "Support of Oracle RAC ASM with SGeRAC" for more information.

3.Install and configure Oracle Clusterware and RAC database instance. Refer to the Oracle Real Application Cluster Installation documents and "Oracle Real Application Clusters Administrator's Guide" for more details.

4.On each node of the cluster, disable the automatic startup of the Oracle Clusterware at boot time.

Login as root and enter:

:$ORA_CRS_HOME/bin/crsctl disable crs

5.On one node of the cluster, disable the Oracle RAC database and instances from being started automatically by the Oracle Clusterware.

Login as the Oracle administrator and run the following command to set the database management policy to manual.

For Oracle 10g:

:$ORACLE_HOME/bin/srvctl modify database -d <dbname> -y manual

For Oracle 11g:

:$ORACLE_HOME/bin/srvctl modify database -d <dbname> -y MANUAL F-2. OC MNP creation procedures [For Modular Package]:

1.On one node of the cluster, create an OC MNP working directory under /etc/cmcluster.

The following step requires root privilege.

:mkdir /etc/cmcluster/OCMNP-Dir

2.Go to step 3 if you don't want to test the oc.conf file before configuring OC MNP. Otherwise copy the OC MNP configuration file located in the Toolkit directory /opt/cmcluster/SGeRAC/toolkit/crsp to the OC MNP working directory. Then edit and test the configuration file oc.conf on one node based on the description in E-2 to fit your Oracle environment.

All the following steps require root privilege.

:cd /etc/cmcluster/YourOwn-OCMNP-Dir

:cp /opt/cmcluster/SGeRAC/toolkit/crsp/oc.conf .

3.Generate the OC MNP configuration file and edit the file based on the description in E-1-1. Then configure the OC MNP.

If oc.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_oc -t oc.conf pkgConfigFile.

Otherwise, create the package configuration file and set the Oracle

Support for the SGeRAC Toolkit 105