Support Article
pxUpdateTime is not getting updated accordingly
SA-40165
Summary
User reports that they are using Business Intelligence Exchange (BIX) for our reporting and BIX extraction logic (Reporting Batch) run on daily basis and get the records from last update date time, the issue is only with the request which is bulk closed from backend.
When they close the request from backend system will not capture the update date time to current date.
Error Messages
00:49:56,438 ( internal.access.ExtractImpl) ERROR - Batch Update Exception: [jcc][t4][102][10040][3.63.75] Batch failure. The batch was submitted, but at least one exception occurred on an individual member of the batch.
Use getNextException() to retrieve the exceptions for specific batched elements. ERRORCODE=-4229, SQLSTATE=null
com.ibm.db2.jcc.am.BatchUpdateException: [jcc][t4][102][10040][3.63.75] Batch failure. The batch was submitted, but at least one exception occurred on an individual member of the batch.
Use getNextException() to retrieve the exceptions for specific batched elements. ERRORCODE=-4229, SQLSTATE=null
at com.ibm.db2.jcc.am.fd.a(fd.java:407)
at com.ibm.db2.jcc.am.n.a(n.java:386)
at com.ibm.db2.jcc.am.zn.a(zn.java:4897)
at com.ibm.db2.jcc.am.zn.c(zn.java:4528)
at com.ibm.db2.jcc.am.zn.executeBatch(zn.java:2837)
at com.pega.pegarules.data.internal.access.DatabasePreparedStatementImpl.executeBatch(DatabasePreparedStatementImpl.java:525)
at com.pega.pegarules.data.internal.access.ExtractImpl.addDbRow(ExtractImpl.java:3904)
at com.pega.pegarules.data.internal.access.ExtractImpl.writeRow(ExtractImpl.java:3698)
at com.pega.pegarules.data.internal.access.ExtractImpl.writeRow(ExtractImpl.java:3680)
at com.pega.pegarules.data.internal.access.ExtractImpl.WritetoOutput(ExtractImpl.java:3616)
at com.pega.pegarules.data.internal.access.ExtractImpl.doExtract(ExtractImpl.java:2555)
at com.pega.pegarules.data.internal.access.ExtractImpl.runExtract(ExtractImpl.java:1369)
at com.pega.pegarules.data.internal.access.ExtractImpl.run(ExtractImpl.java:1138)
at com.pega.pegarules.data.internal.access.ExtractImpl.init(ExtractImpl.java:1112)
at com.pega.pegarules.data.internal.access.ExtractImpl.main(ExtractImpl.java:1063)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:597)
at com.pega.pegarules.internal.bootstrap.PRBootstrap.invokeMethod(PRBootstrap.java:349)
at com.pega.pegarules.internal.bootstrap.PRBootstrap.invokeMethodPropagatingThrowable(PRBootstrap.java:390)
at com.pega.pegarules.internal.bootstrap.PRBootstrap.invokeMethod(PRBootstrap.java:439)
at com.pega.pegarules.pub.PegaRULES.main(PegaRULES.java:85)
00:49:56,439 ( internal.access.ExtractImpl) ERROR - Failed to execute an insert for record :<Record ID>
Steps to Reproduce
1. Create an BIX Extract rule with output as "Database".
2. Make sure that one of the columns that are part of extraction exceeds the column length.
3. Verify Pega-BIX logs to notice an error related to Batch failure.
Root Cause
One of the columns which is mapped to a text area in the UI, consists of more data than expected, due to which it exceeds the length defined for that column.
As the execution is happening from Pega Application as a "Batch", actual error message is not visible in the logs.
Resolution
Perform the following local-change steps:
- Increase the Length of the column to process the existing records.
- Setup a validation at the UI level to restrict the no of characters which can be entered to a field.
- Make sure that Source Database and Target Database have the same restriction on the column length.
Published October 10, 2017 - 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.