karlovac
30th October 2002, 09:53
What to clean (on Bisam base) when system is disconnecting BW user or when system freezes on wrong defined query?
I know, the first step is to remove database locks for user,
but what else could be wrong?
(Bisam, as I know, doesnt have transaction contol ... or?)
Thanks
evertsen
30th October 2002, 17:06
Application Locks and licenses. Remove the app locks with the session of the same name (ttstpdellocks?) and then look on the UNIX side for any processes left by the offending user Not sure about AIX but in HP-UX it would be: ps -ef | grep username. Using the process number (pid) attached to bshell6.1 run # kill -15 pid
Some people run kill -9 but -15 will release the Baan license as well (usually). If you have to use -9, the only way to get the license back is restarting licd6.1
karlovac
31st October 2002, 07:13
Thanks, Evertsen,
one more question is what is happening on the Bisam DB side,
there are some open tables (if user is disconnected in the middle of transaction)?
Or?
Thanks
evertsen
31st October 2002, 07:28
I've only used Informix and Oracle and not had a problem with open tables. I don't know much about Bisam unfortunately.
victor_cleto
31st October 2002, 20:27
There are several discussions ongoing about terminating bshells (use ps -fu <user> instead, use bshcmd6.1 first to try to terminate cleanly the user bshell, etc.), search for them.
Evertseen was correct, session to be called is ttstpdellocks.