Error Cannot Add MONITOR_AGENT record, MONITOR_AGENT_GID Must Be Unique When Scalability Is Switched On. (Doc ID 563186.1)

Last updated on JULY 09, 2014

Applies to:

Oracle Transportation Management - Version 5.5 and later
Information in this document applies to any platform.
Checked for relevance on 23-Apr-2010


Symptoms

-- Problem Statement:

On 5.5 in Production:

When attempting to Bulk Plan Order in a system that is configured with Scalability, OTM cannot Add MONITOR_AGENT record and  MONITOR_AGENT_GID  and an error is seen stating that both must be unique.

The logs contain the following error:


ERROR
281216 Error Exception Cannot add the MONITOR_AGENT record. MONITOR_AGENT_GID must be unique.
java.sql.SQLException: ORA-00001: unique constraint (GLOGOWNER.PK_MONITOR_AGENT) violated

NOTE: This is also seen with other Agents and with some Shipment IDs when the log is investigated.

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