How to re-sync replication if one of the targets goes down in OpenEdge Replication with a 2 target scenario?

« Go Back

Information

Title	How to re-sync replication if one of the targets goes down in OpenEdge Replication with a 2 target scenario?

URL Name	000032918

Article Number	000144387

Environment	Product: OpenEdge Version: 10.x, 11.x OS: All supported platforms OpenEdge Replication

Question/Problem Description

On OpenEdge Replication with 2 targets scenario with non-critical agents, if one of the target shuts down (proshut –by) or if agent is terminated (dsrutil –C terminate agent), will the replication server source die?

How to re-sync replication if one of the targets goes down in OpenEdge Replication with a 2 target scenario?

How to recover when replication connection failure fails to recover against one agent, but continues replicating to another:

(9407) Connection failure for host <host> port <repl listening port> transport TCP.
(10697) The Fathom Replication Server was unable to reconnect to agent agent2. Recovery for this agent will not be performed
(10662) Recovery completed normally for agent agent1.

Steps to Reproduce

Clarifying Information

Error Message

Defect Number

Enhancement Number

Cause

Resolution

The replication server will not shut itself down while one of the agents is connected (and recovered).
The RPLS will continue replicating to the available agent (recoverable), mark the other agent as unrecoverable.
A running RPLS will not try to reconnect to an agent marked as unrecoverable (10697), even if this agent is restarted

But in order to reestablish the synchronization both agents and the replication server must be restarted.

1. To restart the replication Agent:

Prior to OpenEdge 11.6: shutdown and restart the target database.

$ proshut target1 -by
$ proshut target2 -by
$ proserve target1 -DBService replagent [+target database parameters]
$ proserve target2 -DBService replagent [+target database parameters]

OpenEdge 11.6 and later: if the target database is still online the agent can be stopped and restarted:

$ dsrutil <targetdb> -C terminate agent
$ dsrutil <targetdb> -C restart agent

2. To restart the replication Server:

$ dsrutil <targetdb> -C terminate server
$ dsrutil <targetdb> -C restart server

For further instruction refer to Article:

00072841, How to restart RPLS, RPLA and target database when the source database is running.

Please note that the AI extents that are full on the source database will be LOCKED until both target databases are synchronized again. If all AI extents get full and locked on the source machine (no free available AI extent available) then the source database will shutdown. For further information on adding additional AI areas to the database, refer to Article:

All after imaging (AI) areas are in LOCKED state after network failure

Workaround

Notes

Keyword Phrase

Last Modified Date	11/20/2020 7:01 AM