Using Serviceguard Extension for RAC Version A.11.20 - (August 2011)
H. SGeRAC Toolkit Supported Configurations
This version of Toolkit supports the following configurations. The maximum
number of nodes supported in SGeRAC Toolkit depends on the number of nodes
supported by SGeRAC with each storage management configuration. Refer to
"Number of nodes supported in SGeRAC for SLVM, CVM and CFS Matrix" posted on
http://www.hp.com/go/hpux-serviceguard-docs -> Serviceguard Extension for RAC.
------------------------------------------------------------------
Toolkit Multi-Node package | Storage Management | HP-UX version
------------------------------------------------------------------
Oracle Clusterware | SLVM raw | 11i v3
Oracle Clusterware | ASM over HP-UX raw | 11i v3
disks (For 11gR2 or later)
Oracle Clusterware | ASM over SLVM logical | 11i v3
volumes (For 11gR2 or later)
Oracle Clusterware | CVM raw(version 5.0.1)| 11i v3
Oracle Clusterware | CFS(version 5..1 SP1) | 11i v3
RAC Instance | CFS(version 5.1 SP1)) | 11i v3
RAC Instance | ASM over SLVM logical | 11i v2
| volumes
RAC Instance | ASM over HP-UX raw | 11i v3
disks
------------------------------------------------------------------
I. SGeRAC Toolkit Q & A
There are two configuration scenarios in this version of SGeRAC Toolkit.
Question 1:
In some configurations, the customer may not want to configure a RAC MNP
package, but instead wants Oracle Clusterware to control the startup of the
Oracle RAC instances, is this supported by the SGeRAC Toolkit?
Answer 1:
Yes, in this case, the customer can follow the setup steps in section F with
exception of steps 5, 13-18. and configure only the OC MNP using the SGeRAC
Toolkit, then the Istartup of OC MNP will bring up the Oracle RAC instance
also.
Question 2:
How to start a user defined Oracle Service in an SGeRAC Toolkit environment?
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.
Support for the SGeRAC Toolkit 109