Building Disaster Recovery Serviceguard Solutions Using Metrocluster with 3PAR Remote Copy

The Site Controller Package starts on the preferred node at the site. At startup, the Site Controller
Package starts the corresponding RAC MNP stack packages in that site that are configured as
managed packages. After the RAC MNP stack packages are up, check the package log files for
any errors that must have occurred at startup.
If the CRS MNP instance on a node is not up, the RAC MNP stack instance on that node does not
start. However, if CVM/CFS is configured, the CVM DG and CFS MP MNP will start.
Shutting down a disaster tolerant Oracle database 10gR2 RAC
The disaster tolerant RAC database can be shutdown by halting the Site Controller Package of the
corresponding database. To shutdown the database, run the following command on any node in
the cluster:
# cmhaltpkg <site_controller_package_name>
This command halts the Site Controller Package and the current active RAC MNP stack of the
database. After shutting down, check the Site Controller Package log file and the RAC MNP stack
package log files to ensure that the database shuts down appropriately.
HP recommends that you manage the RAC database startup and shutdown using the package
administration commands. RAC MNP package fails if you halt the RAC database using the Oracle
interfaces, such as srvctl and sqlplus. The Site Controller Package interprets this as a failure
and initiates a site failover, which is not necessary.
Halting and restarting the RAC database MNP packages
The RAC MNP stack of the active database of a disaster tolerant RAC database can be shutdown
without impacting the remaining disaster tolerant infrastructure. The Site Controller Package can
continue to run on the site where the active database is running. Run the following command to
halt the RAC MNP package of the active database:
# cmhaltpkg <RAC MNP Package name>
To halt all RAC MNP stack packages, including the CFS MP and CVM DG MNP packages, specify
all the package names with the cmhaltpkg command.
This command halts all RAC MNP stack packages. The Site Controller Package continues to run
and does not initiate a site failover. You can restart the RAC MNP stack later on the same site
using the cmrunpkg command as long as the Site Controller Package is running on this site.
When the Site Controller Package is halted in the cluster, the disaster tolerant RAC database cannot
be started by starting the RAC MNP stack packages because the Site Safety Latch is closed on
both sites. In this case, the disaster tolerant RAC database can be started only by restarting the
Site Controller Package in the cluster.
To restart the database at the same site, the Site Controller Package must be started on that site.
Maintaining Oracle database 10gR2 RAC MNP packages on a site
The RAC MNP package is a SGeRAC toolkit package. To complete maintenance procedures on
the RAC MNP package, follow the procedures recommended by the SGeRAC toolkit for RAC MNP
package maintenance. You must halt the RAC MNP package to perform a maintenance operation
on the RAC MNP package at a site. Run the following command to halt the RAC MNP.
# cmhaltpkg <RAC MNP package name>
When the RAC MNP is halted in the cluster, it is down, therefore the Site Controller Package does
not interpret it as a failure. The Site Controller Package continues to run on the same site and the
Site Safety Latch remains open.
After the maintenance procedures are complete, restart the RAC MNP package at the same site.
Run the following command to restart the RAC MNP package:
# cmrunpkg <RAC MNP package name>
However, if the Site Controller Package is halted while the RAC MNP package is halted for
maintenance, it results in the RAC MNP stack on that site shutting down. In this scenario, the RAC
98 Configuring Oracle RAC in SADTA