Comments on: What happens when a session is killed?

By: bob

bob — Mon, 06 Feb 2006 18:00:07 +0000

In some circumstances you don’t want your killed sessions to hang around there until restart. For example in our application we had a restriction that a user can only open 2 sessions to the database and these zombies prevented a user from logging on. If you want to make sure the session you are killing actually keels over instantly do not issue ‘kill session’. Instead get PID of the process (on UNIX) from v$process.spid (join to v$session to get your session) and kill the process first using OS kill command. Then issue ‘kill session’.

Vadim Bobrov

By: pmoore

pmoore — Mon, 23 Jan 2006 16:01:19 +0000

One thing to watch for – the killed session receives a “Your session has been killed” error. It is possible to trap that error in PL/SQL (although, obviously, not to do anything particularly meaningful with it…)

Badly-written PL/SQL, which uses

exception when others =>

can therefore end up in an infinite loop when killed.

By: troach

troach — Wed, 18 Jan 2006 19:08:52 +0000

Nice script.

Here is a script I use to log users off the database. I could combine the two and it might be a nicer script! :)

ALTER SYSTEM KILL SESSION
(SELECT s.sid,
s.serial#
FROM v$session s
WHERE UPPER(s.username) = UPPER(’SYSTEM’)
/

create or replace procedure set_udump( p_udump in varchar2 )
2 as
3 begin
4 execute immediate ‘alter system set user_dump_dest = ”’ || p_udump
|| ”’ scope=memory’;
5 end;
6 /

GRANT ALTER SYSTEM TO someuser;
GRANT SELECT ON v$_session to someone;

CREATE OR REPLACE PROCEDURE drop_user
(p_drop_user IN VARCHAR2)

v1_sid number;
v1_serial number;

CURSOR C1
IS
SELECT s.sid,
s.serial#
FROM v$session s
WHERE UPPER(s.username) = UPPER(p_drop_user);

BEGIN

OPEN C1;

LOOP

FETCH C1 INTO v1_sid, v1_serial;

EXIT WHEN C1%NOTFOUND;

EXECUTE IMMEDIATE ‘ALTER SYSTEM KILL SESSION ”’ || v1_sid || ‘, ‘ || v1_serial || ””;

END LOOP;
CLOSE C1;
COMMIT;
END;