Thank you for your answer. My question was more along the lines "why doesn't kill session use audsid?" Mr. Kangaraj provided the answer that audsid is 0 for some sessions, or, in older databases, when AUDIT_TRAIL is not TRUE.
My question would then be: why doesn't auditing use SID/SERIAL# instead of creating a new session identifier? But presumably only an Oracle developer could answer that question.
> -----Original Message-----
> Paul Drake
> Sent: mardi, 7. octobre 2003 00:54
>
> --- Paul Drake <discgolfdba_at_yahoo.com> wrote:
> > --- Jacques Kilchoer <Jacques.Kilchoer_at_quest.com>
> > wrote:
> > >
> > > In what cases does the SERIAL# need to be used?
> >
> > orakill.
> >
> > sqlnet.expire_timeout did not work on NT for 8.1.7.
> > garbage middle-tier apps that don't close
> > connections
> > require the use of orakill.
> >
> > Pd
>
> oops.
>
> orakill takes the ORACLE_SID and v$session.sid as
> arguments.
>
> alter system kill session takes the sid and serial
> number as arguments.
>
> I'd only use alter system to kill a session if I could
> not access the server console.
--
Please see the official ORACLE-L FAQ: http://www.orafaq.net
--
Author: Jacques Kilchoer
INET: Jacques.Kilchoer_at_quest.com
Fat City Network Services -- 858-538-5051 http://www.fatcity.com
San Diego, California -- Mailing list and web hosting services
---------------------------------------------------------------------
To REMOVE yourself from this mailing list, send an E-Mail message
to: ListGuru_at_fatcity.com (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).
Received on Tue Oct 07 2003 - 14:29:25 CDT
