The Replication Agent transaction log is implemented using database objects (tables, stored procedures, and triggers) in the primary Informix database. Because of this and the way the Informix database handles transactions internally, there is some risk that transactions may not be applied to a replicate table in the same order they were applied to the primary table.
For example, if transaction B commits during the time lapse between the last data change operation and the commit for transaction A, Sybase Replication Agent presents the transactions to the primary Replication Server with the order AB, when the actual commit order was BA.
To avoid this situation, you can do one of the following:
Ensure that commits are performed immediately after the last data-changing operation in a transaction.
Perform a dummy data-altering operation to a marked table just before committing a transaction.
| Copyright © 2005. Sybase Inc. All rights reserved. |
|
|
