Kbase P103738: Replication fails to intialise, error 11703 on Source database
| Autor |
Progress Software Corporation - Progress |
| Acesso |
Público |
| Publicação |
4/14/2009 |
|
Status: Verified
SYMPTOM(s):
replication agent keeps ends immediately after communication with source is established
replication will not start.
replication agent keeps ending with 10506
The Fathom Replication Agent <agent-name> is ending. (10506)
Error 11703 in log file of source database
It appears the Target Database <database-name> has been restored since the last time Replication was run. Replication to this Agent <agent-name> cannot continue. (11703)
Either the Fathom Replication Agent <agentname> has been incorrectly configured or the target database <databasename> has been improperly sourced. (10440)
The Agent <agent-name> cannot be properly configured and is being terminated. (11696)
The Fathom Replication Agent <agent-name> is being terminated. (10700)
Target created from restore of online backup of source
Backup of source created with probkup online <source> <backup-file> -REPLTargetCreation
FACT(s) (Environment):
OpenEdge Replication 10.x
Fathom Replication 3.0A
All Supported Operating Systems
Fathom Replication
CAUSE:
The <database-name>.repl.recovery files were not removed prior to restoring backup and restarting replication.
FIX:
Before restoring the backup and restarting replication, ensure the *.repl.recovery files have been removed for both source and target .
To recover the situation:
1. ensure that the replication server is not running:
- parse source.lg file for message 10505
The Fathom Replication Server is ending. (10505)
- run the dsrutil source -C status
1199 means it has ended.
- or just run: dsrutil source -C terminate server
NOTE: Please refer to the Replication Users Guide as the return code varies between versions.
2. Stop the target database gracefully
$ proshut target -by
3. delete the <source>.repl.recovery and <target>.repl.recovery files respectively
4. start the target database
$ proserve target [+parameters] -DBService replagent
5. re-start the replication server
$ dsrutil source -C restart server
The following outline of steps should have initially been done when re-establishing the replication enabled target database:
[source]
probkup online source source_bak -REPLTargetCreation
It's important that NO (none, zero) probkups or rfutil -C mark backedup occur between the time you take this bakcup and the time the RPLA and RPLS have touched base. With remote targets, consider increasing the "defer-agent-startup=1440" in the source.repl.properties for 'just in case' there are unexpected further delays in target creation.
delete *.recovery (for both source and target)
[target]
prorest target source_bak
proutil target -C enablesitereplication target
proserve target [+parameters] -DBService replagent
[source]
dsrutil source -C restart server