Db2 fault monitor facilities for Linux® and UNIX
Available on UNIX based systems only, Db2 fault monitor facilities keep IBM® Db2 server databases up and running by monitoring Db2 database manager instances, and restarting any instance that exits prematurely.
The fault monitor coordinator (FMC) is the process of the fault monitor facility that is started
at the UNIX boot sequence. Theinit daemon
starts the FMC and will restart it if it terminates abnormally. The FMC starts one fault monitor for
each Db2
instance. Each fault monitor runs as a daemon process and has the same user privileges as the
Db2 instance.
Once a fault monitor is started, it will be monitored to make sure it does not exit prematurely. If a fault monitor fails, it will be restarted by the FMC. Each fault monitor will, in turn, be responsible for monitoring one Db2 instance. If the Db2 instance exits prematurely, the fault monitor will restart it. The fault monitor will only become inactive if the db2stop command is issued. If a Db2 instance is shut down in any other way, the fault monitor will start it up again.
Db2 fault monitor restrictions
If you are using a high availability clustering product such as IBM Tivoli® System Automation for Multiplatforms (SA MP) or IBM PowerHA® SystemMirror® for AIX®, the fault monitor facility must be turned off since the instance startup and shut down is controlled by the clustering product.
Differences between the Db2 fault monitor and the Db2 health monitor
The health monitor and the fault monitor are tools that work on a single database instance. The health monitor uses health indicators to evaluate the health of specific aspects of database manager performance or database performance. A health indicator measures the health of some aspect of a specific class of database objects, such as a table space. Health indicators can be evaluated against specific criteria to determine the health of that class of database object. In addition, health indicators can generate alerts to notify you when an indicator exceeds a threshold or indicates a database object is in a non-normal state.
By comparison, the fault monitor is solely responsible for keeping the instance it is monitoring up and running. If the Db2 instance it is monitoring terminates unexpectedly, the fault monitor restarts the instance. The fault monitor is not available on Windows.