My Oracle Support Banner

MESSAGES.EDI_TRACKING_ID Field Has Stopped Getting Populated In Argus Tables (Doc ID 2381613.1)

Last updated on JULY 17, 2018

Applies to:

Oracle Argus Safety - Version 7.0.2 and later
Information in this document applies to any platform.

Symptoms

Starting on a specific date the MESSAGES.EDI_TRACKING_ID field is no longer getting populated.
All was fine prior to that date.

The MESSAGEEVENTSNAPSHOTS and RELSYSARGUS tables are populated with COREID as expected.

ESM_StatusCheck_xxx.txt log file from specified date does not have any relevant error.

Latest ESM_StatusCheck_xxx.txt log file with Debug enables does not have any relevant errors related to this

Changes

 

Cause

To view full details, 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 a vibrant support community of peers and Oracle experts.