RE: Read Only User

Thanks for the advice :)
 
Juan Carlos Reyes Pacheco
OCP
-------Original Message-------
 
From: Gogala, Mladen
Date: 12/16/04 16:13:46
To: 'jreyes@xxxxxxxxxxxxxxxx'
Cc: oracle-l@xxxxxxxxxxxxx
Subject: RE: Read Only User
 
 
 
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@xxxxxxxxxxxxxxxx] 
Sent: Thursday, December 16, 2004 2:36 PM 
To: oracle-l@xxxxxxxxxxxxx 
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

Other related posts: