'ORA-00001: unique constraint (xxx.PK_EXP_TXT) violated' or '...PK_TXT_HEADER....' When Executing A Job After Upgrading To ODI 11g

(Doc ID 1328365.1)

Last updated on MAY 12, 2017

Applies to:

Oracle Data Integrator - Version to [Release 11gR1]
Information in this document applies to any platform.


Case #1

Executing a scheduled job in ODI raises the PK_EXP_TXT constraint violation following an upgrade to ODI 11g(11.1.1) from ODI 10g (10.1.3) .

Agent odi_agent_11g encountered an error: ODI-1219: Session preparation failure: database error while connecting to work repository WRKREP_PRD.[[
Caused By: java.sql.BatchUpdateException: ORA-00001: unique constraint (SNPW11G.PK_EXP_TXT) violated.

Case #2

Or when upgrading ODI repository from to the upgrade fails with error:

oracle.odi.setup.RepositorySetupException: java.sql.SQLIntegrityConstraintViolationException: ORA-00001: unique constraint (SNPW.PK_TXT_HEADER) violated.



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