My Oracle Support Banner

Database corruption due to lost write while using EMC DATAMOVER (Doc ID 1905184.1)

Last updated on AUGUST 01, 2019

Applies to:

Oracle Database - Enterprise Edition - Version to [Release 11.1 to 12.1]
Oracle Database Cloud Schema Service - Version N/A and later
Oracle Database Exadata Express Cloud 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
Information in this document applies to any platform.


Database corruption caused by stale/old blocks in the Oracle Database. Lost writes to database files, control files using EMC DATAMOVER file systems.


EMC with SRDF/A (Remote replication)

The Oracle Database may produce different errors or wrong results pointing to lost IO or reading a stale/old version of a block:




 ASYNC option is enabled at DATAMOVER filesystem.

Example : $ server_param server_2 -facility file -modify asyncUncachedOpt -value 1


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

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