Icon View Incident Report

Serious Serious
Reported By: Tim Young
Reported On: 6/20/2008
For: Version 2.00 Build 2
# 2679 LOAD UPDATES Failing When Replication Data Has Passed Through More than One Publisher

The replication design has an issue where any updates that pass through more than one publisher will encounter constraint errors during the loading of the updates on the second publisher. As an example, if you have two laptops and one main office:

1) Both laptops are publishing their updates back to the main office
2) The main office is then publishing all updates back to the laptops

The problem is encountered when the following occurs:

1) The first laptop enters some data
2) The second laptop enters some data
3) The first laptop synchronizes with the main office
4) The second laptop synchronizes with the main office
5) The first laptop synchronizes with the main office again, and a constraint error occurs, most likely a duplicate key exception for the primary key

The reason for the problem is that each update only contains a manifest that includes the publisher ID of the originating publisher. It actually should contain the publisher ID for all publishers that have loaded the update also.


Comments Comments
This issue required a change in the format of the published updates in the .EDBPbl file for a published table. Therefore, it is important that you delete any existing .EDBPbl table files, and allow EDB to recreate them as empty. This will remove any existing logged updates for the table,however, so this action is only recommended for non-production systems. If you have a production system already up and running using the new replication, please contact support for more information on how to update the .EDBPbl table files without losing the existing logged updates.


Resolution Resolution
Fixed Problem on 6/24/2008 in version 2.01 build 1


Products Affected Products Affected
ElevateDB Additional Software and Utilities
ElevateDB DAC Client-Server
ElevateDB DAC Client-Server with Source
ElevateDB DAC Standard
ElevateDB DAC Standard with Source
ElevateDB DAC Trial
ElevateDB VCL Client-Server
ElevateDB VCL Client-Server with Source
ElevateDB VCL Standard
ElevateDB VCL Standard with Source
ElevateDB VCL Trial

Image