We use replication 4 remote places in Greenland
to maintain up-to-date central copies of the de-central databases. The 4
sites have thin and apparently also unstable lines to Nuuk where
central copies resides.
Every week or so one of the replications hangs
whith an error like:
Error 7200: AQE Error: State =
HY000; NativeError = 7057; [Extended Systems][Advantage
SQL][ASA] Error 7057: The record update failed. The key value
produced from this record was not unique, and an index for the current table has
the UNIQUE property. The key value supplied for AESOPERATIONLOG:ID is not
Subscription=central_backup_sub, Table=AESOPERATIONLOG, Record=67302, SQL=INSERT
INTO "AESOPERATIONLOG" ("ID", "DATETIME", "USER_NAME", "APP_NAME", "TABLE_NAME",
"OPERATION", "KEY1", "KEY1_VALUE", "__CLIENTID", "ADD_INFO") VALUES ( ?, ?, ?,
?, ?, ?, ?, ?, ?, ? )
When at the receiver end I open the
table AESOPERATIONLOG with the architect there is no recod with the
offending recordID and a "delete from AESOPERATIONLOG where ID=67302"
succedes with 0 affected records.
If, however, I try to insert a record with that
ID I receive an error about violating a uniqueness constraint.
So the record is not there but still it IS there "a
The only way I have found arround the problem is
1) Break the replication connection by
supplying wrong credentials at the sender side (just to make
2) Modify the table properties by altering the key from autoinc to integer (or
vice versa) - then I can insert a record with the "forbidden" key value and
delete it again
3) Reverse the modification of the table
4) Restore the replication
connection by supplying the rigth
5) Possibly repeating 1-4 on an other table in case
the replikation record was part of a replikation transaktion
Is there something I should do different to avoid
the errors or easen the repair?
Software Danmark A/S