From oracle-l-bounce@freelists.org Thu Mar 3 12:59:06 2005 Return-Path: Received: from air891.startdedicated.com (root@localhost) by orafaq.com (8.12.10/8.12.10) with ESMTP id j23Ix6gE014197 for ; Thu, 3 Mar 2005 12:59:06 -0600 X-ClientAddr: 206.53.239.180 Received: from turing.freelists.org (freelists-180.iquest.net [206.53.239.180]) by air891.startdedicated.com (8.12.10/8.12.10) with ESMTP id j23Ix4em014190 for ; Thu, 3 Mar 2005 12:59:04 -0600 Received: from localhost (localhost [127.0.0.1]) by turing.freelists.org (Avenir Technologies Mail Multiplex) with ESMTP id 69F417DF8A; Thu, 3 Mar 2005 12:45:48 -0500 (EST) Received: from turing.freelists.org ([127.0.0.1]) by localhost (turing [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 13921-10; Thu, 3 Mar 2005 12:45:48 -0500 (EST) Received: from turing (localhost [127.0.0.1]) by turing.freelists.org (Avenir Technologies Mail Multiplex) with ESMTP id E335D7DFA7; Thu, 3 Mar 2005 12:45:47 -0500 (EST) Message-Id: Date: Thu, 03 Mar 2005 11:43:56 -0600 From: "Carmen Rusu" To: , Subject: RE: how can you protect read-only indexes? Mime-Version: 1.0 Content-type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 8bit Content-Disposition: inline X-archive-position: 16898 X-ecartis-version: Ecartis v1.0.0 Sender: oracle-l-bounce@freelists.org Errors-To: oracle-l-bounce@freelists.org X-original-sender: carmen.rusu@rrc.state.tx.us Precedence: normal Reply-To: carmen.rusu@rrc.state.tx.us X-list: oracle-l X-Virus-Scanned: by amavisd-new-20030616-p9 (Debian) at avenirtech.net X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on air891.startdedicated.com X-Spam-Status: No, hits=0.0 required=5.0 tests=none autolearn=ham version=2.60 X-Spam-Level: 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" 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@freelists.org [mailto:oracle-l-bounce@freelists.org] On Behalf Of Carmen Rusu Sent: Thursday, March 03, 2005 10:03 AM To: oracle-l@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? Thanks, -Carmen Rusu Oracle DBA -- http://www.freelists.org/webpage/oracle-l -- http://www.freelists.org/webpage/oracle-l