cmhaltpkg <RAC MNP package name>
Because the RAC MNP is down, as it is halted in the cluster, 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 will remain 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 MNP package can only be started by restarting the Site Controller Package. This is because the Site Safety Latch closes when the Site Controller Package halts.
Maintaining Oracle Database 10gR2 RAC
A RAC database configured using SADTA has two replicas of the RAC database configuration; one at each site. The database configuration is replicated between the replicas using a replicated storage. Most of the maintenance changes done at the site with the active database configuration is propagated to the other site. However, some changes, such as service configuration, and Oracle patch installation, are not replicated. Such maintenance operations must be performed on the RAC database configurations at both the sites. For more information on maintaining an Oracle RAC database, see the Oracle documentation. You must also see the Serviceguard Extension for Oracle RAC manual available at
To complete maintenance operations that require that the RAC database or its instance to be halted, requires the SGeRAC toolkit MNP package in the cluster or its instance to be halted. Run the following command to halt the SGeRAC MNP package:
cmhaltpkg <RAC MNP package name>
The Site Controller Package does not interpret halting of the RAC MNP Stack package as a failure and continues to run uninterrupted. Once the maintenance procedures are complete, restart the RAC MNP package. 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 was halted for maintenance, the RAC MNP stack can only be started by restarting the Site Controller Package.
Moving a Site Aware Disaster Tolerant Oracle RAC Database to a Remote Site
To perform maintenance operations that require the entire site to be down, you can move the disaster tolerant Oracle RAC database to a remote site. To move the RAC database to a remote site, the local RAC database configuration must be first shut down and then the remote RAC database configuration must be started.
Complete the following procedure to move the database to a remote site:
1.Halt the Site Controller Package of the RAC database. cmhaltpkg <site_controller_package_name>
2.Ensure the RAC MNP stack packages are halted successfully. cmviewcl
3.Start the Site Controller Package on a node in the remote site. cmrunpkg <site_controller_package_name>
The Site Controller Package starts up on a node in the remote site and starts the RAC MNP stack packages that are configured.
404 Designing a Disaster Recovery Solution Using Site Aware Disaster Tolerant Architecture