How to raise an exeption in PL/SQL when the client session has terminated?

Question

Due to metalink Note:310924.1, I tried a similar demo script in my 10gR2 database;
session 1)
CREATE TABLE tbl_test(col1 NUMBER,
col2 VARCHAR2(256));
DECLARE
v_client_ip_addr VARCHAR2(15) := '';
v_sqlcode NUMBER;
v_sqlerrm VARCHAR2(256) := '';
BEGIN
FOR i IN 1 .. 10 LOOP
v_client_ip_addr := sys_context('USERENV',
'IP_ADDRESS');
INSERT INTO tbl_test VALUES (i, v_client_ip_addr);
dbms_lock.sleep(5); -- 5 saniye uyu
END LOOP;
ROLLBACK;
EXCEPTION
WHEN OTHERS THEN
v_sqlcode := SQLCODE;
v_sqlerrm := SQLERRM;
INSERT INTO tbl_test VALUES (v_sqlcode, v_sqlerrm);
COMMIT;
END;
session 2)
kill the process
but result is not similar with the metalink note, no rows returned;
SQL>
Table created
DECLARE
v_client_ip_addr VARCHAR2(15) := '';
v_sqlcode NUMBER;
v_sqlerrm VARCHAR2(256) := '';
BEGIN
FOR i IN 1 .. 10 LOOP
v_client_ip_addr := sys_context('USERENV',
'IP_ADDRESS');
INSERT INTO tbl_test VALUES (i, v_client_ip_addr);
dbms_lock.sleep(5); -- 5 saniye uyu
END LOOP;
ROLLBACK;
EXCEPTION
WHEN OTHERS THEN
v_sqlcode := SQLCODE;
v_sqlerrm := SQLERRM;
INSERT INTO tbl_test VALUES (v_sqlcode, v_sqlerrm);
COMMIT;
END;
ORA-00028: your session has been killed
SQL> select * from tbl_test;
COL1 COL2
Any comments will be welcomed,
Thank you :)
Kind regards.
H.Tonguc YILMAZ
Turkcell Ar-Ge, Yazılım Geliştirme
[email protected]
"Learning is expensive, not more than unawareness."

Answer 1

Confirm. That Metalink Note is incorrect.
I've tested against Oracle 10G (1.2.0.1) using both dedicated and shared server connections. In both cases the exception handler did not catch the exception raised for a killed session.
Interestingly the exception stack is slightly different between dedicated and shared server.
Shared server:
ERROR at line 1:
ORA-00028: your session has been killed
ORA-06512: at "SYS.DBMS_LOCK", line 201
ORA-06512: at "BILLY.KILLTEST", line 9
ORA-06512: at line 1
Dedicated server:
ERROR at line 1:
ORA-00028: your session has been killed
I did a minor modification to the code:
connect scott/tiger
drop table tbl_test;
create table tbl_test (col1 number, col2 varchar2(15));
create or replace procedure KillTest is
v_client_ip_addr VARCHAR2(15) := '';
begin
for i in 1..10
loop
v_client_ip_addr := SYS_CONTEXT('USERENV','IP_ADDRESS');
insert into tbl_test values (i, v_client_ip_addr);
commit;
dbms_lock.sleep(5);
end loop;
exception
when OTHERS then
insert into tbl_test values (0, 'exception');
commit;
end;
exec killtest
-- kill this session from another SQL*Plus session
connect scott/tiger
select * from tbl_test;
It is not unusual that an application exception handler does not catch all exceptions - also not in PL/SQL. I recall other instances where I also had system related exceptions that could not be caught via an application exception handler in PL/SQL.
This makes sense as a system related error could "damage" the PL/SQL engine's heap and stack to such an extent that it is unsafe to proceed with the execution of the engine. Thus any application handlers that the engine would have executed under non-system error conditions, are not executed at all.
Whether a kill of a session translates into a such a serious system error to cause this, is of course debatable.