| inactive sessions [message #626905] |
Wed, 05 November 2014 02:09  |
 |
me:)
Messages: 3
Registered: November 2014
|
Junior Member |
|
|
|
we have an In house erp to cater to the needs to various departments. this erp is designed using oracle forms 10g. we are facing a serious problem on users opening more that 1 instance of the same form on different machines by doing so they are creating dabatase locks. we need a solution to terminate inactive user sessions, is there a way to do that in IAS or in forms ?
|
|
|
|
|
|
|
|
|
|
| Re: inactive sessions [message #626920 is a reply to message #626919] |
Wed, 05 November 2014 05:06  |
 |
mughals_king
Messages: 392
Registered: January 2012
Location: pakistan
|
Senior Member |
|
|
SQL Statements can be used to determine the blocking session and kill it.
select sid, serial#, username
from v$session where sid in
(select blocking_session from v$session);
Result:-
SID SERIAL# USERNAME
---------------------------------
144 8982 HR
Alter system kill session '144','8982' immediate;
Hope it wil lhelp you
Regards
Mughal
[Updated on: Wed, 05 November 2014 05:07] Report message to a moderator |
|
|
|
| Re: inactive sessions [message #626953 is a reply to message #626920] |
Wed, 05 November 2014 09:11 |
 |
CraigB
Messages: 386
Registered: August 2014
Location: Utah, USA
|
Senior Member |
|
|
Of course, you have to be logged in with a user that has the ALTER SYSTEM priv granted. Plus, this is an extremely dangerous thing to do. I would recommend you work more towards preventing the "inactive sessions" versus just killing them.
For starters, you could prevent the opening of multiple sessions or you could change the Locking Method property of your Forms datablocks so they only lock a record during commit processing instead of immediately upon a change in Forms.
Craig...
|
|
|
|
] 
Blog
Search
Help
Members
Register
Login
Home
