Re: methodology to keep only certain programs to connect to

[Yechiel Adar]

Hello Joe   I implemented today Tom's trigger in one of our test databases and it works fine. I am using it to track which users / applications are connecting so we can notify them in case of scheduled down time or problems.   You need to run dbmsrand.sql to add dbms_random package to the database.   Yechiel Adar Mehish ----- Original Message ----- From: JOE TESTA To: Multiple recipients of list ORACLE-L Sent: Tuesday, September 10, 2002 5:58 PM 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