Duplicate Key Errors During Integration - Simultaenous Processing of Locations from Different Transmissions (Doc ID 886398.1)

Last updated on SEPTEMBER 08, 2016

Applies to:

Oracle Transportation Management - Version: 5.5.04.01 to 5.5.04.07 - Release: 5.5 to 5.5
Information in this document applies to any platform.
***Checked for relevance on 02-Jun-2011***

Symptoms

-- Problem Statement:
On 5.5.04.01, When attempting to send in an Order Release XML with multiple locations and contacts
that are attached to either the ShipFrom/ShipTo Locations and/or the Involved Party details, the
following error occurs:
When the same transmission is re-processed, the transmission gets processed
ERROR(s)
THE FOLLOWING EXCEPTION WHILE PROCESSING TRANSACTION: glog.util.remote.CreateDuplicateRecord
Cannot add the LOCATION record. LOCATION_GID must be unique.
java.sql.SQLException: ORA-00001: unique constraint (GLOGOWNER.PK_LOCATION) violated

Another error seen is a deadlock on the database as follows:
2009-07-29 08:03:45.246 21126 Error Exception java.sql.SQLException: ORA-00060: deadlock detected
while waiting for resource
java.sql.SQLException: ORA-00060: deadlock detected while waiting for resource

at oracle.jdbc.driver.DatabaseError.throwSqlException(DatabaseError.java:112)

-- Steps To Reproduce:
The issue can be reproduced at will with the following steps:
1. Process Order Release Transactions with the Locations and Contacts that are associated with the
ShipFrom/ShipTo Locations and also the Involved Parties being included in these elements itself
and not as separate transactions
2. See that occasionally, the transmission fails due to Duplicate Location or deadlock error



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