Oracle Database / Data Guard & High Availability
ORA-16047: compare Data Guard database identity settings
Redo transport can reject a destination when database identity does not match the expected configuration. Compare unique names rather than editing credentials first.
Environment and inputs: Oracle Database 19c baseline · SQL*Plus-compatible SQL unless RMAN, DGMGRL, ADRCI or a host shell is specified. Check release, patch level, edition and container first.
Start with this diagnostic
Use the stated SQL, RMAN, DGMGRL or host shell and replace sample names with approved targets. DBA and V$ views need authorized catalog access in the correct container. Do not grant broad privileges for an example.
SELECT name, value FROM v$parameter WHERE name IN ('db_unique_name','log_archive_config');Read the result
The parameters describe this database's identity and configured Data Guard membership. Compare them with the intended remote member and destination settings.
Resolve and verify
Have the Data Guard owner reconcile the exact DB_UNIQUE_NAME and destination configuration on both sides. Validate transport after the managed change.
Operational precautions
Do not rename or repoint a standby based solely on its host name; database and host identities are different.