DBVerify Reports Blocks as 'influx - most likely media corrupt'
(Doc ID 468995.1)
Last updated on JANUARY 30, 2022
Applies to:
Oracle Database - Enterprise Edition - Version 7.3.4.0 and laterInformation in this document applies to any platform.
NOTE: In the images and/or the document content below, the user information and data used represents fictitious data .Any similarity to actual persons, living or dead, is purely coincidental and not intended in any manner.
Symptoms
When using DBVerify (DBV) to check for data block corruptions in an open database, dbv intermittently reports blocks as being 'influx - most likely media corrupt', e.g.:
Page 38832 is influx - most likely media corrupt
***
Corrupt block relative dba: 0x058097b0 (file 22, block 38832)
Fractured block found during dbv:
Data in bad block -
type: 6 format: 2 rdba: 0x058097b0
last change scn: 0x0000.52fb2cae seq: 0x1 flg: 0x04
consistency value in tail: 0x490c0601
check value in block header: 0xd19f, computed block checksum: 0xbc49
spare1: 0x0, spare2: 0x0, spare3: 0x0
***
***
Corrupt block relative dba: 0x058097b0 (file 22, block 38832)
Fractured block found during dbv:
Data in bad block -
type: 6 format: 2 rdba: 0x058097b0
last change scn: 0x0000.52fb2cae seq: 0x1 flg: 0x04
consistency value in tail: 0x490c0601
check value in block header: 0xd19f, computed block checksum: 0xbc49
spare1: 0x0, spare2: 0x0, spare3: 0x0
***
Changes
DBVerify reports the corruptions only when used against an open (in use) database.
Cause
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
| Symptoms |
| Changes |
| Cause |
| Solution |
| References |