Using Serviceguard Extension for RAC, 7th Edition, September 2008

• Recovering. A corrupt message was received on the serial line, and the line is in the process
of resynchronizing.
• Unknown. We cannot determine whether the serial line is up or down. This can happen
when the remote node is down.
Failover and Failback Policies
Packages can be configured with one of two values for the FAILOVER_POLICY parameter:
• CONFIGURED_NODE. The package fails over to the next node in the node list in the package
configuration file.
• MIN_PACKAGE_NODE. The package fails over to the node in the cluster with the fewest
running packages on it.
Packages can also be configured with one of two values for the FAILBACK_POLICY parameter:
• AUTOMATIC. With this setting, a package, following a failover, returns to its primary node
when the primary node becomes available again.
• MANUAL. With this setting, a package, following a failover, must be moved back to its original
node by a system administrator.
Failover and failback policies are displayed in the output of the cmviewcl -v command.
Examples of Cluster and Package States
The following sample output from the cmviewcl -v command shows status for the cluster in
the sample configuration.
Normal Running Status
Everything is running normally; both nodes in a two-node cluster are running, and each Oracle
RAC instance package is running as well. The only packages running are Oracle RAC instance
packages.
CLUSTER STATUS
example up
NODE STATUS STATE
ftsys9 up running
Network_Parameters:
INTERFACE STATUS PATH NAME
PRIMARY up 56/36.1 lan0
STANDBY up 60/6 lan1
PACKAGE STATUS STATE AUTO_RUN NODE
ops_pkg1 up running disabled ftsys9
Policy_Parameters:
POLICY_NAME CONFIGURED_VALUE
Start configured_node
Failback manual
Node_Switching_Parameters:
NODE_TYPE STATUS SWITCHING NAME
Primary up enabled ftsys9 (current)
NODE STATUS STATE
ftsys10 up running
Network_Parameters:
INTERFACE STATUS PATH NAME
PRIMARY up 28.1 lan0
STANDBY up 32.1 lan1
112 Maintenance and Troubleshooting