"glog.util.remote.CreateDuplicateRecord" Exception When Manually Calculating NEXT Sequence Number (Doc ID 1061393.1)

Last updated on JULY 09, 2014

Applies to:

Oracle Transportation Management - Version: 5.5 - Release: 5.5
Information in this document applies to any platform.

Symptoms



NOTE: The following focuses on a specific example using SHIPMENT_COST Sequence Number, but this note applies for any table that includes a Sequence.


A SHIPMENT_COST record is being manually being inserted into the DB via a DIRECT SQL UPDATE action. This is inserting a cost into a different shipment than the one triggering the agent. When a "Change Service Provider" action is then used on a shipment, upon updating the costs, it is failing with the following Exception:

Error creating SHIPMENT_COST for ShipmentCostData: shipmentCostSeqno: null shipmentGid: DOMAIN.SHIPMENT_ID costType: B cost: 100000.0 USD accessorialCodeGid: null accessorialCostGid: null rateGeoCostGroupGid: DOMAIN.RATE_RECORD rateGeoCostSeq: 1991033 specialServiceGid: null isCostFixed: false processAsFlowThru: false adjustmentReasonGid: null generalLedgerGid: null paymentMethodCodeGid: null exchangeRateDate: null exchangeRateGid: DEFAULT domainName: DOMAIN

The SHIPMENT_COST 7165999554 cannot be created because a duplicate already exists

glog.util.remote.CreateDuplicateRecord
Cannot add the SHIPMENT_COST record. SHIPMENT_COST_SEQNO must be unique.
java.sql.SQLException: ORA-00001: unique constraint (GLOGOWNER.PK_SHIPMENT_COST) violated

The Sequence identified in the error is the one that was manually inserted into the Database via the Agent Action. It seems that the NEXT Sequence ID is not being used, and the manual one is being reused.

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