Solaris Cluster 3.x Resource/Application Failed to 'fail over' Resolution Path
(Doc ID 1021504.1)
Last updated on AUGUST 12, 2020
Applies to:Solaris Cluster Geographic Edition - Version 3.1x to 3.3 U2 [Release 3.1 to 3.3]
Solaris Cluster - Version 3.0 to 3.3 U2 [Release 3.0 to 3.3]
Oracle Solaris on SPARC (64-bit)
Oracle Solaris on SPARC (32-bit)
Oracle Solaris on x86-64 (64-bit)
Oracle Solaris on x86 (32-bit)
When a Solaris Cluster resource failed to fail over, there could be many underlying reasons. This document walks you through the most common causes.
Table of content:
1) Verify what version of Solaris Cluster 3.2 or higher, Sun Cluster 3.0 or 3.1 is running.
2) Verify if resource group is set to suspended
3) Verify that start method for one or more resources failed
4) Verify that application failed to stop on the node where it was previously running
5) Verify that Pingpong_interval was not reached
6) Verify Failover_mode setting is set to SOFT or HARD
7) Verify that dependencies for a resource to be started were met
8) Verify that the resource came online first but monitor failed
9) Verify that node is on Nodelist property
10) Verify that resource failed to failover because of validation failure
11) Verify that the cluster node where you expected the resource to fail over did not have a preexisting condition that would have prevented a failover attempt
12) Turn on debugging for resource type
13) Contact Oracle
To view full details, sign in with your My Oracle Support account.
Don't have a My Oracle Support account? Click to get started!