Hi all,

Yes, I know that this post is half year old, but I had the same problem today. I just want to share my findings with you.

I also thought that I am waiting for rollback, but then noticed in log table, that the procedure is continuing doing its stuff.
Then I killed it from OS, but why was that necessary....

Well, after some testing I found out, that "exception when others" catches "ORA-00028: your session has been killed" exception like any other and the loop continues till the real end.

I don't think this is expected behaviour... at least, I haven't expected it
Looks like killing for oracle means just pushing an "you have been killed" exception to the victim's session. So we can make any code unkillable, if we want to.
Strange!

Comments?

Have fun,
Tomaz