Active session
Srini Sr, January 05, 2010 - 5:05 pm UTC
Hi Tom,
For an ACTIVE session, isn't an abnormal termination dangerous? (based on your example, when a lock is held)
The value of the parameter EXPIRE_TIME is set to 6 for our database. In this case, it will investigate and kill only INACTIVE sessions, is this correct?
In my case, is there a possible way to detect this lock? (as the session was in ACTIVE status)
Thanks as Always.
January 06, 2010 - 7:48 am UTC
define dangerous.
if the client HADN'T gone away, you would be in the same exact situation? Now what???
If you want to limit the amount of time any single session may remain active, use a resource profile (cpu per call, time limits, whatever).
Resource profiles
Srini, January 06, 2010 - 6:02 pm UTC
Hi Tom,
If the client hadn't gone away, then it would be possible to break the operation from the client PC.
In this case, the session is active at the database, and there is no hint of the connection at the client PC.
I will read more on the resource profiles. The problem in our case is, the database is accessed by a single user ID, both by the application (three tier) and users (client tools).
Thanks again.
January 11, 2010 - 7:59 am UTC
... and there is no hint of
the connection at the client PC. ...
and we have no idea that is the case, tcp/ip doesn't do it for us.
...
When EXIT from sqlplus, how long it take to clean up?
Anand, March 25, 2010 - 8:12 am UTC
When issuing EXIT command from sqlplus, how much time Oracle will take to clean up the connection?
Need to understand because developer needs to open 3 sessions in one process. And that process will be called 20 /30 times every 30 minutes.
Thank you. Your responses are very helpful.
Anand
March 26, 2010 - 1:41 pm UTC
it is immediate, when you exit, sqplus will pretty much a) commit, b) terminate the connection (note in 11gr2 sqlplus might rollback instead of commit, you choose that via a setting in sqlplus)
if a developer is writing an application that uses sqlplus as a "subroutine", that developer has almost certainly done something wrong, I cannot imagine "forking" sqlplus like that as part of my day to day application execution - how truly 'fragile' that would be - pretty much zero ability to handle and deal with errors.
Jaroslav Tachovsky, March 14, 2013 - 4:02 am UTC
Hello Tom,
on you first reply (link to documentation) is recommendattion to set SQLNET.EXPIRE_TIME in [ORACLE_HOME]/network/admin/sqlnet.ora file. My question is - should it be set on client or server side ?
March 14, 2013 - 8:27 am UTC
<quote>
This parameter is primarily intended for the database server, which typically handles multiple connections at any one time.
</quote>
server side.