We have been running DB2 with Solaris for about 4 years. Like you, we see a large number of db2sysc processes after instance shutdown. >From past discussions with IBM they have said something similar to what you are suggesting. These are processes that were not cleanly removed from DB2.
On rare occasions I had issues bringing down the instance where all the nodes do not come out clean. Sometimes the shutdown would time out. When this occurs you will get a message indicating the port is busy for one of you nodes (when you try to start the instance). When this has occurs I have cleaned out the db2sysc processes and then been able to restart the instance without issue. The same thing can occur with the administrative server if the shutdown is not smooth.
Hope this is helpful,
Roy
Daniel Scheibli wrote:
Hi Jerry,there is a note from IBM (search for ps solaris db2sysc getting the result
http://www-4.ibm.com/cgi-bin/db2www/data/db2/udb/winos2unix/support/document.d2w/report?last_page=list.d2w&fn=1008339) in which they tell us to use an
other ps command. With this you see the real names of the processes.Killing this processes is realy the absolutely last choise.
Hope it helps
Daniel
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 db2syscThis 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]--
Daniel Scheibli
Karlsruhe, GermanyMachen Sie Ihr Hobby zu Geld bei unserem Partner 1&1!
http://profiseller.de/info/index.php3?ac=OM.PS.PS003K00596T0409a--
GMX - Die Kommunikationsplattform im Internet.
http://www.gmx.net=====
To unsubscribe, send 'unsubscribe' to [EMAIL PROTECTED]
For other info (and scripts), see http://people.mn.mediaone.net/scottrmcleod
