Even When The Far Sync Instance Stops, Log_archive_dest_state_n For Standby Is Not Enabled.
(Doc ID 2007563.1)
Last updated on MARCH 10, 2019
Applies to:
Oracle Database - Enterprise Edition - Version 12.1.0.1 and laterOracle Database Cloud Schema Service - Version N/A and later
Oracle Database Exadata Cloud Machine - Version N/A and later
Oracle Cloud Infrastructure - Database Service - Version N/A and later
Oracle Database Backup Service - Version N/A and later
Information in this document applies to any platform.
Symptoms
A physical standby configuration including far sync instance
Example:
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.
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 |
| Cause |
| Solution |
| References |