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
My experience is that an invalid trigger doesn't fire --- no effect.
Also, userids with the DBA role don't fire the trigger. So you can't l=
ock
yourself out of the database. Just go in with a DBA role userid and dr=
op
the logon trigger.
=
=20
"Markham, =
=20
Richard" To: Multiple recipients of= list ORACLE-L <ORACLE-L_at_fatcity.com> =20 <RMarkham cc: =
=20
@hafeleameric Subject: RE: methodology t= o keep only certain programs to connect to =20 as.com> =
=20
Sent by: root =
=20
=
=20
=
=20
09/10/2002 =
=20
01:18 PM =
=20
Please =
=20
respond to =
=20
ORACLE-L =
=20
=
=20
=
=20
what are the drawbacks with such a trigger, what if the code went inva=
lid
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:
--=A0 Set a unique string for the session and update the session info.=
client_info_str :=3D 'WTWLOGIN_' || LTRIM(dbms_random.value,'.'); DBMS_APPLICATION_INFO.SET_CLIENT_INFO(client_info_str);
osuser, terminal, machine
INTO loc_program, loc_username,
loc_osuser,loc_terminal,loc_machine Received on Tue Sep 10 2002 - 14:24:36 CDT
![]() |
![]() |