Hi carmen, move to a tablespace, and make it read only. On Thu, 03 Mar 2005 10:03:01 -0600, Carmen Rusu <carmen.rusu@xxxxxxxxxxxxxxx> wrote: > 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? > > Thanks, > -Carmen Rusu > Oracle DBA > > -- > //www.freelists.org/webpage/oracle-l > -- Oracle Certified Profesional 9i 10g Orace Certified Professional Developer 6i 8 years of experience in Oracle 7,8i,9i,10g and developer 6i -- //www.freelists.org/webpage/oracle-l