But the fundamental question is why prevent them.
What damage are they causing?
Control their actions via proper permissions.
If OEM installation is against Company policy (or "they did not ask the Oracle DBA Group"), then the problem should be addressed via other administrative procedures.
> maheswara.rao_at_sungard.com wrote:
>
> Some of our users installed OEM on their local PC's. They connect to
> the database through DBA Studio.
>
> Is there any way to prevent DBA Studio connections to the server? I
> am thinking of using on_logon trigger but no clue how to catch the
> connection.
>
> Any suggestions?
>
> Rao
--
Please see the official ORACLE-L FAQ: http://www.orafaq.net
--
Author: Deshpande, Kirti
INET: kirti.deshpande_at_verizon.com
Fat City Network Services -- 858-538-5051 http://www.fatcity.com
San Diego, California -- Mailing list and web hosting services
---------------------------------------------------------------------
To REMOVE yourself from this mailing list, send an E-Mail message
to: ListGuru_at_fatcity.com (note EXACT spelling of 'ListGuru') and in
the message BODY, include a line containing: UNSUB ORACLE-L
(or the name of mailing list you want to be removed from). You may
also send the HELP command for other information (like subscribing).
Received on Fri Jan 17 2003 - 13:50:21 CST
