BLOCKRECOVER fails with ORA-00600 [kcvhvdf_1] despite all backups available
(Doc ID 1339930.1)
Last updated on JANUARY 30, 2022
Applies to:Oracle Database - Enterprise Edition - Version 10.2.0.1 and later
Information in this document applies to any platform.
RMAN BLOCKRECOVER command is run after identifying the corrupted block's file number and block number, e.g.
RMAN> BLOCKRECOVER DATAFILE 32 BLOCK 17145 ;
However it fails with following error. All the backups are available.
RMAN-03002: failure of blockrecover command at 07/20/2011 07:59:36
ORA-00283: recovery session canceled due to errors
ORA-00600: internal error code, arguments: [kcvhvdf_1], , , , , , , 
Block corruption is reported during various activities, e.g. :
RMAN> BACKUP INCREMENTAL FROM SCN xxxx DATABASE ;
fails with :
ORA-19566: exceeded limit of 0 corrupt blocks for file /<path>/<datafile name>.dbf
continuing other job steps, job failed will not be re-run
channel ORA_DISK_2: finished piece 1 at 20-JUL-11
2) BACKUP VALIDATE reports corruption :
RMAN> BACKUP BLOCKS ALL VALIDATE CHECK LOGICAL DATABASE ;
when finished, run following query to see corrupted blocks:
SQL> SELECT * FROM V$DATABASE_BLOCK_CORRUPTION ;
FILE# BLOCK# BLOCKS CORRUPTION_CHANGE# CORRUPTIO
---------- ----------- ---------- --------------------- ---------
32 17145 1 0 FRACTURED
3) DBV reports corruption :
DBVERIFY - Verification starting : FILE = /<path>/<datafile name>.dbf
Page 17145 is influx - most likely media corrupt
Corrupt block relative dba: 0x080042f9 (file 32, block 17145)
Fractured block found during dbv:
Data in bad block:
type: 6 format: 2 rdba: 0x080042f9
last change scn: 0x056f.56ee1f31 seq: 0x2 flg: 0x04
spare1: 0x0 spare2: 0x0 spare3: 0x0
consistency value in tail: 0x33bd0601
check value in block header: 0xe69f
computed block checksum: 0xec5f
To view full details, sign in with your My Oracle Support account.
Don't have a My Oracle Support account? Click to get started!
In this Document