Question

1
Replies
287
Views
SamikMallik Member since 2007 3 posts
Scotiabank
Posted: October 20, 2017
Last activity: October 23, 2017
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.
  1. Is there any other tool (e.g. Logging Level Settings etc.) to narrow down this error reporting to speed up the debugging process?
  2. 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?
Low-Code App Development Low-Code App Development Testing Applications
Moderation Team has archived post
Share this page LinkedIn