RE: Read Only User
- From: "Gogala, Mladen" <MGogala@xxxxxxxxxxxxxxxxxxxx>
- To: "'mark.powell@xxxxxxx'" <mark.powell@xxxxxxx>, oracle-l@xxxxxxxxxxxxx
- Date: Thu, 16 Dec 2004 13:14:25 -0500
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@xxxxxxx]
Sent: Thursday, December 16, 2004 12:41 PM
To: oracle-l@xxxxxxxxxxxxx
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.
--
//www.freelists.org/webpage/oracle-l
Other related posts:
