After configuring Data Guard using Broker, parameter log_archive_config shows different values on Primary And Standby
(Doc ID 2406377.1)
Last updated on JANUARY 17, 2023
Applies to:
Oracle Database Cloud Schema Service - Version N/A and laterOracle 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 Backup Service - Version N/A and later
Information in this document applies to any platform.
Symptoms
Parameter log_archive_config is set and shows the correct values on primary and standby:
Example:
SQL> show parameter log_archive_config
NAME TYPE VALUE
------------------------------------ -----------
log_archive_config string dg_config=(<primary_unique_name>,<standby_unique_name>)
After the Broker gets configured, log_archive_config should be set on both primary and standby.
However, the Broker does not configure the Standby's log_archive_config correctly.
Example on Primary:
SQL> show parameter log_archive_config
NAME TYPE VALUE
------------------------------------ -----------
log_archive_config string dg_config=(<primary_unique_name>,<standby_unique_name>)
Example on Standby:
SQL> show parameter log_archive_config
NAME TYPE VALUE
------------------------------------ -----------
log_archive_config string dg_config=(<db_unique_name>)
Changes
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 |
| References |