RE: Limiting user connections with DBA Studio

[Todd Carlson]

Title: RE: Database Verification

You should kill the previous DBA too. ;-)   Todd   -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]] On Behalf Of [EMAIL PROTECTED] Sent: Friday, January 17, 2003 2:24 PM To: Multiple recipients of list ORACLE-L Subject: RE: Limiting user connections with DBA Studio   Todd,   The previous DBA has granted them almost all the privileges except DBA privilege.  Now, when we tried to take away this SELECT_CATALOG_ROLE, then, these specific users started raising alarms.   So, what we are planning is to kill their session the moment we find that they are using DBA Studio.    Rao -----Original Message----- From: Todd Carlson [mailto:[EMAIL PROTECTED]] Sent: Friday, January 17, 2003 2:10 PM To: Multiple recipients of list ORACLE-L Subject: RE: Limiting user connections with DBA Studio They can’t use it unless they can select from the data dictionary views. For example, if they don’t the SELECT_CATALOG_ROLE role or DBA privs in 8.1.7 they can not use DBA Studio.   Todd   -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]] On Behalf Of [EMAIL PROTECTED] Sent: Friday, January 17, 2003 11:09 AM To: Multiple recipients of list ORACLE-L Subject: Limiting user connections with DBA Studio   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