Using the DB2 fault monitor
The main role of DB2 fault monitor is to keep the instances running all the time. In the case where an instance fails because of an unpredicted event, such as a software bug or an accidental close, the fault monitor will try to restart it.
Getting ready
In the following recipe, we will cover the parameters that control the fault monitor and how it works.
How to do it...
Every instance has a fault monitor registry file located in <instance user home>/sqllib/. This file has the format fm.machinename.reg and contains the parameters that control the behavior of the fault monitor. Usually, this file is updated using the corresponding switches of the db2fm command. For example, our fault monitor registry, for db2inst1 on nodedb21, has the following parameters or keywords:
[db2inst1@nodedb21 sqllib] more fm.nodedb21.reg FM_ON = no # default FM_ACTIVE = yes # default START_TIMEOUT = 600 # default STOP_TIMEOUT = 600 # default STATUS_TIMEOUT = 20 # default STATUS_INTERVAL...
