Oracle FAQ Your Portal to the Oracle Knowledge Grid
HOME | ASK QUESTION | ADD INFO | SEARCH | E-MAIL US
 

Home -> Community -> Mailing Lists -> Oracle-L -> RE: sid/serial# vs. audsid: why both?

RE: sid/serial# vs. audsid: why both?

From: John Kanagaraj <john.kanagaraj_at_hds.com>
Date: Mon, 06 Oct 2003 14:59:27 -0800
Message-ID: <F001.005D230D.20031006145927@fatcity.com>


Jacques,

>In what cases does the SERIAL# need to be used? Can someone give an example
where a session-level command would be
>applied to an incorrect session object if SERIAL# were not available?

For backward compatibility reasons :) Looks like AUDSID wasn't generated 7.2 and prior unless AUDIT_TRAIL was TRUE (even if you don't use auditing). A lot of scripts use SERIAL# and the ALTER SYSTEM KILL SESSION uses the serial#, which should always be available.

>Why not use AUDSID all the time? Is there a reason why the database keeps
track of two session identifying numbers?

AUDSID is 0 if connecting as internal. Notes 123128.1 and 122230.1 may help!

John Kanagaraj
DB Soft Inc
Phone: 408-970-7002 (W)

Listen to great, commercial-free christian music 24x7x365 at http://www.klove.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 Mon Oct 06 2003 - 17:59:27 CDT

Original text of this message

HOME | ASK QUESTION | ADD INFO | SEARCH | E-MAIL US