Question
Tech Mahindra
Tech Mahindra
CA
Tech Mahindra
Posted: Oct 20, 2017
Last activity: Oct 23, 2017
Last activity: 23 Oct 2017 1:30 EDT
Closed
Pega BIX Extracts - Efficient Debugging
During Development, whenever, we see an error in BIX-Log File, we see something similar as below:
2017-10-20 06:15:06,775 [ xxxxxxxxxx.xxx] [ ] [ ] ( internal.access.ExtractImpl) ERROR - SQL Exception: Execution of insert returned 0 rows inserted. PzInsKey of the errored row: A-B-C-WORK W-123456
2017-10-20 06:15:06,775 [ xxxxxxxxxx.xxx] [ ] [ ] ( internal.access.ExtractImpl) DEBUG - DB2 SQL Error: SQLCODE=-302, SQLSTATE=22001, SQLERRMC=null, DRIVER=4.18.60
It means, the Destination Column Size is not enough size to hold the data.
In our application, we have 44 - 45 such staging tables and each of them have 50 - 60 columns on an average. Now this error message does not tell us the Table Name / Column name for which the error occurred.
- Is there any other tool (e.g. Logging Level Settings etc.) to narrow down this error reporting to speed up the debugging process?
- By default, Pega considers VARCHAR (31) for any Text type property while creating the DDL for BIX Extracts. Is there any way to determine the highest length of that text field stored in the DB?
Posted: 7 years ago
PEGA
Pegasystems Inc.
IN
Hi,
- Is there any other tool (e.g. Logging Level Settings etc.) to narrow down this error reporting to speed up the debugging process?
- Change the below classes to debug level in prlogging file.
- com.pega.pegarules.data.internal.access.DatabaseUtilsCommonImpl
- com.pega.pegarules.engine.database.DatabasePreparedStatement
- By default, Pega considers VARCHAR (31) for any Text type property while creating the DDL for BIX Extracts. Is there any way to determine the highest length of that text field stored in the DB?
- You can check the table structure using any db tools by looking at the table properties.