Did this article resolve your question/issue?



10.0B: Cannot start Source Database Replication Server after an PROQUIET or Online Backup

« Go Back


Title10.0B: Cannot start Source Database Replication Server after an PROQUIET or Online Backup
URL NameP92539
Article Number000141420
EnvironmentProduct: OpenEdge
Version: 10.0B
OS: All Supported platforms
Other: Replication
Question/Problem Description
Cannot start Replication Server for source database after Online Backup of the source
Cannot start Replication Server for Source database after PROQUIET issued against the source

Replication Server terminates when it connects to the Replcation Agent after a PROBKUP of the source database
Replication breaks after a PROQUIET is disabled or an online PROBKUP
Replication Agent terminates when the RPLS finds : "This database has not been properly backed up."
Steps to Reproduce1. Setup OpenEdge Replication
2. Start the source and target databases and ensure they've synchronized
3. Make some source database changes (create/delete/update)
4. Take an online backup of the source database or enable then disable PROQUIET
5. Make some source database changes (create/delete/update)
6. Shutdown the source and target databases
7. Restart both databases:
At this point the RPLS fails with error: "This database has not been properly backed up."
Clarifying Information
Error MessageThe database has not been properly backed up
The Fathom Replication Agent agent1 is being terminated. (10700)
Defect Number20040823-010 \ PSC00155737
Enhancement Number
When a source database is backed up  or a quiet point is started, the master block information is not updated unless the -REPLTargetCreation argument is used which flags flushing this replication information. As a consequence, when the RPLS connects to the RPLA this information is out of sync.

Upgrade to OpenEdge 10.0B01, 10.2A or later OpenEdge releases.

  • Anytime an online backup or quiet point is started, replication specific information in the master block is flushed before AIB and BIB latches are acquired
  • The -REPLTargetCreation argument only required when the intention is to re-base target(s).  In which case, no further RFUTIL mark backedup, PROQUIET or PROBKUP (even with -REPLTargetCreation flag) until the replication target database has been restored with this backup, started and completed synchronization or it will fail initial synchronization and the target baseline will need to be re-taken: When is the -REPLTargetCreation flag needed on PROBKUP or PROQUIET?

To immediately recover before the Service Pack can be installed:

  • When  the Replication Server fails to start in the manner described above after an online backup or proquiet was performed, the following steps can be used to get around the problem with an Enterprise Database License:

1. Stop the Target database:

$   proshut <target> -by

2. Enable then disable PROQUIET against the source database with the -REPLTargetCreation flag (**)

  • This will no longer be necessary once a fixed version is installed (**)

$   proquiet <source> enable -REPLTargetCreation
$   proquiet <source> disable

3. Restart the Target database

4. Restart the Replication Server:

$   dsrutil <source> -C restart server


In versions prior to OpenEdge 10.0B: Use the -REPLTargetCreation flag anytime a PROBKUP online or a PROQUIET is raised against a Replication Source database:

  • This argument does not add any additional processing time or overhead.

$   probkup online <source> dbname.bak -REPLTargetCreation [ -verbose -Bp 20 ]

$   proquiet
<source> enable -REPLTargetCreation
proquiet <source> disable


Last Modified Date11/25/2021 1:05 PM
Disclaimer The origins of the information on this site may be internal or external to Progress Software Corporation (“Progress”). Progress Software Corporation makes all reasonable efforts to verify this information. However, the information provided is for your information only. Progress Software Corporation makes no explicit or implied claims to the validity of this information.

Any sample code provided on this site is not supported under any Progress support program or service. The sample code is provided on an "AS IS" basis. Progress makes no warranties, express or implied, and disclaims all implied warranties including, without limitation, the implied warranties of merchantability or of fitness for a particular purpose. The entire risk arising out of the use or performance of the sample code is borne by the user. In no event shall Progress, its employees, or anyone else involved in the creation, production, or delivery of the code be liable for any damages whatsoever (including, without limitation, damages for loss of business profits, business interruption, loss of business information, or other pecuniary loss) arising out of the use of or inability to use the sample code, even if Progress has been advised of the possibility of such damages.