Re: Block corruption while rebuilding the tablespace

From: Tim Gorman <>
Date: Mon, 14 Nov 2011 09:46:44 -0700
Message-ID: <>


It would be helpful to provide OS, OS version, and database version, so let's assume 10g or above...

One thing you might consider doing is reading up on the package DBMS_REPAIR, although despite the name, the package doesn't "repair" corruption, it just "fences" the corrupted blocks so that the rest of the object can be used. I've always likened this to taking your pet to the veterinarian to get "fixed"; the pet returns with something missing but is less troublesome. In this respect then, if you just want to recover the rest of the table and give up any data in that corrupted block, then consider the SKIP_CORRUPT_BLOCKS procedure in DBMS_REPAIR, which may allow your ALTER TABLE ... MOVE command to succeed with the move, but without the data from the corrupted block(s).

If you want to try to recover the data which used to be in that block, then you'll need to read up on RMAN "object point-in-time" recovery techniques or, as has already been suggested, the BLOCKRECOVER capability.

Good luck!


On 11/13/2011 10:20 PM, Shastry(DBA) wrote:
> Hello Gurus,
> I am trying to rebuild the tablespace using the move and i could move all
> the objects execpt the below table which is erroring out with block
> corruption.
> Please suggest me on this to go ahead what best options are available to
> do. Shall i do export import for this table alone.
> Problem Description: SQL> alter table XDSBIADM.CV_BOOKINGS_DETAILS_ALL_DATA
> move tablespace XDSBIADM_DATA_NEW parallel 8;
> alter table XDSBIADM.CV_BOOKINGS_DETAILS_ALL_DATA move tablespace
> XDSBIADM_DATA_NEW parallel 8
> *
> ERROR at line 1:
> ORA-12801: error signaled in parallel query server P007
> ORA-01578: ORACLE data block corrupted (file # 358, block # 267)
> ORA-01110: data file 358: '/oracle/oradata/JPRDEV/fs28/xdsbiadm_data_22.dbf'
> ORA-26040: Data block was loaded using the NOLOGGING option
> Thanks,
> Anant
> --

Received on Mon Nov 14 2011 - 10:46:44 CST

Original text of this message