Recovering the primary database's datafile using the physical standby, and vice versa
(Doc ID 453153.1)
Last updated on APRIL 03, 2020
Applies to:Oracle Database - Enterprise Edition - Version 18.104.22.168 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.
***Checked for relevance on 16-July-2015***
How to recover the primary database's datafile using a copy of a standby database's datafile.
How to recover the standby database's datafile using a copy of a primary database's datafile.
Before replacing a datafile with a copy from either production or standby, please confirm that all archivelogs are available for full recovery of this datafile. It is also important to ensure that the source is corruption-free. Run DBV or RMAN validate to check for corruption.
a) dbv must return with zero corrupted pages
If using ASM, you need to also supply the userid for dbv:
b) rman validate:
Once RMAN is completed, this view must return zero rows:
<Note 1265884.1> 'Resolving ORA-752 or ORA-600  During Standby Recovery'
Datafiles should not be copied to a physical standby until the primary has been cleared of any corruption.
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
|Recovering the Primary's Datafile|
|Recovering the Standby's Datafile|