Last updated on AUGUST 08, 2017
Applies to:Solaris Cluster - Version 3.0 to 4.3 [Release 3.0 to 4.3]
Solaris Cluster Geographic Edition - Version 3.0x to 4.3 [Release 3.0 to 4.3]
Oracle Solaris on SPARC (32-bit)
Oracle Solaris on SPARC (64-bit)
Oracle Solaris on x86-64 (64-bit)
This document describes how to recover from a quorum amnesia condition in Oracle Solaris Cluster. This procedure should be used if the cluster suffers from amnesia due to hardware failure, as in the example below. Misuse of this document may affect the integrity of the Cluster Configuration Repository (CCR) which contains the cluster configuration data. It is advisable to contact Oracle Support Services if this document is to be used in a production environment. Although the example below describes a two node cluster it should work for any possible topology and configuration.
Typical Amnesia Scenario:
In the above case, node node-1 cannot start the cluster due to the amnesia protection of Oracle Solaris Cluster. Since node node-1 was not a member of the cluster when it was shut down (when node-2 crashed) there is a possibility it has an outdated CCR and should not be allowed to automatically start up the cluster on its own.
The general rule is that a node can only start the cluster if it was part of the cluster when the cluster was last shut down. In a multi node cluster it is possible for more than one node to become "the last" leaving the cluster.
Sign In with your My Oracle Support account
Don't have a My Oracle Support account? Click to get started
Million Knowledge Articles and hundreds of Community platforms