Corrupt Block, Bad Header Found Message during Rman Restore On Raw device

(Doc ID 1399327.1)

Last updated on SEPTEMBER 01, 2017

Applies to:

Oracle Database - Enterprise Edition - Version to [Release 9.2 to 11.2]
Information in this document applies to any platform.
** Checked for relevancy 22/10/2014 **


Rman restore reports corruption message

Hex dump of (file 37, block 1) in trace file /u01/oracle/product/diag/rdbms/test/trace/test_ora_1155088.trc
Corrupt block relative dba: 0x09400001 (file 37, block 1)
Bad header found during kcvxfh v8
Data in bad block:
type: 0 format: 2 rdba: 0x09400001
last change scn: 0x0000.00000000 seq: 0x1 flg: 0x05
spare1: 0x0 spare2: 0x0 spare3: 0x0
consistency value in tail: 0x00000001
check value in block header: 0x8e7
computed block checksum: 0x0
Reading datafile '+DATA/test//datafile/apps_ts_tx_data.295.741794537' for corruption at rdba: 0x09400001 (file 37, block 1)
Reread (file 37, block 1) found same corrupt data

Restore is been done on raw device or Asm diskgroup created using raw device

Datafile restore goes fine


Sign In with your My Oracle Support account

Don't have a My Oracle Support account? Click to get started

My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms