Kbase P121558: Unable to Re-enable Fathom Replication after Transition using Fathom Replication 3.0A/10.0B
| Autor |
Progress Software Corporation - Progress |
| Acesso |
Público |
| Publicação |
05/05/2008 |
|
Status: Verified
FACT(s) (Environment):
Fathom High Availability Replication 3.0A
Fathom High Availability Replication 10.0B
OpenEdge 10.0B
Progress 9.1E
All Supported Operating Systems
SYMPTOM(s):
Unable to Re-enable Fathom Replication after Transition
Either the Fathom Replication Agent <agentname> has been incorrectly configured or the target database <databasename> has been improperly sourced. (10440)
The CRITICAL Agent <agent-name> cannot be configured. The Fathom Replication Server is terminating. (11694)
The Fathom Replication Agent <agent-name> is being terminated. (10700)
CAUSE:
Bug# OE00136043
CAUSE:
The instructions in 3.0A Progress Fathom Replication Users Guide "Re-enabling Fathom Replication after Transition". (2-45) are incorrect.
The OpenEdge 10.1A code base implements enhancements to the Fathom Replication with failback replication where it is possible to eventually restore the originating replication between two servers with only one probkup transfer. Please refer to the 3.1A OpenEdge Replication Users Guide for further details.
FIX:
The correct steps are:
After target has successfully been transitioned:
$ dsrutil target -C transition agent
Take an OFFLINE probkup of the transitioned target database to use for the
re-creation of the replication enabled source database.
[Source machine]
del *.recovery
check the source.st is good and includes ai extents
check the source.repl.properties are in the same directory as the source.db
prorest source targetOFFL.bak
rfutil source -C mark backedup
rfutil source -C aimage begin
proutil source -C enablesitereplication source
>> Replication (source) is now enabled for database source. (10351)
Start the (new) source database:
proserve source {params} -DBService replserv
probkup online source source_b -REPLTargetCreation
Use this online backup (source_b) to create target database again.
** make sure the *.recovery file has been removed before restoring the target **
proutil target -C enablesitereplication target
proserve target {params} -DBService replagent