Oracle FAQ | Your Portal to the Oracle Knowledge Grid |
![]() |
![]() |
Home -> Community -> Mailing Lists -> Oracle-L -> RE: methodology to keep only certain programs to connect to
This message is in MIME format. Since your mail reader does not understand
this format, some or all of this message may not be legible.
------_=_NextPart_001_01C258DF.B2F30EE0
Content-Type: text/plain; charset="ISO-8859-1"
Joe
You can use the sys_context function to get the auditing session id -
select * from v$session where audsid = sys_context('USERENV','SESSIONID');
David Lord
-----Original Message-----
From: JOE TESTA [mailto:JTESTA_at_longaberger.com]
Sent: 10 September 2002 16:58
To: Multiple recipients of list ORACLE-L
Subject: methodology to keep only certain programs to connect to
I've been tasked to ensure only certain app programs access the database.
I'm thinking on-logon trigger, check the program field from v$session. unfortunately v$session is for all sessions, i can't seem to find the view that tells me only MY info during login. I only want the sid, serial#, username and program for my just now connection to the database.
Does this exist or am I going about this the wrong way?
We're thinking of checking those fields to make sure sql*plus, toad, etc can't connect as a particular user(even though the password is known out in the community).
any ideas would be greatly appreciated.
joe
A member of the Hays plc group of companies. Hays plc is registered in England and Wales number 2150950. Registered Office Hays House Millmead Guildford Surrey GU2 4HJ.
------_=_NextPart_001_01C258DF.B2F30EE0
Content-Type: text/html; charset="ISO-8859-1"
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1">
<META content="MSHTML 6.00.2716.2200" name=GENERATOR></HEAD>
<BODY style="MARGIN-TOP: 2px; FONT: 10pt Times New Roman; MARGIN-LEFT: 2px">
<DIV><SPAN class=484575315-10092002>Joe</SPAN></DIV>
<DIV><SPAN class=484575315-10092002></SPAN> </DIV>
<DIV><SPAN class=484575315-10092002>You can use the sys_context function to get
the auditing session id - </SPAN></DIV>
<DIV><SPAN class=484575315-10092002></SPAN> </DIV>
<DIV><SPAN class=484575315-10092002></SPAN><SPAN class=484575315-10092002>
</SPAN>select * from v$session where audsid =
sys_context('USERENV','SESSIONID');</DIV>
<DIV> </DIV>
<DIV><SPAN class=484575315-10092002>David Lord</SPAN></DIV>
<BLOCKQUOTE dir=ltr
style="PADDING-LEFT: 5px; MARGIN-LEFT: 5px; BORDER-LEFT: #000000 2px solid; MARGIN-RIGHT: 0px">
<DIV class=OutlookMessageHeader dir=ltr align=left><FONT
face=Tahoma>-----Original Message-----<BR><B>From:</B> JOE TESTA
[mailto:JTESTA_at_longaberger.com]<BR><B>Sent:</B> 10 September 2002
16:58<BR><B>To:</B> Multiple recipients of list ORACLE-L<BR><B>Subject:</B>
methodology to keep only certain programs to connect to<BR><BR></FONT></DIV>
<DIV>I've been tasked to ensure only certain app programs access the
database.</DIV>
<DIV> </DIV>
<DIV>I'm thinking on-logon trigger, check the program field from
v$session. unfortunately v$session is for all sessions, i can't seem to
find the view that tells me only MY info during login. I only want the
sid, serial#, username and program for my just now connection to the
database.</DIV>
<DIV> </DIV> <DIV>Does this exist or am I going about this the wrong way?</DIV> <DIV> </DIV> <DIV>We're thinking of checking those fields to make sure sql*plus, toad, etccan't connect as a particular user(even though the password is known out in the community).</DIV>
<DIV> </DIV> <DIV>any ideas would be greatly appreciated.</DIV> <DIV> </DIV> <DIV>joe</DIV> <DIV> </DIV></BLOCKQUOTE><CODE><FONT SIZE=3><BR>
**********************************************************************<BR>This message (including any attachments) is confidential and may be <BR> legally privileged. If you are not the intended recipient, you should <BR> not disclose, copy or use any part of it - please delete all copies <BR> immediately and notify the Hays Group Email Helpdesk at<BR> email.helpdesk_at_hays.plc.uk<BR>
**********************************************************************<BR>Received on Tue Sep 10 2002 - 10:35:32 CDT
![]() |
![]() |