The following is the cause of this error:
Client tried to repush a transaction has already been committed at the master site. A common cause of this problem is an error at the local site in initializing or updating the local site transaction sequence mechanism.
Action you can take to resolve this issue: Verify that transaction data that RepAPI was attempting to repushed to the master site exists at the master table and is valid and consistent with the local site. If this error occurs, redundantly identified transactions are ignored and then purged from the local updatable materialized view logs. Check that the local site is correctly assigning new transaction IDs and is not accidently generating non-unique values.
Tags: Database, Microsoft, Oracle, SQL, Software, DBMS, Error Messages, Directory
Disclaimer:Pak/ed and the contributors are not responsible for any errors contained and are not liable for any damages resulting from the use of this material. Disclaimer
Home Disclaimer Advertise Contact Privacy Policy
Copyright © 2004-16 Paked.com. All rights reserved.
Note: Site best viewed at 1024 x 768 or higher screen resolution