Designing Disaster Recovery Clusters using Metroclusters and Continentalclusters, Reprinted October 2011 (5900-1881)

3. Ensure that the Site Controller Package is enabled on all nodes in the site where the database
must be started.
cmmodpkg –e –n <site A node 1> -n <site B node 2>\
<site_controller_package_name>
4. Start the Site Controller Package by enabling it.
cmmodpkg –e <Site Controller Package name>
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, you must check the package log
files for any errors that could 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 shut down appropriately.
It is recommended that you manage the RAC database startup and shutdown using the package
administration commands. Halting the RAC database using the Oracle interfaces, such as srvctl
and sqlplus, will cause the RAC MNP package to fail. 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.
However, special care must be taken when the Site Controller Package is halted after halting the
active RAC MNP stack on a site. The disaster tolerant RAC database cannot be started by starting
the RAC MNP stack packages as the Site Safety Latch is closed on both sites when the Site Controller
Package is halted in the cluster. 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. A maintenance operation on the RAC MNP package at a site can also
involve halting the RAC MNP package. Run the following command to halt the RAC MNP.
Administering the Site Aware Disaster Tolerant Metrocluster Environment 403