Support Article
Batch Update Exception: String or binary data would be truncated
SA-6769
Summary
BIX Extract is failing with errors.
Issue 1: ERROR - Batch Update Exception: The conversion of a datetime2 data type to a datetime data type resulted in an out-of-range value.
java.sql.BatchUpdateException: The conversion of a datetime2 data type to a datetime data type resulted in an out-of-range value
Issue 2: ( internal.access.ExtractImpl) ERROR - Batch Update Exception: String or binary data would be truncated.
Error Messages
Issue 1: ERROR - Batch Update Exception: The conversion of a datetime2 data type to a datetime data type resulted in an out-of-range value.
java.sql.BatchUpdateException: The conversion of a datetime2 data type to a datetime data type resulted in an out-of-range value
Issue 2: ( internal.access.ExtractImpl) ERROR - Batch Update Exception: String or binary data would be truncated.
Steps to Reproduce
Not Applicable
Root Cause
The root cause of this problem is a defect in Pegasystems’ code/rules.
Issue 1 resolved after refreshing the DB data.
Issue 2: When extracting a page group property, PRPC auto add a key property which stores the indices of the page group. The truncation logic is not applied to the auto generated key columns in a page group. This is expected behaviour. Because if we truncate the key column , it wont be having unique values. (The truncation logic is not applied to the pzInskey column also)
Resolution
This issue is resolved through the following local change:
Change the DDL to have key column length as 64 instead 18.
Published January 31, 2016 - Updated October 8, 2020
Have a question? Get answers now.
Visit the Collaboration Center to ask questions, engage in discussions, share ideas, and help others.