RE: Read Only User
- From: "Post, Ethan" <Ethan.Post@xxxxxx>
- To: <jreyes@xxxxxxxxxxxxxxxx>, <oracle-l@xxxxxxxxxxxxx>
- Date: Thu, 16 Dec 2004 14:39:42 -0600
Can't drop a connected user last time I checked, you need to kill
session, then drop, may require a DBMS_JOB call to accomplish, watch out
for the bug which causes jobs not to run, been hitting that one today on
some other things. We are getting into borderline virus writing here, I
am sure Pete can tell us a few easy ways to deliver the payload.
-----Original Message-----
From: oracle-l-bounce@xxxxxxxxxxxxx
[mailto:oracle-l-bounce@xxxxxxxxxxxxx] On Behalf Of Juan Carlos Reyes
Pacheco
Sent: Thursday, December 16, 2004 2:27 PM
To: oracle-l@xxxxxxxxxxxxx
Subject: RE: Read Only User
Not good. What would stop mladen from altering his session to 'read
wirte'
after he's connected?
Hi, in that case you can change the trigger
CREATE TRIGGER FON.SADFASDF
AFTER
LOGON
ON DATABASE
.
WHEN USER=3D'MLADEN' THEN DROP USER MLADEN;
.
/
:)
=20
--
//www.freelists.org/webpage/oracle-l
Other related posts:
