Oracle FAQ Your Portal to the Oracle Knowledge Grid

Home -> Community -> Mailing Lists -> Oracle-L -> RE: Authorete

RE: Authorete

From: Goulet, Dick <>
Date: Thu, 11 Mar 2004 16:26:22 -0500
Message-ID: <>

Shackles work very well in that case. Possibly you could borrow a few pairs of handcuffs from the local police department!! *-)  

Dick Goulet
Senior Oracle DBA
Oracle Certified 8i DBA

-----Original Message-----
From: April Wells [] Sent: Thursday, March 11, 2004 3:08 PM
Subject: RE: Authorete

no, I don't think that will give me what I'm really after...  

The idea is to tie the hands of the programmers to such an extent that I KNOW what they can and can not do... and how bad they can put me in a bind.  

April Wells
Oracle DBA/Oracle Apps DBA
Corporate Systems
Amarillo Texas

"Few people really enjoy the simple pleasure of flying a kite" Adam Wells age 11
"Imagination is the highest kite one can fly." Lauren Bacall

-----Original Message-----
From: Jacques Kilchoer [] Sent: Thursday, March 11, 2004 2:03 PM
Cc: April Wells
Subject: RE: Authorete

Would it also work to create a logon trigger that does an "alter session set current_schema = " instead of creating synonyms?

-----Original Message-----
From: []On Behalf Of April Wells

 Ended up having to create case sensitive synonyms (upper case version, lower case version) on the double quoted table structures or the user couldn't log in.

Granting is easy... aliasing is the interesting part.

Try create synonym user on whoever.user Oracle tends to get testy.

-----Original Message-----
From: Richard Stevenson
I guess dump software from vendors that don't understand reserved words wouldn't cut it?   

Seriously, wouldn't granting all privileges on the objects to another user work ?  

I am trying (silly me) to impose some security on this product, and they have tables called... user... privilege... group... session... and I need to have the tables owned by one user while another user can SUID the data, but not affect the table structure (got burned on financials implementation with customizations... ) and it is geeking out when the user tries to log into the front end...

The information contained in this communication, including attachments, is strictly confidential and for the intended use of the addressee only; it may also contain proprietary, price sensitive, or legally privileged information. Notice is hereby given that any disclosure, distribution, dissemination, use, or copying of the information by anyone other than the intended recipient is strictly prohibited and may be illegal. If you have received this communication in error, please notify the sender immediately by reply e-mail, delete this communication, and destroy all copies.

Corporate Systems, Inc. has taken reasonable precautions to ensure that any attachment to this e-mail has been swept for viruses. We specifically disclaim all liability and will accept no responsibility for damage sustained as a result of software viruses and advise you to carry out your own virus checks before opening any attachment.

Please see the official ORACLE-L FAQ:

To unsubscribe send email to: put 'unsubscribe' in the subject line.
Archives are at
FAQ is at
Received on Thu Mar 11 2004 - 17:28:20 CST

Original text of this message