Due to Network Issues on Oracle Point of Service(POS), the Same Transaction is Being Resent to Central Office Which is Failing With Unique Constraint Error
Last updated on JUNE 23, 2017
Applies to:Oracle Retail Point-of-Service - Version 13.3 to 14.0 [Release 13.3 to 14.0]
Information in this document applies to any platform.
On Oracle Retail Point Of Service (ORPOS), due to network issues, the same transaction is resent to Oracle Retail Central Office(ORCO) which is failing with unique constraint.
After sending the transaction to JMS queue, ID_TLOG_BTCH is not updated due to the network errors and the same transaction is picked again for sending which is causing unique constraint errors at CO.
The below exception appears in the POS logs:
Steps To Recreate:
This issue might occur due to network fluctuations wherein the transaction has been posted to the queue but the column ID_TLOG_BTCH on TR_TRN table is not updated with the appropriate value to mark that the transaction has been posted to ORCO.
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