Member or host without any alert

The output for the db2instance -list command shows no alerts for any members or hosts, but other problems might have occurred.

Primary role moves between cluster caching facility hosts
The primary role is not on the same host as the last time the db2instance -list command was run, that is, the primary role has moved to another cluster caching facility host. This host change indicates a problem with the cluster caching facility at some point in the past that might need to be investigated.
Multiple member restarts on the home host
There are no apparent problems in the output of the db2instance -list command, and there are no alerts flagged in the ALERT column for either the members or the hosts. There might however exist a large or growing number of FODC directories, or space usage in the diagpath diagnostic dump directory ($INSTHOME/sqllib/db2dump/ $m by default) continues to grow at an abnormal pace (based on historical behavior).

Parent topic: Summary of instance status information from the db2instance -list command