We are running a v8 DB2 client FP2 on AIX 5.1. We notice the db2fmcd process running on the server and with our client we see a bunch of defunct processes owned by the db2 client id, however the parent process is the db2fmcd process.

From the documentation I found the db2fmcd is the following:

db2fmd The fault monitor daemon process that is started for every instance of DB2 that is monitored by the fault monitor. It is monitored by the coordinator daemon (db2fmcd), so if you kill the db2fmd process, db2fmcd will bring it back up. UNIX

Is the above process necessary? or how do I stop all the defunct processes from appearing?

thanks in advance

Mark

I caught this line while it was spawning another child process:

root 118078 33898 2 14:39:20 - 0:00 /home/symariq/sqllib/bin/db2fm -i symariq - m /home/symariq/sqllib/lib/libdb2gcf.a -S

if anyone has any thoughts on this, I would appreciate it.

root 33898 1 0 Dec 09 - 2:20 /usr/opt/db2_08_01/bin/db2fmcd

There are a bunch of these

symariq 34278 33898 0 0:00 <defunct>
symariq 34316 33898 0 0:00 <defunct>
symariq 35062 33898 0 0:00 <defunct>
symariq 35598 33898 0 0:00 <defunct>
symariq 36558 33898 0 0:00 <defunct>
symariq 37048 33898 1 0:00 <defunct>
symariq 38068 33898 1 0:00 <defunct>
symariq 39100 33898 0 0:00 <defunct>
symariq 39582 33898 1 0:00 <defunct>
symariq 39684 33898 1 0:00 <defunct>

Hi

I met this problem before.

It is bug of DB2 V8, APAR IY48423 --- DB2FMCD IS SPAWNING MANY DEFUNCT PROCESSES. Please see the ref http://www-3.ibm.com/cgi-bin/db2www/...aparno=IY48423

This bug is already fixed and included in DB2 V8 fixpak 4.

Therefore, go to install fixpak 4.

Good luck !!

Sophie