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

Home -> Community -> Mailing Lists -> Oracle-L -> RE: Read Only User

RE: Read Only User

From: Gogala, Mladen <MGogala_at_allegientsystems.com>
Date: Thu, 16 Dec 2004 15:11:09 -0500
Message-ID: <D42C14B2E3F2B74DB41D5B6B2E2B992F01931FAB@pegasus.lawaudit.com>


And user "MLADEN" would blow away your rollback segments in no time. Setting transaction to read only would cause me to read all data in the consistent mode, as it was when the transaction started. Fews hour later and few inspected tables later, DBA would be having loads of fun. In addition to that, the whole story would last only until I executed commit. After that, the transaction is over. New transaction wouldn't be read only unless I specify so myself. Juan, when I come to think of it, you should continue with your DBA tips.
--

Mladen Gogala
Ext. 121

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

From: Juan Carlos Reyes Pacheco [mailto:jreyes_at_dazasoftware.com] Sent: Thursday, December 16, 2004 2:36 PM To: oracle-l_at_freelists.org
Subject: Re: Read Only User

Hi I search some solution and found this , Maybe this trigger could help in some cases, why don't you test.
:)  

CREATE TRIGGER FON.SADFASDF
AFTER
LOGON
ON DATABASE
..
WHEN USER='MLADEN' THEN SET TRANSACTION READ ONLY; ..
/  

--

http://www.freelists.org/webpage/oracle-l Received on Thu Dec 16 2004 - 14:15:47 CST

Original text of this message

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