Transactions Are Missing in TR_TRN Table After 'ORA-00001: Unique Constraint' Error for Two Different Transactions (Doc ID 2053512.1)

Last updated on JUNE 23, 2017

Applies to:

Oracle Retail Point-of-Service - Version 13.4.8 and later
Information in this document applies to any platform.

Symptoms

Two different transactions have the same transaction number, causing an ORA-00001: 'Unique Constraint Violated' error.


Steps to Reproduce:

  1. Log in to ORPOS
  2. Perform transactions in offline mode
  3. Check QueueException folder

Cause

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