Benutzer-Werkzeuge

Webseiten-Werkzeuge


dba:kill_disconnect_session

Unterschiede

Hier werden die Unterschiede zwischen zwei Versionen angezeigt.

Link zu dieser Vergleichsansicht

Beide Seiten der vorigen Revision Vorhergehende Überarbeitung
dba:kill_disconnect_session [2015/01/07 11:15]
gpipperr [Eine gekillete Session in der DB wiederfinden]
dba:kill_disconnect_session [2015/01/16 16:23] (aktuell)
gpipperr [Eine gekillete Session in der DB wiederfinden]
Zeile 191: Zeile 191:
 </code> </code>
  
 +
 +=== SNIPED Sessions ====
 +..
 +
 +
 +Sniped - the session has passed the idle_time limit defined in user profile. The session will remain snipped until the client communicates with the db again, when it will get "ORA-02396: exceeded maximum idle time, please connect again" and the session is removed from v$session.
 +
 +...
 +
 +When IDLE_TIME is set in the users' profiles or the default profile. This will kill the sessions in the database (status in v$session now becomes SNIPED) and they will eventually disconnect. It does not always clean up the Unix session (LOCAL=NO sessions). At this time all oracle resources are released but the shadow processes remains and OS resources are not released. This shadow process is still counted towards the parameters of init.ora.
 +This process is killed and entry from v$session is released only when user again tries to do something. Another way of forcing disconnect (if your users come in via SQL*Net) is to put the file sqlnet.ora on every client machine and include the parameter "SQLNET.EXPIRE_TIME" in it to force the close of the SQL*Net session.
 +
 +...
 +
 +see https://community.oracle.com/thread/531765 
    
 <note important>In Arbeit</note> <note important>In Arbeit</note>
"Autor: Gunther Pipperr"
dba/kill_disconnect_session.txt · Zuletzt geändert: 2015/01/16 16:23 von gpipperr