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

2003-10-07 Thread Paul Drake
--- Paul Drake [EMAIL PROTECTED] wrote:
 --- Jacques Kilchoer [EMAIL PROTECTED]
 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.

Pd

__
Do you Yahoo!?
The New Yahoo! Shopping - with improved product search
http://shopping.yahoo.com
-- 
Please see the official ORACLE-L FAQ: http://www.orafaq.net
-- 
Author: Paul Drake
  INET: [EMAIL PROTECTED]

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: [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).


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

2003-10-07 Thread Jacques Kilchoer
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 [EMAIL PROTECTED] wrote:
  --- Jacques Kilchoer [EMAIL PROTECTED]
  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: [EMAIL PROTECTED]

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: [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).


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

2003-10-06 Thread John Kanagaraj
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

** The opinions and facts contained in this message are entirely mine and do
not reflect those of my employer or customers **
-- 
Please see the official ORACLE-L FAQ: http://www.orafaq.net
-- 
Author: John Kanagaraj
  INET: [EMAIL PROTECTED]

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: [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).


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

2003-10-06 Thread Jacques Kilchoer
Thank you John. I guess I can revise my question, then, to say Why not use 
SID/SERIAL# all the time? :)
I suppose there are reasons but it seems unnecessary to have two sets of values that 
uniquely identify a session. Though of course, from the documentation, AUDSID is 
unique over the lifetime of the database (generated from sequence SYS.AUDSES$) and 
SID/SERIAL# would not be unique over the lifetime of the database.

 -Original Message-
 John Kanagaraj
 Sent: lundi, 6. octobre 2003 15:59
 
 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!
-- 
Please see the official ORACLE-L FAQ: http://www.orafaq.net
-- 
Author: Jacques Kilchoer
  INET: [EMAIL PROTECTED]

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: [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).


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

2003-10-06 Thread Paul Drake
--- Jacques Kilchoer [EMAIL PROTECTED]
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

__
Do you Yahoo!?
The New Yahoo! Shopping - with improved product search
http://shopping.yahoo.com
-- 
Please see the official ORACLE-L FAQ: http://www.orafaq.net
-- 
Author: Paul Drake
  INET: [EMAIL PROTECTED]

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: [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).