Broker overrides local LOG_ARCHIVE_DEST_n destination on Bystander Standby

(Doc ID 1364467.1)

Last updated on SEPTEMBER 06, 2017

Applies to:

Oracle Database - Enterprise Edition - Version 11.2.0.1 to 11.2.0.3 [Release 11.2]
Information in this document applies to any platform.

Symptoms

After switchover using Data Guard Broker DGMGRL or Grid Control between Primary A and Standby Target B, the LOG_ARCHIVE_DEST_n defined on a Bystander Standby C for local archival is changed.


Example:
  Primary A
  Physical Standby Target B
  Physical Standby Bystander C
   (Real Application Cluster/Clusterware may be configured but is not a factor)

All three start off configured with LOG_ARCHIVE_DEST_1 like so:

  log_archive_dest_1 = 'location=/u01/arch/  valid_for=(all_logfiles,all_roles) db_unique_name=<DB_UNIQUE_NAME set for database>'

After switchover between Primary A and Standby B, LOG_ARCHIVE_DEST_1 on Bystander Standby C will be reset like so:

  log_archive_dest_1='location=USE_DB_RECOVERY_FILE_DEST','valid_for=(ALL_LOGFILES, ALL_ROLES)'

With another LOG_ARCHIVE_DEST_n also being defined as:

  log_archive_dest_2='location="/u01/arch/"','valid_for=(STANDBY_LOGFILE,STANDBY_ROLE)'



The Broker log on the new Primary B after switchover may show changes were attempted there too but failed:

Executing SQL [alter system set log_archive_dest_1='']
SQL Execution error=604, sql=[alter system set log_archive_dest_1=''].
See error stack below.
ORA-00604: error occurred at recursive SQL level 1
ORA-02097: parameter cannot be modified because specified value is invalid
ORA-16028: new LOG_ARCHIVE_DEST_1 causes less destinations than
LOG_ARCHIVE_MIN_SUCCEED_DEST requires

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