My Oracle Support Banner

FAR SYNC Reported ORA-16477 and Stopped Sending Redo to Standby databases After the Restart. (Doc ID 2810665.1)

Last updated on APRIL 17, 2023

Applies to:

Oracle Database - Enterprise Edition - Version to [Release 19]
Oracle Database - Enterprise Edition - Version to [Release 18]
Oracle Database - Enterprise Edition - Version to [Release 12.1 to 12.2]
Information in this document applies to any platform.


In 19c Data Guard Broker Configuaration, Primary-farsync-2 ADG database setup, When farsync is restarted, logs are not shipping from farsync to standby and, the destination shows error: ORA-16477: destination is being serviced by another viable source.

1. When FarSync is stopped, log shipping from primary to standby works as expected.
2. When FarSync is restarted, FarSync rejoins the topology. The primary recognizes it and sends redo to the FarSync.
    The FarSync does not forward logs to the standby. The FarSync reports that the standby databases are serviced by another database. The standby databases do not receive logs.
3. The ORA-16477 is reported on the FarSync, not the standby.
4. (Re)enabling the standby destination state on the FarSync causes FarSync to send logs to the standby; and clears the ORA-16477, but only for the single destination.
    If there are multiple standby databases serviced by FarSync, this operation ("nudging" the log_archive_dest_n or log_archive_dest_state_n parameters) has to be performed for each destination.
When FarSync rejoins topology need to re-enable log_Archive_dest_2 for standby even though it is Enable mode.

or gets an error:





 Unable to ship the redo via FarSync, after Farsync restarts.


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

My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.