Identity Governance - import from IM fails wth SQL error: String or binary data would be truncated.

Products

• CA Identity Suite

Issue/Introduction

Identity Governance import from Identity Manager fails.

The errors in eurekify.log:

16:49:23,441 WARN  [com.ca.rcm.services.trace.TraceMessage] (import-connector thread-1) TraceMessage param1 value is too long: 325 it will be truncated to 256 characters; value: org.springframework.dao.DataIntegrityViolationException: PreparedStatementCallback; SQL [ INSERT INTO ResourceFields (DatabaseID, ResourceID, FieldNumber, FieldValue) VALUES (?, ?, ?, ?) ]; String or binary data would be truncated.; nested exception is ...
16:49:23,450 ERROR [stderr] (import-connector thread-1) com.eurekify.command.CommandExecutionException: org.springframework.dao.DataIntegrityViolationException: PreparedStatementCallback; SQL [ INSERT INTO ResourceFields (DatabaseID, ResourceID, FieldNumber, FieldValue) VALUES (?, ?, ?, ?) ]; String or binary data would be truncated.; nested exception is java.sql.BatchUpdateException: String or binary data would be truncated.

Environment

Release : 14.3 CP2, 14.4 X or any further version if schema changes were not applied.

Component : CA IDENTITY SUITE (VIRTUAL APPLIANCE)

Cause

Identity Governance database schema was not upgraded during the product upgrade on 14.3 CP2.

Resolution

Please see the following document:

https://techdocs.broadcom.com/us/en/symantec-security-software/identity-security/identity-governance/14-3/release-notes/Cumulative-Patches/Previous-Cumulative-Patches.html

Under deployment instructions, the third point specified as the following. This was missed in customer env.

Identity Governance 14.3 CP2 has DATABASE SCHEMA changes. After deploying the patch, update the database schema by following the instructions provided in the  CP-IG-140300-0002_Instructions_On_How_To_Deploy  file of the extracted folder.

Additional Information

Applying these scripts will change DBVersion value in SAGE_VERSION table to 14.01.01.06

Extract from document CP-IG-140300-0002_Instructions_On_How_To_Deploy:

DB_Scripts Folder:

The scripts provided in the below folder must be run as the database user with which the product was
installed.

Oracle:
If your backend database is Oracle.
Run the below scripts on the database.
1. UPGRADE_SDB_ORACLE.sql -> Run this script on the SDB database.
2. UPGRADE_I2_DATABASE_ORACLe.sql -> Run this script on the gvmdatawarehouse(reporting)
database.
3. 3.52-OracleScriptMonUpdate.txt -> Run the stored procedure in the text file on your WPDS
(workpoint) database.

SQL Server:
If your backend database is SQL Server.
Run the below scripts on the database.
1. UPGRADE_SDB_SQL.sql -> Run this script on the SDB database.
2. UPGRADE_I2_DATABASE_SQL.sql -> Run this script on the gvmdatawarehouse(reporting) database.