Member shows alert while in STARTED state, all hosts are in ACTIVE state with no alerts
This symptom observed occurs as a follow on from the scenario "Member WAITING_FOR_FAILBACK, alert, corresponding host(s) is in INACTIVE state with alert". The output of the db2instance -list command shows a member with an alert while its state is STARTED. All hosts are in ACTIVE state with no alerts.
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 STARTED 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 NOMember 0 still has its
alert flagged as an indicator to the administrator to investigate the problem that occurred on hostB
that prevented the member from performing a
restart light.Note: The hostB problem is detailed in the parent topic Member
WAITING_FOR_FAILBACK, alert, corresponding host(s) is in INACTIVE state with alert.
For information about diagnosis, see the related link "Host (A) fails, restart light works on a host (C), but not the first host (B), failback N/A".