My Oracle Support Banner

ORA-1578 ORA-354 ORA-600 [3020] Misplaced blocks by Symantec / Veritas after adding LUN (Doc ID 1323532.1)

Last updated on MARCH 05, 2019

Applies to:

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

Symptoms

ORA-1578 / ORA-354 or ORA-600 [3020] during recovery due to misplaced blocks after adding a LUN by Symantec / Veritas.  A misplaced block means that a block content was written in a different location (different file or different block) overwriting the original block.  The corruption is reported in the alert log and by dbverify with message "Bad header found":


This could also cause a missing write in the original block were the IO was intended to go to in the first place (rfile#=10 in our example above) for which it may be needed to restore the original file and apply media recovery; although this block is not corrupt but has stale/old data.  The recovery of this block may not fix the stale version if the block is modified after the miss write happened producing ORA-600 [3020]

Changes

A new LUN has been added with PERSISTENCE set to NO while the Oracle database is OPEN.

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


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