Member is in ERROR state
Techniques to identify and diagnose a scenario when there is a member in ERROR state in the output of the db2instance -list command are outlined.
This is a sample output from the db2instance
-list command showing a three member, two cluster caching facility
environment:
ID TYPE STATE HOME_HOST CURRENT_HOST ALERT PARTITION_NUMBER LOGICAL_PORT NETNAME
-- ---- ----- --------- ------------ ----- ---------------- ------------ -------
0 MEMBER ERROR hostA hostA YES 0 0 hostA-ib0
1 MEMBER STARTED hostB hostB NO 0 0 hostB-ib0
2 MEMBER STARTED hostC hostC NO 0 0 hostC-ib0
128 CF PRIMARY hostD hostD NO - 0 hostD-ib0
129 CF PEER hostE hostE NO - 0 hostE-ib0
HOSTNAME STATE INSTANCE_STOPPED ALERT
-------- ----- ---------------- -----
hostA ACTIVE NO NO
hostB ACTIVE NO NO
hostC ACTIVE NO NO
hostD ACTIVE NO NO
hostE ACTIVE NO NOThis output shows that Db2® cluster services could not restart the failed member on its home host or on any other host in the cluster. As shown in the STATE column, member 0 is in the ERROR state. Manual intervention is required, as indicated by the alert flagged for member 0
For information about diagnosing this symptom, see "Host failed and restart light does not work on any host, failback did not happen."