markom
7th April 2003, 20:19
hello!
I have problems with oracle
sometime users in baan get error 1018 because max number of session exceeded in oracle. When I look in DBA studio I see a lot of sessions but 80% of sessions have status inactive.
What can I do that this session want be there.
I now I can put bigger parameter in init.ora session = xxx but i would like to prevent that inactive sesssion want be there.
We have Oracle 8.1.7.3/NT/ BaanIV c4
Thanks for all help
Lp Mare
suhas-mahajan
8th April 2003, 08:13
Dear Markom,
Please describe your question -
"What can I do that this session want be there"
-Suhas
markom
8th April 2003, 08:51
you can see in oracle witch sessions are active or inactive. If you have session parameter = 100 in init.ora and you have number of active and inactive sessions 100 you get that message. what can I do that inactive session wouldn't stay inside.
suhas-mahajan
8th April 2003, 10:19
Dear,
It is advisible, be alert during doing this type of work, if possible avoid it, because it may pull you into data corruption.
But if you are sure, you can not avoid and the sessions are "inactive and non administrative", you can try -
The benefit of killing "inactive and non administrative" session is -session's transaction is rolled back and resources (such as locks and memory areas) held by the session are immediately released and available to other sessions.
The following query identifies all sessions for the perticular user :
SELECT sid, serial#
FROM v$session
WHERE username = 'USERNAME';
This will gives you SID and SERIAL no. on server manager give -
SVRMGR> ALTER SYSTEM KILL SESSION 'SID,SERIAL no';
This will kill your specified session.
Try this, If you require, I will give a good script for identifying.
-Suhas
Djie-En
8th April 2003, 10:54
Originally posted by markom
you can see in oracle witch sessions are active or inactive. If you have session parameter = 100 in init.ora and you have number of active and inactive sessions 100 you get that message. what can I do that inactive session wouldn't stay inside.
Hi,
Pls. change the figure of session-parameter into for example 105 or higher.
Don't kill the inactive processes by DBA-studio.
Because if you login into Baan there is already 1 process which is inactiv.
When the user calls a maintain session, you will see in DBA-studio already three inactiv processes.
GN
markom
8th April 2003, 11:38
Thanks for your help. You can send me script on my e-mail
marko.markic@elan.si
Thanks again
Lp Mare
suhas-mahajan
8th April 2003, 13:49
Dear,
Please find attached herewith user.sql.txt file, rename it to user.sql and run from SQL prompt.
Bye.
-Suhas
victor_cleto
8th April 2003, 17:12
If oracle sessions are inactive then that is because the bshell is also inactive... since the oracle processes are created from the bshell, I would try to control first from Baan side before going to Oracle (timeouts, make sure your users logoff at end of day, kill inactive bshells, etc...)
dave_23
8th April 2003, 21:07
Also, if they are truly idle you can set bdb_max_session_schedule
to a lower value.
check with your driver technical manual!
Dave