Comments on: The Difference Bewteen Kill Session and Disconnect Session in Oracle Database http://www.dbuggr.com/smallwei/main-difference-bewteen-kill-session-disconnect-session-oracle-databa/ Share Knowledge & Be Rewarded Sun, 14 Mar 2010 16:03:05 -0400 http://wordpress.org/?v=2.8.6 hourly 1 By: smallwei http://www.dbuggr.com/smallwei/main-difference-bewteen-kill-session-disconnect-session-oracle-databa/comment-page-1/#comment-366 smallwei Mon, 23 Nov 2009 17:28:13 +0000 http://www.dbuggr.com/smallwei/main-difference-bewteen-kill-session-disconnect-session-oracle-databa/#comment-366 <strong>Kills a session:</strong> Releases locks and other resources but keeps the session object so that the application gets a graceful "ora-28, you have been KILLED, goodbye" message from the server. the session is dead, killed, resources released. However the session remains -- this is so the client process which is still connected can report gracefully to the end user "your session was killed, goodbye". What happened was that user had a session opened (maybe a sqlplus session). It was just sitting there -- and would continue to sit there until it went to the database -- then the session would actually "disappear" -- after the client got the message. <strong>Disconnect session:</strong> Disconnect is primarily for TAF (failing over), so you can fail a connection over from one instance to another. you can have it do that after the transaction ends so as to not lose work. Disconnecting zaps the dedicated server, and the client does not get a nice message. Kills a session:
Releases locks and other resources but keeps the session object so that the application gets a graceful “ora-28, you have been KILLED, goodbye” message from the server.

the session is dead, killed, resources released. However the session remains — this is so the client process which is still connected can report gracefully to the end user “your session was killed, goodbye”. What happened was that user had a session opened (maybe a sqlplus session). It was just sitting there — and would continue to sit there until it went to the database — then the session would actually “disappear” — after the client got the message.

Disconnect session:
Disconnect is primarily for TAF (failing over), so you can fail a connection over from one
instance to another. you can have it do that after the transaction ends so as to not lose work.
Disconnecting zaps the dedicated server, and the client does not get a nice message.

]]>