Oracle FAQ Your Portal to the Oracle Knowledge Grid
HOME | ASK QUESTION | ADD INFO | SEARCH | E-MAIL US
 

Home -> Community -> Usenet -> c.d.o.server -> Re: trigger problem

Re: trigger problem

From: Tony Andrews <andrewst_at_onetel.com>
Date: 15 Apr 2005 07:51:07 -0700
Message-ID: <1113576667.882543.220330@g14g2000cwa.googlegroups.com>


DA Morgan wrote:
> "ORA-20000: You have attempted to use TOAD to access a production
> database in violation of company policy. An email has been sent to
> HR and your manager notifying that you have violated company policy"

But what is so special about Toad that it alone should be banned? What can a developer do to the production database with Toad that he/she could not do with SQL Plus, Forms, HTMLDB, or any one of dozens of other ways to access the database?

Surely what needs to be done is to make sure that developers are limited in what they can do via ANY access method, such as:

- don't let them know the DBA/schema password
- restrict their privileges on objects as appropriate
- use resource limits to prevent them from running crippling queries
- etc.

Plus maybe use auditing to monitor what they do... Received on Fri Apr 15 2005 - 09:51:07 CDT

Original text of this message

HOME | ASK QUESTION | ADD INFO | SEARCH | E-MAIL US