Kbase P158269: Ai files on source database are locked and busy, restarting of target database results in error (105
| Autor |
Progress Software Corporation - Progress |
| Acesso |
Público |
| Publicação |
5/18/2011 |
|
Status: Unverified
SYMPTOM(s):
Ai files on source database are locked and busy, restarting of target database results in error (10506) The Fathom Replication Agent is ending.
(10506) The Fathom Replication Agent is ending.
(11251) The Replication Server successfully connected to all of it's configured Agents.
(11703) It appears the Target Database has been restored since the last time Replication was run. Replication to this Agent cannot continue.
(10440) Either the Fathom Replication Agent has been incorrectly configured or the target database has been improperly sourced.
(11696) The Agent cannot be properly configured and is being terminated.
(10700) The Fathom Replication Agent is being terminated.
(10504) Unexpected error -129 returned to function rpSRV_ServerLoop.
(10505) The Fathom Replication Server is ending.
FACT(s) (Environment):
All Supported Operating Systems
OpenEdge 10.1B
OpenEdge 10.1C
OpenEdge 10.2x
CAUSE:
When source database was down, the following command was run which reset the Recovery.properties file pointers and in-validated the target database.
probkup <source-dbname> <device> -REPLTargetCreation
FIX:
The following steps may be used to re-enable replication on the source database and create a new target database without bringing the production database down to enable replication.
1. disable sitereplication:
dsrutil <dbname> -C disablesitereplication source
2. Backup ai files ( still applicable with previous backup)
OS COPY IS FINE
3. rfutil to empty ai files
rfutil <dbname> -C aimage extent empty
4. proutil <dbname> -C enableSiteReplication source
5. probkup online <dbname> <device-name> -REPLTargetCreation
6. Before you can restore over the old target database, you must disable sitereplication:
proutil <dbname> -C disablesitereplication target
7. Restore Target database
prorest <target-dbname> <device-file-name>
There will be a message:
"Database already exists.
Do you want to over write it? [y
]:
Response must be "y" to establish the new target database.
8. Enable replication for the new target database
proutil <dbname> -C enableSiteReplication target
9. Start the target database and agent
proserve <dbname> -DBService replagent -S 4501 ( or port which is is being used for replagent)
10. ReStart Replication server on source database if it has stopped:
dsrutil <dbname> -C restart server