DB2 v8 Client and db2fmcd creating a bunch of defunct processes

Mark Maziarczyk

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

I caught the following line on the server when I did a ps -ef |grep PID:

symariq 40862 33898 1 14:42:08 - 0:00
/home/symariq/sqllib/bin/db2fm -i symariq -m
/home/symariq/sqllib/lib/libdb2gcf.a -S

And there are a bunch of process below that are on the server, can someone
tell me why these processes are being spawned and if the db2fmcd process
needs to be running on the server?

thanks

Mark



root 33898 1 0 Dec 09 - 2:20
/usr/opt/db2_08_01/bin/db2fmcd
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>

symariq 41074 33898 0 0:00 <defunct>
symariq 41262 33898 0 0:00 <defunct>
symariq 41506 33898 2 0:00 <defunct>
symariq 43872 33898 0 0:00 <defunct>
symariq 44122 33898 0 0:00 <defunct>
symariq 44480 33898 0 0:00 <defunct>
symariq 45000 33898 0 0:00 <defunct>
symariq 45250 33898 0 0:00 <defunct>
symariq 45582 33898 0 0:00 <defunct>
symariq 46010 33898 1 0:00 <defunct>
symariq 46158 33898 0 0:00 <defunct>
symariq 46534 33898 1 0:00 <defunct>
symariq 47558 33898 1 0:00 <defunct>
symariq 47750 33898 0 0:00 <defunct>
symariq 48480 33898 0 0:00 <defunct>
symariq 48898 33898 0 0:00 <defunct>

---------------------------------------------------------------------------------
Welcome to the IDUG DB2-L list. To unsubscribe, go to the archives and home page at http://www.idugdb2-l.org/archives/db2-l.html. From that page select "Join or Leave the list". If you will be out of the office, send the SET DB2-L NO MAIL command to [login to unmask email] The IDUG List Admins can be reached at [login to unmask email] Find out the latest on IDUG conferences at http://conferences.idug.org/index.cfm

Philip Nelson

Re: DB2 v8 Client and db2fmcd creating a bunch of defunct processes
(in response to Mark Maziarczyk)
Mark,

Didn't see a reply to this, so I'll do my best.

The db2fmcd (Fault Monitor Co-ordinator Daemon) definitely does need to
be running on the server. In Version 8 this sits at the very lowest
level and is responsible to start the instances and restart them if they
come down for any unexpected reason. You'll find that this is now what
gets started in inittab (in V7 the instances themselves were started in
inittab). To have an instance started by db2fmcd at boot time you need
to set environment variable DB2AUTOSTART=YES.

As far as the list of defunct processes is concerned I can't really help
you without more information about them. Has an instance been failing ?
Or are these failed "client" processes ?

HTH

Phil

On Mon, 2003-12-15 at 19:50, [login to unmask email] wrote:
> We are running a DB2 v8 Client FP2 on AIX 5.1. We notice the db2fmcd
> process running on that server and with our client we see a bunch of of
> defunct processes owned by the db2 client user, however the parent process
> is the db2fmcd process.
>
> I caught the following line on the server when I did a ps -ef |grep PID:
>
> symariq 40862 33898 1 14:42:08 - 0:00
> /home/symariq/sqllib/bin/db2fm -i symariq -m
> /home/symariq/sqllib/lib/libdb2gcf.a -S
>
> And there are a bunch of process below that are on the server, can someone
> tell me why these processes are being spawned and if the db2fmcd process
> needs to be running on the server?
>
> thanks
>
> Mark
>
>
>
> root 33898 1 0 Dec 09 - 2:20
> /usr/opt/db2_08_01/bin/db2fmcd
> 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>
>
> symariq 41074 33898 0 0:00 <defunct>
> symariq 41262 33898 0 0:00 <defunct>
> symariq 41506 33898 2 0:00 <defunct>
> symariq 43872 33898 0 0:00 <defunct>
> symariq 44122 33898 0 0:00 <defunct>
> symariq 44480 33898 0 0:00 <defunct>
> symariq 45000 33898 0 0:00 <defunct>
> symariq 45250 33898 0 0:00 <defunct>
> symariq 45582 33898 0 0:00 <defunct>
> symariq 46010 33898 1 0:00 <defunct>
> symariq 46158 33898 0 0:00 <defunct>
> symariq 46534 33898 1 0:00 <defunct>
> symariq 47558 33898 1 0:00 <defunct>
> symariq 47750 33898 0 0:00 <defunct>
> symariq 48480 33898 0 0:00 <defunct>
> symariq 48898 33898 0 0:00 <defunct>
>
> ---------------------------------------------------------------------------------
> Welcome to the IDUG DB2-L list. To unsubscribe, go to the archives and home page at http://www.idugdb2-l.org/archives/db2-l.html. From that page select "Join or Leave the list". If you will be out of the office, send the SET DB2-L NO MAIL command to [login to unmask email] The IDUG List Admins can be reached at [login to unmask email] Find out the latest on IDUG conferences at http://conferences.idug.org/index.cfm
>

---------------------------------------------------------------------------------
Welcome to the IDUG DB2-L list. To unsubscribe, go to the archives and home page at http://www.idugdb2-l.org/archives/db2-l.html. From that page select "Join or Leave the list". If you will be out of the office, send the SET DB2-L NO MAIL command to [login to unmask email] The IDUG List Admins can be reached at [login to unmask email] Find out the latest on IDUG conferences at http://conferences.idug.org/index.cfm