Support Article

BIX error writing DDL:"table cannot be more than 30 characters"

SA-38120

Summary



User has recently upgraded from PRPC 6.1 SP2 to Pega 7.2. They have upgraded BIX at the same time and this is running successfully in production.

A requirement has come to add some new properties to our BIX extracts and when trying to create the DDL script for this it is failing stating that a table name is too long, however, this is an existing table name that was being written to in the older version of BIX and is being written to in Pega 7.2.


Error Messages

ERROR - Error in writing DDL. Table Name Pega_Retiral_PolicyList_BoxUnits cannot be more than 30 characters
-------------------------
2017-05-08 13:51:05,218 [ wcsduv0091] ( internal.access.ExtractImpl) INFO - {b=1000, a=BIX_Admin, i=LBG-SW-LPI-WORK-NEWBUSINESS!BIX_P4LNB, X=../ddlFiles/BIX_P4LNB}
2017-05-08 13:51:18,612 [ wcsduv0091] ( internal.access.ExtractImpl) INFO - dbname:Microsoft SQL Server9.00.5069
2017-05-08 13:51:21,376 [ wcsduv0091] ( internal.access.ExtractImpl) ERROR - Error in writing DDL. Table Name Pega_P4LNB_PolicyList_Underwriting_FormerCheck cannot be more than 30 characters
2017-05-08 13:51:22,874 [ wcsduv0091] ( internal.access.ExtractImpl) INFO - PAL Statistics for BIX Extract run :
Non-rule-resolved instances accessed from the database: 181
CPU time accessing non-rule-resolved instances from the database: 0
Elapsed Time accessing non-rule-resolved instances from the database: 5.672
CPU time retrieving rule-resolved Rules from the database: 0
Rule-resolved rules requested from database or cache: 1
Bytes read from database Storage Streams (uncompressed): 3301386
Number of database requests that exceeded the time threshold: 0
CPU time spent performing BLOB decryption: 0
Elapsed time spent performing BLOB decryption: 0
BLOB decryption: 0

2017-05-08 13:51:22,887 [ wcsduv0091] ( internal.access.ExtractImpl) INFO - Created a schema file: ../ddlFiles/BIX_P4LNB.sql
No of Errors encountered after grepping the logs : 1
LBG-SW-LPI-WORK-NEWBUSINESS!BIX_P4LNB Errors have occurred while executing the Work extract
2017-05-08 13:54:17,


Steps to Reproduce



Add new property to BIX extract and run command line extract to create a DDL file.


Root Cause



This is an expected behavior. PRPC restricts the table length to maximum 30 characters.

Resolution



Explained as it is expected behavior.

Also, explained an alternative local-change to re-name the tables and use the same table name (of length < 30 characters) in BIX extract rule.

Published May 17, 2017 - Updated June 29, 2017

Have a question? Get answers now.

Visit the Collaboration Center to ask questions, engage in discussions, share ideas, and help others.