Last updated on APRIL 19, 2017
Applies to:Oracle Database - Enterprise Edition - Version 184.108.40.206 and later
Information in this document applies to any platform.
Primary aborted, preferred Far sync aborted, startup mount of old Primary, NO
automatic reinstatement, manual reinstate fails, enable database fails.
There were NO application transactions.
During the initial attempt to reinstate, it appears that we failed to
successfully establish the redo route from the new primary. The preferred
Far Sync was down.After failover, the automatic reinstate should occur with
only the alternate Far Sync up.
Although in a simpler configuration, with only one Far Sync, startup mount was enough
for DG to initiate automatic reinstate.
Why must we re-create rather than reinstate?
Sign In with your My Oracle Support account
Don't have a My Oracle Support account? Click to get started
Million Knowledge Articles and hundreds of Community platforms