which is read by the Toolkit script oc.sh.
oc.check - Toolkit monitor script that checks if the Oracle Clusterware is running.
oc.sh - Toolkit script to start, stop, and check the Oracle Clusterware.
The files under /opt/cmcluster/SGeRAC/toolkit/racp are for the RAC MNP:
toolkit_dbi.sh - The entry point to the Toolkit entity. It is an interface between the RAC database instance MNP package control script and the rac_dbi.* files listed below.
rac_dbi.conf - The Toolkit configuration file that contains a list of
rac_dbi.check - Toolkit monitor script that checks if the RAC instance is running.
rac_dbi.sh - Toolkit script to start, stop, and check the RAC instance.
The files under /opt/cmcluster/SGeRAC/toolkit/asmp are for the ASMDG MNP:
toolkit_asmdg.sh - The entry point to the Toolkit entity. It is an interface between the ASMDG MNP package
control script and the asm_dg.* files listed below.
asm_dg.conf - The Toolkit configuration file that contains a list of
file which is read by the Toolkit script asm_dg.sh.
asm_dg.check - Toolkit monitor script that checks if the ASM disk group is mounted or not.
asm_dg.sh - Toolkit script to mount, unmount and check the status ASM disk group.
E. SGeRAC Toolkit Configuration
The OC MNP supports storage management using SLVM, CVM, CFS, ASM ( For 11gR2 or later versions of RAC only) and ASM over SLVM (For 11gR2 or later versions of RAC only). The RAC MNP supports storage management using SLVM, CVM, CFS, ASM or ASM over SLVM. Users should follow the storage configuration procedures required by SLVM, CVM, CFS, ASM or ASM over SLVM respectively to configure the storage for Oracle Clusterware (OCR and voting disk) and RAC database (control files, data files,
Certain package parameters and some specific parameter values are needed when configuring the Toolkit MNPs. In addition, some Toolkit specific configurations are needed in the Toolkit configuration file. The following sections contain the parameters and values required by the SGeRAC Toolkit.
The SGeRAC Toolkit for SGeRAC A.11.19 and later supports both modular and legacy package formats, these two different formats are described as below:
For modular packages, it is not necessary to create a package script file, and the package configuration file template can be created by running the Serviceguard command "cmmakepkg
<toolkit module name>
For the OC MNP:
package_name
Set to any name desired for the OC MNP.
package_type
Set by default to multi_node
package_description
Set by default to "SGeRAC Toolkit Oracle Clusterware package"
node_name
Specify the names for the nodes that the OC MNP will run on.
auto_run
Set to yes or no depending on whether the OC MNP is to be started on cluster join or on demand.
local_lan_failover_allowed
Set by default to yes to allow cluster to switch LANs locally in the event of a failure.
node_fail_fast_enabled Set by default to no.
