Support Article
BIX - Data is truncated when extracting to external DB
SA-17620
Summary
Data is truncated while extracting to an external database (DB) even though the target column can hold more.
For example: In DB Table, there is a column with Data Type as VARCHAR2(256), but the data extracted to this column is truncated to 32 characters.
Data is inserted correctly if performed directly using insert query. The same does not occur if the target DB is the same as the PegaRULES DB. The issue also goes away if the "To Table" is schema qualified in the extract rule, but there is a length limit for this field.
Error Messages
Not Applicable
Steps to Reproduce
1. Create an Extract rule for a work class where some of the columns are VARCHAR2(64), making sure that at least some of the data is more than 32 characters.
2. Generate the DDL by running the Extract rule and run the DDL against the target DB.
3. Run the Extract rule to extract data in to the target DB.
Root Cause
A defect in Pegasystems’ code or rules. The column size is hardcoded to use an arbitrary value of 32 if BIX fails to find the length of the target column. Hence, data is truncated to 32, even though column length is larger in the target database.
Resolution
Apply HFix-25062.
After applying this HFix, instead of initializing the column length to 32 characters while extracting, application will consider the data field length on the property in the extract rule form for column length.
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.