Set as converted Controlfile due to db_unique_name Mismatch Message in the ALERT.LOG after Rebuilding Standby Controlfile on Physical Standby
(Doc ID 1530140.1)
Last updated on APRIL 03, 2020
Applies to:Oracle Database - Enterprise Edition - Version 220.127.116.11 and later
Oracle Database Exadata Cloud Machine - Version N/A and later
Oracle Cloud Infrastructure - Database Service - Version N/A and later
Oracle Database Exadata Express Cloud Service - Version N/A and later
Oracle Database Cloud Exadata Service - Version N/A and later
Information in this document applies to any platform.
For the purposes of this document, the following fictitious environment is used as an example to describe the procedure:
Why are the following Messages in the Physical Standby Database ALERT.LOG ?
"Changing di2dbun from SITSDBA to SITSDBA_STBY"
Prior to seeing these Messages, Managed Recovery was stopped, and the Standby Controlfile was recreated from the Primary. The Standby was then mounted with the new Standby Controlfile.
Once Managed Recovery was started, the Messages appeared in the ALERT.LOG.
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