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

Answer 2:
Oracle automatically creates one database service when the database is
created. For many installations, using the default service is sufficient and
the default service is always started and does not require extra steps to
start. If a user needs more flexibility in the management of the workload
using the database, and creates some additional services, these services can
be started using the SGeRAC Toolkit in 2 ways:
1. The user can configure the OC MNP only and let the Oracle Clusterware
bring up the Oracle Services.
2. If both the OC MNP and RAC MNP are configured and the user has configured
additional services, the user is responsible for starting those additional
services.
J. SGeRAC Toolkit Limitation/Restriction
There are some restrictions and limitations in this release of SGeRAC Toolkit.
1. The SGeRAC Toolkit RAC MNP supports ASM over SLVM and ASM over HP-UX raw
disks/disk array logical units in SGeRAC environment. The Toolkit does
not support single instance using ASM over SLVM in the cluster.
2. The SGeRAC Toolkit OC MNP and RAC MNP do not restart the Oracle Clusterware
or RAC instances. After the RAC MNP is started and the corresponding
database instances are up and running, the RAC instances are under Oracle
Clusterware control.
3. Disk groups that are exclusively used by a RAC database should be managed
in separate ASMDG MNP. If two RAC databases use different ASM disk groups
then those ASM disk groups should not be configured in a single ASMDG MNP.
However, if two RAC databases use the same set of ASM disk groups then
those ASM disk groups can be configured in a single ASMDG MNP and then
both RAC MNP can be configured to have dependencies on the ASMDG MNP.
K. SGeRAC Toolkit Legacy Package to Modular Package Migration
For SGeRAC Toolkit A.11.17 and A.11.18 users, the migration from the SGeRAC
Toolkit legacy packages to modular packages can be done with the following
steps:
1. After backing up the legacy package directory, the user can do a rolling
upgrade one node at a time or can halt the entire cluster to upgrade to
SGeRAC A.11.19 or later version.
2. Shutdown the legacy RAC MNP if a RAC MNP is running.
: cmhaltpkg <legacy RAC MNP>
3. Create a new RAC MNP package working directory on one node, then cd to the
new package directory.
: cd /etc/cmcluster/RACMNP-Dir
4. Use the cmmigratepkg command to migrate the legacy RAC MNP to modular
format.
: cmmigratepkg -p <legacy RAC MNP> -s -o <RAC MNP output>
5. Create a new modular RAC MNP ascii file.
: cmmakepkg -i <RAC MNP output> -m sg/multi_node_all -m <toolkit module>
-t <RAC MNP configuration file> <new RAC MNP ascii file>
6. Edit the new RAC MNP ascii file, set the Toolkit parameters, refer to
section E-2 to verify and configure new modular RAC MNP parameters.
7. Now apply the package configuration file.
: cmapplyconf -P <new RAC MNP ascii file>
8. Shutdown the legacy OC MNP if the OC MNP is running.
: cmhaltpkg <legacy OC MNP>
9. Create a new OC MNP package working directory on one node, then cd to the
new package directory.
: cd /etc/cmcluster/OCMNP-Dir
10. Use the cmmigratepkg command to migrate the legacy OC MNP to modular
format.
: cmmigratepkg -p <legacy OC MNP> -s -o <OC MNP output>
11. Create a new modular OC MNP ascii file.
: cmmakepkg -i <OC MNP output> -m sg/multi_node_all -m <toolkit module>
-t <OC MNP configuration file> <new OC MNP ascii file>
12. Edit the new OC MNP ascii file, set the Toolkit parameters, refer to
section E-2 to verify and configure the new modular OC MNP parameters.
13. Now apply the package configuration file
: cmapplyconf -P <new OC MNP ascii file>
14. You may now start the new OC MNP and RAC MNP in the cluster using the
cmrunpkg or cmmodpkg –e commands.
15. After verifying the successful operation of the new OC MNP and RAC MNP
Support for the SGeRAC Toolkit 111