Hi Doesn't rebuilding actually use the existing index to read the data from, so rebuild will actually hit the corruption? From documentation: http://www.filibeto.org/sun/lib/nonsun/oracle/10.2.0.1.0/B19306_01/server.102/b14231/indexes.htm#i1006864 "When you rebuild an index, you use an existing index as the data source." So drop and create the index. 1. Get the index DDL using DBMS_METADATA.GET_DDL select dbms_metadata.get_ddl('INDEX','SMON_SCN_TIME_TIM_IDX') txt from dual; 2. Drop old index: drop index SMON_SCN_TIME_TIM_IDX; 3. Run create index statement returned from dbms_metadata.get_ddl On Tue, Aug 24, 2010 at 8:55 PM, Andrew Kerber <andrew.kerber@xxxxxxxxx> wrote: > I suggested new tablespace in case there is physical corruption. Moving the > index would take it off of the bad spot. > > On Tue, Aug 24, 2010 at 12:47 PM, Bobak, Mark <Mark.Bobak@xxxxxxxxxxxx> > wrote: >> >> I’m not sure the new tablespace would be required either, but I’m pretty >> sure ‘online’ option is out of the question, as that’s an Enterprise Edition >> only option, if I’m not mistaken. >> >> >> >> -Mark >> >> >> >> From: oracle-l-bounce@xxxxxxxxxxxxx [mailto:oracle-l-bounce@xxxxxxxxxxxxx] >> On Behalf Of Uzzell, Stephan >> Sent: Tuesday, August 24, 2010 1:44 PM >> To: 'andrew.kerber@xxxxxxxxx'; jepettrey@xxxxxxxxx >> Cc: Oracle-L@xxxxxxxxxxxxx >> Subject: RE: Oracle XE Corruption >> >> >> >> Wouldn’t just a simple rebuild online suffice? Why move it to a new >> tablespace if it is an object owned by SYS? -- Ilmar Kerm -- //www.freelists.org/webpage/oracle-l