TR_TRN.ID_TLOG_BTCH Column of Some Transactions is Reset to -1 and Resent to Central Office; 'ORA-00001: Unique Constraint Violated' Errors Result
Last updated on JANUARY 12, 2018
Applies to:Oracle Retail Central Office - Version 13.0 to 13.4.7 [Release 13.0 to 13.4]
Oracle Retail Point-of-Service - Version 13.0 to 13.4 [Release 13.0 to 13.4]
Oracle Retail Back Office - Version 13.0 to 13.4.7 [Release 13.0 to 13.4]
Information in this document applies to any platform.
Transactions previously replicated to Central Office are being resent inappropriately, causing current replication batch failure and missing transactions. Transactions are resent as the tlog batch ID is reset to -1. This leads to unique constraint violation errors, and the persistence of the entire batch of transactions fails. This results in a mismatch between transactions in Back Office at the store level and Central Office.
1. Postprocessor is scheduled to run every 15 minutes.
Steps to Reproduce:
1. Ring an item and tender to complete the transaction.
2. The transaction is saved to the store level/Back Office database.
Note that in some cases, the tlog batch ID is reset to -1 due to simultaneous execution of postprocessor. The following error occurs in the Central Office log:
Sign In with your My Oracle Support account
Don't have a My Oracle Support account? Click to get started
My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms