Re: own session's SID

Or you could create a logon trigger that acquired the value and stuffed it into a context so that the user could use a call to sys_context('your_system_context','sid').

Probably more efficient for the user to
call sys_context than it would be to call a home-grown pl/sql function. (Not guaranteed, of course, as sys_context() is resolved in pl/sql through a select from dual).

Regards

Jonathan Lewis

http://www.jlcomp.demon.co.uk/faq/ind_faq.html The Co-operative Oracle Users' FAQ

http://www.jlcomp.demon.co.uk/seminar.html Optimising Oracle Seminar - schedule updated Sept 19th

• Original Message ----- From: "Gogala, Mladen" <Mladen.Gogala_at_aetn.com> To: "'Ruth Gramolini'" <rgramolini_at_tax.state.vt.us>;
  <jonathan_at_jlcomp.demon.co.uk>; "Gogala, Mladen" <Mladen.Gogala_at_aetn.com>;
  <thomas.mercadante_at_labor.state.ny.us>; <mark.powell_at_eds.com>;
  <oracle-l_at_freelists.org>
  Sent: Friday, October 15, 2004 9:47 PM Subject: RE: own session's SID

No, it's by no means a 10g thing. It is unsupported/undocumented stuff. It's like using an 18-wheeler to drive from home to a grocery shop and back. It works, but..... On top of that, you probably wouldn't want to grant execute on DBMS_SUPPORT to public. In other works, DBMS_SUPPORT is not an answer. Create function as the user system, create public synonym and grant execute on the function to public. When oracle doesn't want to do it for you, you have to take matters in your own hands.

--
Mladen Gogala
A & E TV Network
Ext. 1216



--
http://www.freelists.org/webpage/oracle-l