Re: Logical block corruption

From: <johnbhurley_at_sbcglobal.net>
Date: Tue, 31 Mar 2009 17:38:17 -0700 (PDT)
Message-ID: <20f5ae16-9cde-44b9-9a72-052867e92c64_at_b16g2000yqb.googlegroups.com>

On Mar 31, 4:56 pm, Ste <s..._at_ste.it> wrote:
> Hi all,
>
> from yesterday my RMAN full backup is failing due to logical block
> corruption. Using dbv I've found that all datafiles belonging to a
> tablespace have index pages corrupted.
>
> Block Checking: DBA = 260237463, Block Type = KTB-managed data block
> **** actual rows locked by itl 2  = 163 != # in trans. header = 162
> ---- end index block validation
> Page 190615 failed with check code 6401
> Block Checking: DBA = 260237473, Block Type = KTB-managed data block
> **** actual rows locked by itl 2  = 274 != # in trans. header = 273
> ---- end index block validation
> ............SKIP.................
> Block Checking: DBA = 260305750, Block Type = KTB-managed data block
> **** actual rows locked by itl 2  = 333 != # in trans. header = 332
> ---- end index block validation
> Page 258902 failed with check code 6401
>
> DBVERIFY - Verification complete
>
> Total Pages Examined         : 381440
> Total Pages Processed (Data) : 270535
> Total Pages Failing   (Data) : 0
> Total Pages Processed (Index): 30095
> Total Pages Failing   (Index): 35
> Total Pages Processed (Other): 189
> Total Pages Empty            : 80621
> Total Pages Marked Corrupt   : 0
> Total Pages Influx           : 0
>
> I want to use dbms_repair(i'm running oracle 8.1.7.4) but there's a way
> to fix the whole tablespace?
>
> Thanks
> Ste

Why don't you drop and re-create the indexes that have the problems?

If you were up to a more recent release you could use rman validate check logical database and rman recover corruption list ... Received on Tue Mar 31 2009 - 19:38:17 CDT