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

Table 30 Error Messages and their Resolution (continued)
ResolutionCauseLog Messages
This message is logged
because the Site
Unable to execute command.
Dependency on the following packages not
met: crspkg.
1. Check the log file of the failed package.
2. Identify and fix the problem. It is
possible that the CRS MNP packages
are not running.
Controller Package has
failed to start one or more
packages that it manages.
cmrunpkg: Unable to start some package or
package instances.
3. Enable node switching for the failed
MNP package.
This situation occurs
because the package
Check the log files of the packages managed
by Site Controller for more details.
4. Clean the site using the cmresetsc
tool.
dependency configured
for the packages that
Check for any error messages in the package
log file on all nodes in the site siteA for the
5. Restart the Site Controller Package.
failed is not met on this
site.
packages managed by Site Controller (
hrdb_sc )
Fix any issue reported in the package log files
and enable node switching for the packages
on nodes they have failed.
Reset the site siteA using cmresetsc command
and start hrdb_sc again Site Controller startup
failed.
This message is logged
because the previous
Starting Site Controller(hrdb_sc) on site siteA.
Previous startup of Site Controller (hrdb_sc) on
the site siteA has failed
1. Check the log files of all the packages
managed by Site Controller Package on
the site.startup of the Site
Controller Package failed
on the local site siteA.
2. Identify the issues and fix them.
Clean up the site siteA and start hrdb_sc again
3. Enable node switching for the package
managed by the Site Controller Package
on the site.
Check for any error messages in the package
log file on all nodes in the site siteA for the
packages managed by Site Controller
(hrdb_sc).
4. Clean the site using the cmresetsc
tool.
Fix any issue reported in the package log files
and enable node switching for the packages
on nodes they have failed.
5. Restart the Site Controller Package.
Reset the site siteA using cmresetsc command
and start hrdb_sc again.
Site Controller startup failed.
This message is logged
because the previous
Starting Site Controller (hrdb_sc) on site siteB.
Site Controller start up on the site siteA has
failed.
1. Check the log files of all the packages
managed by Site Controller Package on
the remote site.start-up of the Site
Controller Package failed
2. Identify and issues and fix them.
Clean up the site siteA and start hrdb_sc again.
on the remote site. In this
3. Enable node switching for the package
managed by Site Controller Package on
the other site.
Fix any issue reported in the package log files
and enable node switching for the packages
on nodes they have failed.
case, the remote site is
siteB.
4. Clean the remote site using the
cmresetsc tool on a node in the other
site.
Reset the site siteA using cmresetsc command
and start hrdb_sc again.
5. Restart the Site Controller Package.
Site Controller startup failed.
This message is logged
because one of the
Executing: cmrunpkg siteA_mg1 siteA_mg2.
siteA_mg3.
1. Check the log file of the package on the
nodes where node switching is not
enabled.packages managed by
the Site Controller
Unable to run package siteA_mg1 on node
ccia6, the node switching is disabled.
2. Clean any stray resources owned by the
package, that are still online on the
node.
Package has failed to start
at this site.
Unable to run package siteA_mg1 on node
ccia7, the node switching is disabled.
3. Enable node switching for the package
on the nodes.
cmrunpkg: Unable to start some package or
package instances.
4. Clean the site using the cmresetsc
tool.
Check the log files of the packages managed
by Site Controller for more details.
5. Start the Site Controller Package.
410 Designing a Disaster Recovery Solution Using Site Aware Disaster Tolerant Architecture