DB2 10.5 for Linux, UNIX, and Windows

db2fmcu - DB2 fault monitor controller command

DB2® Fault Monitor is the DB2 database facility that automatically starts an instance after a crash. It can also auto restart an instance on machine reboot. You can configure the DB2 fault monitor on Linux and UNIX operating systems using the DB2 fault monitor controller command. The command must be run as root because it accesses the system's inittab file.

Authorization

Root user authority

Required connection

None

Command syntax


>>-db2fmcu--+------------------------+--+--------------+-------><
            +- -u-- -p--db2fmcd_path-+  '- -f--inittab-'   
            '- -d--------------------'

Command parameters

-u -p db2fmcd_path: This option re-configures the inittab file to include the fault monitor controller (FMC) at system startup, where db2fmcd_path is the complete path to the FMC daemon (db2fmcd) object, for example /opt/IBM/db2/bin/db2fmcd.; As of Red Hat Enterprise Linux (RHEL) 6, the /etc/inittab file has been deprecated. Specifying this option creates or replaces the db2fmcd.conf file under the /etc/init directory.; As of Solaris 10, the /etc/inittab file has been deprecated. Specifying this option creates and enables the db2fm SMF service.
-d: This option changes the inittab file configuration to prevent the FMC from being run at system startup.; As of RHEL 6, the /etc/inittab file has been deprecated. Specifying this option removes the db2fmcd.conf file.; As of Solaris 10, the /etc/inittab file has been deprecated. Specifying this option disables the db2fm SMF service.
-f inittab: This option specifies a path to the inittab file.

Example

To start the fault monitor controller at system startup by re-configuring the inittab file, run the following command:

db2fmcu -u -p /opt/IBM/db2/bin/db2fmcd

To prevent the fault monitor controller from being launched at system startup, run the following command:

db2fmcu -d

Usage notes

If you changed /etc/inittab manually, you need to send SIGHUP to process 1 to ask it to re-scan /etc/inittab right away. Otherwise, it can take some time before the next re-scan happens. If you updated /etc/inittab via db2fmcu, you do not need to send the signal as it is already done by the db2fmcu command.
In the Solaris Operating System, the processes listed in the /etc/inittab file inherit the default system project settings. Ensure that the kernel parameters for the project are set high enough to accommodate the DB2 processes or start the db2fmcd process under a different project that has the appropriate kernel settings. To start the db2fmcd process under a different project, edit the fmc entry in the /etc/inittab file to use newtask. For example, add /usr/bin/newtask -p in front of the db2fmcd path. For more information about setting kernel parameters, see the db2osconf command.