RE: how can you protect read-only indexes?

From: Khedr, Waleed <Waleed.Khedr_at_FMR.COM>
Date: Thu, 3 Mar 2005 12:03:17 -0500
Message-ID: <42BBD772AC30EA428B057864E203C999013C78E5@MSGBOSCLF2WIN.DMN1.FMR.COM>

You need to configure accounts and security differently. Don't give owner id to developers.

Waleed

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

From: Carmen Rusu [mailto:carmen.rusu_at_rrc.state.tx.us]=20 Sent: Thursday, March 03, 2005 11:03 AM
To: oracle-l_at_freelists.org
Cc: Carmen Rusu
Subject: how can you protect read-only indexes?

Oracle EE 9.2.0.4 64 bit
SunOS 5.8 64bit
data warehouse db ~100gb right now, growing every month no partitioning yet

Just verified that you can drop an index when its underlying tablespace is in read-only mode.

It happened when an ETL job ran second time, by mistake. The corresponding tables, also on read-only tablespaces, survived ok the truncate op.

So, what can I do to foolproof my ETL, so that the indexes are not dropped by mistake next time?=20

Thanks,
-Carmen Rusu

Oracle DBA

--

http://www.freelists.org/webpage/oracle-l
--

http://www.freelists.org/webpage/oracle-l Received on Thu Mar 03 2005 - 12:24:02 CST