Greetings to all,
My Baan server and/or the baan nt manager has had to be re-started several times in the past month in order to clear the "runaway processes" which have been more common these days. The problems is always the same, how to relate the dbdriver PID, the ntbshell PID, and of course the Baan user. I was hoping that some of you might have some ideas on how to deal with these situations in an easier way without interrupting the most "undisturbable" users. I believe that this topic has been discussed previously as the problem is not knew, so even a link to that thread will help. Also ...are there any 3rd party developments known in the software market that might help?
with my best regards,
Paulo

Normally these are server process and there is no need to relate the same with user processes.

If you need to kill any user , please use bshcmd6.1 . In latest porting sets on unix there is alg6.1 utility also to send message / kill user processes. For NT also similar utilities should be available. Some NT user can correct the position for better.

I am not sure on Windows installations. We encountered this problem on our Unix installation.

Here is our case info -

Case 952330
Runaway ora8_maint6.2 process
Case description:
Periodically we are finding a ora8_maint6.2 that is using significant CPU resources for > 12 hrs, after which time we kill the process. What is this process and how do we address this.
Solution description:
VERSION(S):
B52_a
SITUATION IDENTIFIED IN:
ora8_maint6.2
ATTACHMENTS:
SITUATION DESCRIPTION:
Periodically we are finding a ora8_maint6.2 that is using significant CPU resources for > 12 hrs, after which time we kill the process.
SOLUTION DESCRIPTION:
Problem did not happen again, and it cannot be reproduced. Will reopen case if the problem shows up again.

so we tracked the whole problem down to find that during user creations, when we enter a wrong DBA password to create the users in different databases it causes that runaway processes.

Thank you for your replies, but let me add this ...... The reason of 99% of the runaway processes that I have in my system is perfectly identified. It happens when the user emits by mistake a long report that usually takes 6-8 hours to be prepared by baan. When the user realizes his mistake he easily clicks the "output to console" in the option dialog window. Although he aborts the process and is freed to start again ....this process keeps on running in the windows 2000 SQL platform consuming CPU%. Imagine my situation with over 100 simultaneous users , unable to be 100% certain of which process in the task manager is this one as there is no direct correspondence in between the dbdriver PID, the ntbshell PID, and of course the Baan user. I would not want to kill the Director's statistical report instead. This is why I will need to know exactly which process in the task manager belongs to each user, so I can "kill" the correct process.
Paulo

Paulo,

I can understand your problem. I am not SQL person, so cannot tell, how to kill database's session. We are using some Oracle queries/command to determine and kill the processes. The NT resource kit has a utility called 'kill'. You can integrate LICMON and BSHCMD for killing the user/process. I am giving here some already discussed topics/links:

1. http://www.baanboard.com/baanboard/showthread.php?s=&threadid=9541
2. http://www.sysinternals.com/ntw2k/f...e/pstools.shtml
3. http://www.baanboard.com/baanboard/showthread.php?s=&threadid=10350
4. http://www.baanboard.com/baanboard/showthread.php?s=&threadid=8604
5. http://www.baanboard.com/baanboard/showthread.php?s=&threadid=12257

Hope this helps.

-Suhas

bshcmd6.1 also kills bshell which are silent. So if the bshell has sumbitted heavy query to database driver , it will not get killed.

However there must be utilities in NT server process manager to CPU consumption (pid , parent id etc) . And with the parent id u must be able to trace the user.

However output to console is not the solution.I don't know about NT and the database driver u are working. Somebody experienced in this can shed some light on this.

I followed one of the above links and eventually found a tool for viewing processes, who started them and when. Then you can kill processes and process trees.


http://www.sysinternals.com/ntw2k/freeware/procexp.shtml

The tool is called Process Explorer, in case the link above doesn't work properly.

It doesn't clear the baan licence for that bshell though so you'll have to restart the licence service to do that.

EdHubbard,
I followed your link and downloaded the Process Explorer. It really works. It is exactly what I was looking for. It is curious how this small "exe" can give out such important information about the processes running on a machine.
Thank you very much,
Paulo :)