Stephane Faroult wrote: Killing Oracle server processes is definitely bad manners. Especially if you are using MTS. Even if you are not, the proper way to kill an Oracle process is to use ALTER SYSTEM KILL SESSION. I think that you should use the DBMS_APPLICATION_INFO package to set something like 'Hey! Shoot me!' in your CLIENT_INFO column in V$PROCESS - it would make it easier to another process to log as DBA, spot the process and bang.
--------- Stephane, We will certainly disagree on that. I contend that you should *always* kill the process first. The reason being that using 'ALTER SYSTEM KILL SESSION' has a nasty habit of hanging sessions that are holding locks. I've seen it happen on all versions from 7.0.16 - 8.1.6, on DG/UX, Windows NT 4.0 and Solaris 2.5 - 2.6. It has become my habit to always kill the process ( if dedicated server ) or NT thread first. If the session still appears in v$session, use ALTER SYSTEM KILL SESSION to finish it off. Works every time. Doing it Oracle's way has necessitated too many database bounces for my tastes. Jared -- Please see the official ORACLE-L FAQ: http://www.orafaq.com -- Author: INET: [EMAIL PROTECTED] Fat City Network Services -- (858) 538-5051 FAX: (858) 538-5051 San Diego, California -- Public Internet access / Mailing Lists -------------------------------------------------------------------- To REMOVE yourself from this mailing list, send an E-Mail message to: [EMAIL PROTECTED] (note EXACT spelling of 'ListGuru') and in the message BODY, include a line containing: UNSUB ORACLE-L (or the name of mailing list you want to be removed from). You may also send the HELP command for other information (like subscribing).
