Even When The Far Sync Instance Stops, Log_archive_dest_state_n For Standby Is Not Enabled.

(Doc ID 2007563.1)

Last updated on MAY 12, 2015

Applies to:

Oracle Database - Enterprise Edition - Version and later
Information in this document applies to any platform.


 A physical standby configuration including far sync instance


The environment is as follows:

When the next conditions are met, Data Guard Broker sets the status of log_archive_dest_n
for Standby Database as "ALTRENATE", not "VALID".

 - Data Guard Broker is used.(dg_broker_start=true)
 - Far synce instance is stopped gracefully. (shutdown immediate)

By the influence, you do not get synchronization with Primary Database and Standby Database.


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