After configuring Data Guard using Broker, parameter log_archive_config shows different values on Primary And Standby

(Doc ID 2406377.1)

Last updated on MAY 31, 2018

Applies to:

Oracle Database - Enterprise Edition - Version 12.1.0.2 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> sho parameter log_archive_config

NAME TYPE VALUE
------------------------------------ -----------
log_archive_config string dg_config=(test2,test2_servb)

 

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> sho parameter log_archive_config


NAME TYPE VALUE
------------------------------------ -----------
log_archive_config string dg_config=(test2,test2_servb)

 

Example on Standby:


SQL> sho parameter log_archive_config


NAME TYPE VALUE
------------------------------------ -----------
log_archive_config string dg_config=(test2)

Cause

Sign In with your My Oracle Support account

Don't have a My Oracle Support account? Click to get started

My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms