DG Broker reports "ORA-16642: DB_UNIQUE_NAME mismatch"
(Doc ID 2764417.1)
Last updated on JULY 20, 2024
Applies to:
Oracle Database - Enterprise Edition - Version 12.2.0.1 and laterInformation in this document applies to any platform.
Symptoms
We have below fictitious environment to portray this issue.
Primary : prmy (Host Name : prmy_host.orcl.com)
Standby : stby (Host Name : stby_host.orcl.com
DG Broker reports "ORA-16642: DB_UNIQUE_NAME mismatch", though Log Transport and Apply have no issues.
DGMGRL> show configuration
Configuration - ORCL
Protection Mode: MaxPerformance
Members:
PRMY - Primary database
Error: ORA-16642: DB_UNIQUE_NAME mismatch <<++++
STBY - Physical standby database
Fast-Start Failover: DISABLED
Configuration Status:
ERROR (status updated 0 seconds ago)
Changes
New Configuration
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 |