RE: Read Only User

From: Gogala, Mladen <MGogala_at_allegientsystems.com>
Date: Thu, 16 Dec 2004 13:14:25 -0500
Message-ID: <D42C14B2E3F2B74DB41D5B6B2E2B992F01931FA5@pegasus.lawaudit.com>

The trick that will disable modifications from procedures is to do the following, logged in as SYSDBA: startup force mount
alter database open read only

Your read-only user will not be able to modify anything in the database, regardless of the procedures that he has access to.

--

Mladen Gogala
Ext. 121

-----Original Message-----

From: Powell, Mark D [mailto:mark.powell_at_eds.com] Sent: Thursday, December 16, 2004 12:41 PM To: oracle-l_at_freelists.org
Subject: RE: Read Only User

But does the read only user really have to have access to the stored code routines? Eliminate that requirement and then you do not need to worry about either the overhead of an extra trigger on every table or having to maintain masking routines for every package that has update procedures on your system.

--

http://www.freelists.org/webpage/oracle-l Received on Thu Dec 16 2004 - 12:22:41 CST