Event Code PRMDB-XXXX-X "String or Binary Data Would Be Truncated" and "INSERT statement conflicted with the FOREIGN KEY constraint" When Importing an XER File in P6 (Doc ID 2398380.1)

Last updated on MAY 19, 2023

Applies to:

Symptoms

When attempting to import an XER file into P6, the following error occurs:

Event Code: PRMDB-XXXX-X, PRMDB-0149-C, PRMDB-0219-2
Message: PRM DBAccess Error: SQL State: 1, SQL Error Code: 3621, Level: 0, Procedure: , Line: 1
The statement has been terminated.
SQL State: 14, SQL Error Code: 8152, Level: 16, Procedure: , Line: 1
String or binary data would be truncated.

Followed by a Foreign Key constraint conflict (examples below):

Event Code: PRMDB-2982-C
Message: PRM DBAccess Error: SQL State: 1, SQL Error Code: 3621, Level: 0, Procedure: , Line: 1
The statement has been terminated.
SQL State: 1, SQL Error Code: 547, Level: 16, Procedure: , Line: 1
The INSERT statement conflicted with the FOREIGN KEY constraint "fk_projwbs_project". The conflict occurred in database "<DB>", table "dbo.PROJECT", column 'proj_id'.

    or

PRM DBAccess Error: SQL State: 1, SQL Error Code: 3621, Level: 0, Procedure: , Line: 1
The statement has been terminated.
SQL State: 1, SQL Error Code: 547, Level: 16, Procedure: , Line: 1
The INSERT statement conflicted with the FOREIGN KEY constraint "fk_taskpred_task". The conflict occurred in database "<DB>", table "dbo.TASK", column 'task_id'.

OR (with an Oracle database):

ORA-12899: value too large for column "ADMUSER"."TASK"."TASK_NAME"

Changes

Cause