You need to configure accounts and security differently. Don't give owner id to developers.
Waleed
-- --Original Message-- -- From: Carmen Rusu [mailto:carmen.rusu@(protected)]=20 Sent: Thursday, March 03, 2005 11:03 AM To: oracle-l@(protected) 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