Redo Log Corruption While Using Netapps Filesystem With Default Setting of Filesystemio_options Parameter
(Doc ID 437005.1)
Last updated on FEBRUARY 03, 2019
Applies to:Oracle Server - Enterprise Edition - Version 10.2.0.2 and later
Information in this document applies to any platform.
***Checked for relevance on 09-Aug-2011***
Seeing Redo log corruption errors while running streams using netapps file system.The filesystemio_options is set to default value of "none" in the database.
ALTER SYSTEM DUMP LOGFILE '/cabbage02/oradata/dwhse10/redo05_d.log'
ERROR at line 1:
ORA-00354: corrupt redo log block header
ORA-00353: log corruption near block 535496 change 32855751261 time 01/07/2007
ORA-00334: archived log: '/cabbage02/oradata/dwhse10/redo05_d.log'
The Redo Log Files get corrupted and halts the Database on the check point. The block dumps of corrupted log member contains images from the previous log sequence#.
Redo logs on NetApp storage using nfs with intense I/O (ie Streams activity) precipitates the corruption when NOT using directio.Other filestorage systems similar to NetApp have not been tested, however it is anticipated that the same behavior would be seen if the storage uses nfs.
With redo on local drives or low intensity I/O, the corruption does not reproduce.
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
|This document is being delivered to you via Oracle Support's Rapid Visibility (RaV) process and therefore has not been subject to an independent technical review.|