After Flashback both Primary and Standby, Standby recovery report "Recovery completed through change"
(Doc ID 1969169.1)
Last updated on FEBRUARY 02, 2022
Applies to:Oracle Database - Enterprise Edition - Version 126.96.36.199 and later
Oracle Database Cloud Schema Service - Version N/A and later
Oracle Database Exadata Express Cloud Service - Version N/A and later
Gen 1 Exadata Cloud at Customer (Oracle Exadata Database Cloud Machine) - Version N/A and later
Oracle Database Cloud Exadata Service - Version N/A and later
Information in this document applies to any platform.
NOTE: In the images and/or the document content below, the user information and environment data used represents fictitious data
from the Oracle sample schema(s), Public Documentation delivered with an Oracle database product or other training material.
Any similarity to actual environments, actual persons, living or dead, is purely coincidental and not intended in any manner.
For the purposes of this document, the following fictitious environment is used as an example to describe the procedure:
Standby database db_unique_name : prod_stby
Diskgroups used :- DB_FLASH_ADV and DB_DATA_ADV
After flashback both Primary and Standby database to the same scn, the primary starts with open resetlogs. Restart the standby recovery, the standby recovery does not applying the new archive logs from the primary resetlogs point. It either reports:
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