'unique constraint (PK_EXP_TXT) violated' Signaled Or Random Hanging Of ODI Scenarios At Runtime (Doc ID 603109.1)

Last updated on JUNE 16, 2022

Applies to:

Purpose

The purpose of this Note is to resolve the situations resulting in sudden, unexplained failures or hang-ups of Oracle Data Integrator (ODI) process executions which previously ran successfully.

Behavior and error messages

Unique constraint (PK_EXP_TXT) violated...

The execution of a given Session suddenly hangs, without any error message, while other Sessions successfully go to completion.

Most commonly, this happens on:

• loading steps such as "Drop work table" and "Create work table" and
• integration steps such as "Drop flow table" and "Create flow table I$".

If the execution if processed by an Agent, the following is signaled in the Agent trace:

where the message is raised when the value of an I_TXT column becomes greater than 10 digits.

Troubleshooting Steps

My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.