My Oracle Support Banner

Block Corruption (ALL ZERO) detected after reclaiming space on Veritas Filesystem (Doc ID 1587427.1)

Last updated on JULY 29, 2019

Applies to:

Oracle Database - Enterprise Edition - Version 8.1.7.0 and later
Oracle Database Cloud Schema Service - Version N/A and later
Oracle Database Exadata Cloud Machine - Version N/A and later
Oracle Database Exadata Express Cloud Service - Version N/A and later
Oracle Cloud Infrastructure - Database Service - Version N/A and later
Information in this document applies to any platform.

Symptoms

 RDBMS is reporting corrupted blocks with Zeroes after the underlying diskspace has been 'reclaimed'.  Example from RMAN validate:

Hex dump of (file 15, block 783824) in trace file /<Path>/trace/<SID>_ora_12515.trc
Corrupt block relative dba: 0x03cbf5d0 (file 15, block 783824)
Completely zero block found during validation
Reread of blocknum=783824, file=/<Path>/<datafile>.dbf. found same corrupt data
Reread of blocknum=783824, file=/<Path>/<datafile>.dbf. found same corrupt data
Reread of blocknum=783824, file=/<Path>/<datafile>.dbf. found same corrupt data
Reread of blocknum=783824, file=/<Path>/<datafile>.dbf. found same corrupt data
Reread of blocknum=783824, file=/<Path>/<datafile>.dbf. found same corrupt data

 

 This may also produce ORA-1578 or ORA-8103 if the corrupt block is read by a SQL statement.

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
Cause
Solution
References


My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.