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

But, it does not clean any of the managed packages for the Site Controller Package. Any issues
in the packages managed by Site Controller Package must be fixed by the operator and the
package’s node switching must be enabled before restarting the Site Controller Package.
When the Site Controller Package has failed, the following message appears in the Site Controller
Package log file on the node where it was last running or was last started:
Check the package log files on all nodes of all other packages managed
by the Site Controller Package to identify issues in those packages.
Complete the following steps to clean a site for a site aware disaster tolerant application:
1. Clean the Site Safety Latch on the site by running the cmresetsc tool.
On a node from the site, run the following command:
/usr/sbin/cmresetsc <Site_controller_package_name>
IMPORTANT: You must be root user to run this command.
2. Check the package log file of the Site Controller Package on the node it failed on and fix any
reported issues.
3. Enable node switching for the Site Controller Package on that node.
cmmodpkg –e -n <node name> <site_controller_package_name>
4. Check the package log file on all nodes of the MNP packages managed by the Site Controller
Package on the site.
5. Fix any issues reported in the package log files and enable node switching for the MNP
packages on the failed nodes.
cmmodpkg -e -n <node 1 name> -n <node 2 name> <MNP Package name>
6. Restart the Site Controller Package and enable global switching.
cmrunpkg <site_controller_package_name>
cmmodpkg -e <site_controller_package_name>
In addition to the cmresetsc tool, use the cmviewsc tool to view information on the Site Controller
Package managed workload package. This tool is available in the /usr/sbin directory. Run the
following command to use the cmviewsc tool.
/usr/sbin/cmviewsc [-v] [site_controller_package_name]
Following is the information displayed by this tool:
• Number of critical and managed packages at each site.
• Status of the Site Controller managed packages (halted or started).
• Site Controller managed packages halted cleanly or not.
• Site active or passive.
• Site Safety Latch value on each node. The value can be Close, Open or Intermediate.
For more information on using cmviewsc, see cmviewsc(1m).
Identifying and Cleaning RAC MNP Stack Packages that are Halted
The Site Controller Package does not start if the RAC MNP stack packages are not halted clean.
An MNP package is halted unclean when the halt script does not run successfully on all the
configured nodes of the package. This implies that there might be some stray resources configured
with the package, that are online in the cluster. The Site Controller Package logs the following
message in its log file on the node where it failed to start:
Package <package name> has not halted cleanly on node <node name>
The following command shows whether an MNP package halt was clean or unclean:
406 Designing a Disaster Recovery Solution Using Site Aware Disaster Tolerant Architecture