The CFS-DG-MP-MNP1 package manages the mount points and disk groups associated with the Oracle Clusterware package. The Oracle Clusterware package needs its associated storage to be up, and for this reason it needs to be dependent on the CFS-DG-MP-MNP1 package.

Similarly, the CFS-DG-MP-MNP2 package manages the mount points and disk groups associated with the Oracle RAC DB package. The RAC DB package again needs its associated storage to be up, and for this reason it needs to be dependent on the CFS-DG-MP-MNP2 package.

The SG-CFS-pkg (SMNP) is responsible for configuring and starting the CVM/CFS stack. The CFS-DG-MP-MNP1 and the CFS-DG-MP-MNP2 packages need CVM to be configured and running, and for this reason these packages need to be dependent on the SG-CFS-pkg (SMNP).

If a separate storage has been used for Oracle Clusterware software, then the storage information will be populated in the package configuration, so that the user is freed from having to activate the volumes, mount the file system, etc. This will be taken care of as part of the Oracle Clusterware package Easy Deployment.

Parameter discovery and default parameters

By way of automatic package parameter discovery by the Easy Deployment operation, the following Oracle

Clusterware package attributes are automatically populated in the corresponding configuration file:

•Cluster nodes

•Oracle Clusterware Home path

After finding the CFS storage location of the VOTE disk/OCR disk path, the Easy Deployment operation checks whether the required mount point and disk group packages are deployed or not. If these storage packages do not already exist in the cluster, the Easy Deployment operation automatically deploys these packages. Subsequently, a dependency on the required mount point packages is configured in the Oracle Clusterware package.

The following Oracle Clusterware parameters are initialized to predetermined values:

•Package name

–In a non-Metrocluster environment, this is set to sgerac_oc_pkg.

–In a site-aware Metrocluster environment, the site_id will be appended to the package name (sgerac_oc_pkg_<site_id>).

•Package type

•Toolkit directory

The Oracle Clusterware package working directory is set to /etc/cmcluster/sgerac_oc_pkg/ in a non-Metrocluster environment. In a site-aware Metrocluster environment, the Oracle Clusterware package working directory is set to /etc/cmcluster/sgerac_oc_pkg_<site_id>/. All other package parameters will be set to default values in accordance to the manual http://www.hp.com/go/hpux-serviceguard-docs -> HP Serviceguard Extension for RAC. Please refer to the same for more details on default package parameters.

Error and exception handling

An error message will appear in the Serviceguard Manager package Easy Deployment operation log window if the Oracle Clusterware package deployment fails for one or more of the following reasons:

•The cluster configured with a non-Metrocluster environment already has a non OC package configured for any other third-party application with the name sgerac_oc_pkg, or in a site-aware Metrocluster a non-OC package with the name sgerac_oc_pkg_<site_id> already exists, configured for any other third-party application on a given site.

•An unexpected error occurs during the Oracle Clusterware package deployment operation.

18