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_01C25990.C7620E10

Content-Type: text/plain;

        charset="iso-8859-1"

I have seen invalid triggers cause ORA-604 errors.

-----Original Message-----

From: Markham, Richard [mailto:RMarkham_at_hafeleamericas.com] Sent: Tuesday, September 10, 2002 12:19 PM To: Multiple recipients of list ORACLE-L Subject: RE: methodology to keep only certain programs to connect to

what are the drawbacks with such a trigger, what if the code went invalid and would not compile is
it possible that you could lock yourself out, or would the base login functionality still work regardless
or the status of this trigger?

-----Original Message-----

From: Mercadante, Thomas F [mailto:NDATFM_at_labor.state.ny.us] Sent: Tuesday, September 10, 2002 12:24 PM To: Multiple recipients of list ORACLE-L Subject: RE: methodology to keep only certain programs to connect to

Joe,  

I use the following with decent success on a logon database trigger:    

• Set a unique string for the session and update the session info. client_info_str := 'WTWLOGIN_' || LTRIM(dbms_random.value,'.'); DBMS_APPLICATION_INFO.SET_CLIENT_INFO(client_info_str);
• look into the v$session view for the session just connected. SELECT program, username,

osuser, terminal, machine
INTO loc_program, loc_username,

loc_osuser,loc_terminal,loc_machine
FROM V$SESSION Received on Wed Sep 11 2002 - 07:43:07 CDT