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).

This is a sample output from the db2instance -list command showing a three member, two cluster caching facility environment:
--        ----             -----           ---------    ------------  -----  ----------------  ------------  -------
0         MEMBER           STARTED         hostA        hostA         NO                    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
--------       -----      ---------------- -----
hostA          ACTIVE     NO               NO
hostB          ACTIVE     NO               NO
hostC          ACTIVE     NO               NO
hostD          ACTIVE     NO               NO
hostE          ACTIVE     NO               NO
This symptom can be caused by a member restart on the home host. Ongoing or a repetition of problems causing multiple member restarts on the home host can lead to the growing space usage of the diagpath diagnostic dump directory ($INSTHOME/sqllib/db2dump/ $m by default)
  • Check the instance_owner.nfy log for information about when the failure occurred.
  • Look for entries in this member db2diag log file around this timestamp for more details on why the failure occurred.
    Note: Check for error messages related to db2rstar in the db2diag log file.
  • Look for FODC directories in the diagpath location (or sqllib/db2dump/ $m directory by default). If there are FODC directories see the related link to "First occurrence data capture information" for instructions on how to proceed.
  • If there are no FODC directories and the cause of the error is still unknown, consult the system error log for the affected host.