Hi,
I suggest you use dbv to verify it and find the segment according to
file_id and block_number (dba_extents).
And try analyze validate structure.

If really corrupted, you have to recreate it. Maybe it is rman bug, if
oracle really block corruption, there should be ora-1578 in alert logfile
when other SQL is visiting that block.

Any way, verify it first.

Regards
zhu chao
msn:[Email Address Removed] Original Message -----
From: "Roger Xu" <[Email Address Removed] "LazyDBA.com Discussion" <[Email Address Removed] Thursday, August 28, 2003 11:22 PM
Subject: Bad header found during backing up datafile


In our development box, when RMAN is running, I see the following
messages only in the alert.log quite often.
And it seems to me always happens in the index tablespace.
I ran dbverify and validate structure of the whole database
with no corruption reported.

Any comments?





***
Corrupt block relative dba: 0x13c2c44c (file 79, block 181324)
Bad header found during backing up datafile
Data in bad block -
type: 48 format: 1 rdba: 0x3939390a
last change scn: 0x3537.31333031 seq: 0x34 flg: 0x38
consistency value in tail: 0x791b0602
check value in block header: 0x3431, block checksum disabled
spare1: 0x4, spare2: 0x31, spare3: 0x330
***
Reread of blocknum=181324, file=/oracle/DV2/sapdata3/btabi_15/btabi.data15.
found valid data


Roger Xu
Database Administrator
Dr Pepper Bottling Company of Texas
(972)721-8337


--------
Oracle documentation is here:
http://tahiti.oracle.com/pls/tahiti/tahiti.homepage
To unsubscribe: send a blank email to oracledba-[Email Address Removed] subscribe: send a blank email to oracledba-[Email Address Removed] the list archive: http://www.LAZYDBA.com/odbareadmail.pl
Tell yer mates about http://www.farAwayJobs.com
By using this list you agree to these
terms:http://www.lazydba.com/legal.html




Oracle LazyDBA home page