hi all,
I am encountering a weird issue here, i have configured db2fm as below:

root@chialeep:/opt/ibm/db2/V9.7/bin# grep db2 /etc/inittab
fmc:2345:respawn:/opt/ibm/db2/V9.7/bin/db2fmcd #DB2 Fault Monitor Coordinator

started db2fm with below command:
./db2fm -i db2inst1 -m /home/db2inst1/sqllib/lib/libdb2gcf.so.1 -U -u

however, when i issue db2stop via user: db2inst1 (instance owner), the fault monitor service will not able to startup by itself:

root@chialeep:/opt/ibm/db2/V9.7/bin# grep db2 /etc/inittab
fmc:2345:respawn:/opt/ibm/db2/V9.7/bin/db2fmcd #DB2 Fault Monitor Coordinator

Any idea?

I tried this, and it always shows down:
root@chialeep:/opt/ibm/db2/V9.7/bin# ./db2fmcu
FMC: down

"With Fault Monitor facility, if the DB2® Universal Database™ (DB2 UDB) instance exits prematurely, the fault monitor will restart it."

db2stop != prematurely

Check this technote for info on how to configure and test it:
https://www-304.ibm.com/support/docv...id=swg21209001

hi BELLO4KA,
Thanks for your replied. I have follow the link given by you to setup the fault monitor.

root@chialeep:/opt/ibm/db2/V9.7/bin# cat /etc/inittab | grep db2fmcd
fmc:2345:respawn:/opt/ibm/db2/V9.7/bin/db2fmcd #DB2 Fault Monitor Coordinator
root@chialeep:/opt/ibm/db2/V9.7/bin# ps -ef | grep db2fm
root 1618 1462 0 09:00 pts/0 00:00:00 grep --color=auto db2fm
root@chialeep:/opt/ibm/db2/V9.7/bin# ./db2fm -i db2inst1 -U
root@chialeep:/opt/ibm/db2/V9.7/bin# ./db2fm -i db2inst1 -u
oot@chialeep:/opt/ibm/db2/V9.7/bin# ./db2fm -i db2inst1 -f on
root@chialeep:/opt/ibm/db2/V9.7/bin# ./db2fm -i db2inst1 -a on
root@chialeep:/opt/ibm/db2/V9.7/bin# ./db2fm -i db2inst1 -f on
root@chialeep:/opt/ibm/db2/V9.7/bin# ./db2fm -i db2inst1 -a on


But db2fmcu still showing:
root@chialeep:/opt/ibm/db2/V9.7/bin# ./db2fmcu
FMC: down

Any idea why?

Did you reboot the server? What's the output from step #11?

restarted the server and try to tail log:

root@chialeep:/home/db2inst1# cd /home/db2inst1 && tail -f ./sqllib/db2dump/db2diag.log
FUNCTION: DB2 Common, Fault Monitor Facility, db2fm, probe:70
MESSAGE : ECF=0x900003A4=-1879047260=ECF_FM_POSSIBLE_TIME_HOLE_BEFORE_SET_RE AD_LOCK
Possible timing hole between releasing write lock and getting read lock

2011-04-23-09.28.33.592193+480 I82022G347 LEVEL: Warning
PID : 2752 TID : 1629152 PROC : db2fm
INSTANCE: db2inst1 NODE : 000
FUNCTION: DB2 Common, Fault Monitor Facility, fmNotifyDaemon, probe:40
MESSAGE : ECF=0x90000369=-1879047319=ECF_FM_NO_DAEMON_RUNNING
There is no db2fmd daemon running


Here is my fault monitor registry file content:
root@chialeep:/home/db2inst1# cd /home/db2inst1 && tail -f ./sqllib/db2dump/db2diag.log
FUNCTION: DB2 Common, Fault Monitor Facility, db2fm, probe:70
MESSAGE : ECF=0x900003A4=-1879047260=ECF_FM_POSSIBLE_TIME_HOLE_BEFORE_SET_RE AD_LOCK
Possible timing hole between releasing write lock and getting read lock

2011-04-23-09.28.33.592193+480 I82022G347 LEVEL: Warning
PID : 2752 TID : 1629152 PROC : db2fm
INSTANCE: db2inst1 NODE : 000
FUNCTION: DB2 Common, Fault Monitor Facility, fmNotifyDaemon, probe:40
MESSAGE : ECF=0x90000369=-1879047319=ECF_FM_NO_DAEMON_RUNNING
There is no db2fmd daemon running

What's the output from step #11?

step11 output:

chialeep@chialeep:~$ sudo su - db2inst1
[sudo] password for chialeep:
$ db2fm -s -S
Gcf module 'fault monitor' is INSTALLED PROPERLY but NOT ALIVE
Gcf module '/opt/ibm/db2/V9.7/lib32/libdb2gcf.so' is INSTALLED PROPERLY but NOT ALIVE

Something is not right. I'd suggest to redo it from the beginning, including db2fmcu -d, and save the output from each step. If this still doesn't work, consider opening a PMR.