Hi List,
We have DB2 v 6.1 on Solaris 5.6. I notice when I execute 'ps -ef | grep dbatu01' that I get the following list of processes running under the instance owner:
dbatu01 26791 1 0 May 28 ? 0:01 db2sysc
dbatu01 26785 1 0 May 28 ? 0:00 db2sysc
dbatu01 26893 1 0 May 28 ? 0:01 db2sysc
dbatu01 26779 1 0 May 28 ? 0:01 db2sysc
dbatu01 9931 22573 0 16:44:32 pts/2 0:00 grep dbatu01
dbatu01 26894 1 0 May 28 ? 0:00 db2sysc
dbatu01 26897 1 0 May 28 ? 0:00 db2sysc
dbatu01 26783 1 0 May 28 ? 0:01 db2sysc
dbatu01 26895 1 0 May 28 ? 0:00 db2sysc
dbatu01 26896 1 0 May 28 ? 0:00 db2sysc
dbatu01 26778 1 0 May 28 ? 0:02 db2sysc
dbatu01 22573 22571 0 12:30:24 pts/2 0:01 -csh
dbatu01 23601 1 0 12:46:46 pts/2 0:01 /opt/IBMdb2/user/dbatu01/sqllib/bin/db2bp 22573 5
dbatu01 26787 1 0 May 28 ? 0:00 db2sysc
This is with the dbm stopped.
My understanding is that db2sysc is a system controller daemon, doing various system and maintenance tasks. However, I can't understand why these processes are still active after DB2 has been stopped. I suspect that they are orphans, or 'zombies', whose parent task had died. Can anyone confirm this? Can anyone shed light on how this situation occurs?
Is there any sort of control parameter to tidy these up when the dbm is stopped, or to limit the number of db2sysc processes that can be started concurrently?
Is it safe to 'kill -9' these processes when the dbm is inactive?
Is there any way of identifying which task each of these db2sysc processes was intended to perform?
Thanks in anticipation for your help.
Regards,
Jerry Long
MBL DBA
[EMAIL PROTECTED]
