Read only has to do with dml, has nothing to do with ddl.
Waleed
-- --Original Message-- -- From: jungwolf [mailto:spatenau@(protected)]=20 Sent: Thursday, March 03, 2005 4:35 PM To: Khedr, Waleed Cc: oracle-l@(protected) Subject: Re: how can you protect read-only indexes?
On Thu, 3 Mar 2005 14:52:15 -0500, Khedr, Waleed <Waleed.Khedr@(protected)> wrote: > I know I'm not answering your question, but I have to say that you need > to fix the processes themselves that are causing these issues. > Also why does the process drop the indexes if it failed truncating the > table. > You need to defined some dependencies and abort mechanisms. >=20 > Regards, >=20 > Waleed
Well, of course the process needs to be reconfigured but that's not the point at all. The point is, why are objects in a readonly tablespace vulnerable to being dropped? That's counterintuitive behavior even if it does make sense after thinking about the implementation. I think the original poster was asking if she can make readonly tablespaces act with the expected behavior.
The best idea I've seen has been the trigger option from Juan. I haven't looked at triggers at the DB level so I'm not sure how much security it'll provide, but at least it holds promise. For example: SQL> create trigger boo before drop on database DECLARE eERROR exception; begin raise eerror; end; / 2 3 4 5 6 7 8 9 Trigger created.
