Recovering a cluster when one of the hosts in a DB2 pureScale cluster indicate "No" for Quorum

Technote (FAQ)


Question

How to recover a cluster, when one of the hosts in a DB2 pureScale cluster indicate "No" for Quorum?

Cause

In a DB2 pureScale cluster that works with TSA, one of the nodes (ie. host03 in the following example) indicates a "No" for Quorum. This is because the quorum vote was disabled on this node. Therefore, the tiebreaker would become "No" as well.


host01:/# lsrpnode -B -Q -P
Name OpState RSCTVersion Quorum Preferred Tiebreaker
host01 Online 3.1.2.5 Yes Yes Yes
host06 Online 3.1.2.5 Yes Yes Yes
host05 Online 3.1.2.5 Yes Yes Yes
host04 Online 3.1.2.5 Yes Yes Yes
host03 Online 3.1.2.5 No Yes No <<<<<<<<<<<<<


You can see "IsQuorumNode=0" in output of "lsrsrc -Ab IBM.PeerNode":

resource 6:
Name = "host03"
NodeList = {3}
RSCTVersion = "3.1.2.5"
ClassVersions = {}
CritRsrcProtMethod = 0
IsQuorumNode = 0 <<<<<<<<<<<<<<
IsPreferredGSGL = 1
NodeUUID = "00000000-0000-0000-0000-000000000000"
ActivePeerDomain = "db2domain_20121024211952"
NodeNameList = {"host03.sealedair.corp"}
OpState = 1
ConfigChanged = 0
CritRsrcActive = 1
OpUsabilityState = 1

Answer

To recover the cluster back to its health, run the following from any host in the cluster that is online:


$ export CT_MANAGEMENT_SCOPE=2
$ chrsrc -s "Name like '<node>'" IBM.PeerNode IsQuorumNode=1


Rate this page:

(0 users)Average rating

Document information


More support for:

DB2 for Linux, UNIX and Windows
High Availability - DB2 Failover

Software version:

9.8, 10.1, 10.5

Operating system(s):

AIX, Linux

Reference #:

1648982

Modified date:

2013-09-26

Translate my page

Machine Translation

Content navigation