Re: kill session that holds lock for more then 10 sec

"Harald Maier" <harald_at_maierh.de> schrieb im Newsbeitrag news:m38ykcm7m1.fsf_at_ate.maierh...
> "Volker Hetzer" <volker.hetzer_at_ieee.org> writes:
>
> > "Paul Drake" <drak0nian_at_yahoo.com> schrieb im Newsbeitrag
> > news:1ac7c7b3.0401122252.dcaf2d9_at_posting.google.com...
> >> ALTER SYSTEM KILL SESSION is not the way to go.
> >>
> >> you could conceivably wait hours for the session to be killed and
> >> the lock(s) to be released. don't go with a DBMS_JOB, schedule an
> >> OS task so that you can leverage orakill.exe. that will seriously
> >> kill a session.
> >>
> >> basically, use a batch file to call sqlplus. in sqlplus run a
> >> script to spool an orakill script quit sqlplus and execute the
> >> spooled .bat file for bonus points, you could log the offending
> >> user that held the lock too long (although 60 seconds seems to be a
> >> little too short to me).
> >>
> >> D:\oracle\ora81\bin>orakill
> > Does something like this exist on unix too?
>
> orakill allows under Windows to kill a thread of the one Oracle
> Process. Under Unix Oracle is designed to use many processes so there
> is no necessity to have a orakill utility. The Unix kill command is
> enough.

Is it *safe* to kill a user session with kill or kill -9? I always thought the oracle process had some cleanup responsibility too?

Lots of Greetings!
Volker Received on Tue Jan 13 2004 - 05:24:55 CST