RE: how can you protect read-only indexes?
- From: "Carmen Rusu" <carmen.rusu@xxxxxxxxxxxxxxx>
- To: <oracle-l@xxxxxxxxxxxxx>, <Les.Hollis@xxxxxx>
- Date: Thu, 03 Mar 2005 11:43:56 -0600
I know that tablespaces are logical structures and as such you are not
"writing" anything to them.
You are physically processing the datafiles that are part of the
tablespace definition.
What I am looking for is a simple and elegant solution to prevent the
drop of my indexes when they live on a read-only tablespace
:-)
Thanks,
-Carmen
>>> "Hollis, Les" <Les.Hollis@xxxxxx> 3/3/2005 11:34:28 AM >>>
Just a little FYI here.
You can also drop a table IF the underlying tablespace is READ-ONLY.
The reason this is allowed is that you are only making entries in the
data dictionary when you drop an object. AND/OR to the datafile header
if you are locally managed tablespaces. You are writing anything to
the
READ-ONLY tablespace.
-----Original Message-----
From: oracle-l-bounce@xxxxxxxxxxxxx
[mailto:oracle-l-bounce@xxxxxxxxxxxxx] On Behalf Of Carmen Rusu
Sent: Thursday, March 03, 2005 10:03 AM
To: oracle-l@xxxxxxxxxxxxx
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?
Thanks,
-Carmen Rusu
Oracle DBA
--
//www.freelists.org/webpage/oracle-l
--
//www.freelists.org/webpage/oracle-l
Other related posts:
