Maybe it depends on the system you are using, but I have always had the
opposite experience, in that if you killed the system process first, it
somehow lost the Oracle process and you COULDN'T kill it even though it was
still running. The only solution at that point was to either wait for the
process to finish on it's own, if it could, or bounce the DB.
At 09:02 AM 11/13/00 -0800, you wrote:
>That's interesting Jared... I had always heard terrible stories about what
>could happen to you if you killed the system process first (plague, locusts,
>hung sessions, etc.) Has anyone else had similar experiences to Jared's?
>Perhaps the stuff I have heard is all "fluff". I'm certainly inclined to
>believe Jared.
>
>My question is this: When Oracle kills the session, what is it killing
>*exactly*?
>
>
>John Dailey
>Consultant
>Concept Solutions, LLC
>
>Concept Solutions, LLC
>*Your Business Intelligence Partner*
>www.concept-solutions.com
>
>
>-----Original Message-----
>Sent: Monday, November 13, 2000 11:26 AM
>To: Multiple recipients of list ORACLE-L
>
>
>
>I've found that the best method for killing session is to
>kill the system process *first*, then kill the Oracle session.
>
>PMON seems to do a better job of cleaning up sessions that way.
>Dunno why, but several years of anecdotal evidence and being
>required to bounce the DB when I didn't kill the process first
>have convinced me.
>
>Jared
>
>On Mon, 13 Nov 2000 dgoulet_at_vicr.com wrote:
Received on Mon Nov 13 2000 - 11:49:20 CST
