Building Disaster Recovery Serviceguard Solutions Using Metrocluster with Continuous Access for P9000 and XP A.11.00
For more information about 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:
cmviewcl –v –f line <MNP Package name>
Verify for the field last_halt_failed under every instance of the MNP package. When set to
Yes, that instance of the MNP package did not successfully execute the halt script when it was
halted. Find for all the instances.
The unclean nodes might have stray resources. See the MNP package log file on the corresponding
node to identify the reason for the halt script run failure. Clean any stray resources that are still
online in the node and enable node switching on the node for the package. This clears the flag
and allows the Site Controller Package to start. Complete this procedure for all the nodes where
the MNP package instance has halted unclean.
cmmodpkg –e -n <node name> <MNP Package name>
Understanding Site Controller package logs
This section describes the various messages that are logged in the log files and the methods to
resolve those error messages.
Table 9 describes the error messages that are displayed and the recommended resolution.
Table 9 Error Messages and their resolution
ResolutionCauseLog Messages
The critical package at
siteA is still running.
Starting Site Controller (hrdb_sc) on site siteB.
Site safety latch at site siteA is open.
1. Clean the nodes on siteA and enable
node switching for the Site Controller
Package.
Verifying if site failover conditions are met.
2. Restart the Site Controller Package on
siteA.
Critical package hrdb at site siteA is up.
Error: Site failover conditions are not met.
Unexpected Site Controller startup.
Unable to initiate site failover at site SiteB.
Site Controller startup failed.
An MNP package
managed by the Site
Starting Site Controller (hrdb_sc) on site siteB.
Site safety latch at site siteA is open.
1. Verify the MNP package log on all the
nodes on which it failed to run the halt
script successfully.Controller Package at
siteA has not halted
Verifying if site failover conditions are met.
2. Clean any stray resources that are still
online on the node.
clean on at least one of its
nodes.
Package hrdb has not halted cleanly on node
<node name>.
3. Re-enable node switching for the MNP
package on the node.
Unable to initiate site failover at site siteB.
4. Restart the Site Controller Package.
Site Controller startup failed.
Start the Site Controller Package on the site
where it was previously halted in the
DETACH mode.
The Site Controller was
halted in the
DETACHmode at site
siteA.
Starting Site Controller (hrdb_sc) on site siteB.
Site safety latch at site siteA is open.
Verifying if site failover conditions are met.
Error: Site failover conditions are not met.
Unexpected Site Controller startup.
Troubleshooting Metrocluster SADTA 85