ORA-1578 ORA-353 ORA-19599 Corrupt blocks with zeros when filesystemio_options=SETALL on ext4 file system using Linux
Last updated on AUGUST 16, 2017
Applies to:Oracle Database - Enterprise Edition - Version 10.1.0.2 to 188.8.131.52 [Release 10.1 to 12.1]
Permanent or transient corruptions with zeroed out blocks when using ext4 file system on Linux (i.e. Redhat RHEL 5 and RHEL6 , Oracle Linux OEL5,OEL6) and the database parameter filesystemio_options is defined to SETALL. It produces different corruption errors for datafiles, redo log files, etc. Examples:
ORA-1578 reporting corruption in database files. The alert log or trace file describe the corruption as a zeroed out block:
Completely zero block found during multiblock buffer read
Reading datafile '/u07/oradata/temp.dbf' for corruption at rdba: 0x01bcbbe0 (file 214, block 3980256)
A reread may or may not find VALID data.
ORA-368 / ORA-353 while reading redo/archived log files. The next errors may be produced during recovery when reading a corrupt zeroed out redo log block:
ORA-00368: checksum error in redo log block
ORA-00353: log corruption near block 2515 change 1525478329224 time 10/15/2012 22:00:00
ORA-00334: archived log: '/arch/1_3068_670411.dbf'
ORA-19599 by RMAN backing up archived logs. This may also affect other files like redo log files
; the alert log shows a message like:
Bad header found during backing up archived log
Data in bad block - seq:0. bno:0. time:0
calculated check value: 0
Database files on ext4 File System on Linux and Database parameter filesystemio_options is set to SETALL.
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