BIX Extract is failing when configured from an agent
We have configured the BIX rule from agent but we are seeing exceptions when the agent runs. Below is the exception we are getting.
2016-12-20 19:47:00,354 [ PegaRULES-Batch-1] [ ] [ Complaint:01.01.02] ( internal.access.ExtractImpl) INFO - BIX Version : 7.1
2016-12-20 19:47:00,511 [ PegaRULES-Batch-1] [ ] [ Complaint:01.01.02] ( internal.access.ExtractImpl) INFO - Target database using batch inserts
2016-12-20 19:47:11,723 [ PegaRULES-Batch-1] [ ] [ Complaint:01.01.02] ( internal.access.ExtractImpl) ERROR - Batch Update Exception: [jcc][t4][102][10040][4.18.60] 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][4.18.60] 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.kd.a(kd.java:475)
at com.ibm.db2.jcc.am.Agent.endBatchedReadChain(Agent.java:414)
at com.ibm.db2.jcc.am.cp.a(cp.java:5238)
at com.ibm.db2.jcc.am.cp.c(cp.java:4825)
at com.ibm.db2.jcc.am.cp.executeBatch(cp.java:3036)
We have configured the BIX rule from agent but we are seeing exceptions when the agent runs. Below is the exception we are getting.
2016-12-20 19:47:00,354 [ PegaRULES-Batch-1] [ ] [ Complaint:01.01.02] ( internal.access.ExtractImpl) INFO - BIX Version : 7.1
2016-12-20 19:47:00,511 [ PegaRULES-Batch-1] [ ] [ Complaint:01.01.02] ( internal.access.ExtractImpl) INFO - Target database using batch inserts
2016-12-20 19:47:11,723 [ PegaRULES-Batch-1] [ ] [ Complaint:01.01.02] ( internal.access.ExtractImpl) ERROR - Batch Update Exception: [jcc][t4][102][10040][4.18.60] 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][4.18.60] 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.kd.a(kd.java:475)
at com.ibm.db2.jcc.am.Agent.endBatchedReadChain(Agent.java:414)
at com.ibm.db2.jcc.am.cp.a(cp.java:5238)
at com.ibm.db2.jcc.am.cp.c(cp.java:4825)
at com.ibm.db2.jcc.am.cp.executeBatch(cp.java:3036)
at com.pega.pegarules.data.internal.access.DatabasePreparedStatementImpl.executeBatch(DatabasePreparedStatementImpl.java:534)
at com.pega.pegarules.data.internal.access.ExtractImpl.insertRowsBatchMode(ExtractImpl.java:5811)
at com.pega.pegarules.data.internal.access.ExtractImpl.doExtract(ExtractImpl.java:3347)
at com.pega.pegarules.data.internal.access.ExtractImpl.runExtract(ExtractImpl.java:1730)
at com.pega.pegarules.data.internal.access.ExtractImpl.init(ExtractImpl.java:1383)
at com.pega.pegarules.data.internal.access.ExtractImpl.parseAndRunExtractCommand(ExtractImpl.java:1328)
at com.pega.pegarules.data.internal.access.ExtractImpl.executeCommandLineExtract(ExtractImpl.java:1045)
at com.pega.pegarules.data.internal.PRDataProviderImpl.executeCommandLineExtract(PRDataProviderImpl.java:1314)
at com.pega.pegarules.session.internal.mgmt.Executable.executeCommandLineExtract(Executable.java:8282)
at com.pegarules.generated.activity.ra_action_pxextractdatawithargs_af9552bf7ad754cbdac2e3d257607afb.step3_circum0(ra_action_pxextractdatawithargs_af9552bf7ad754cbdac2e3d257607afb.java:411)
at com.pegarules.generated.activity.ra_action_pxextractdatawithargs_af9552bf7ad754cbdac2e3d257607afb.perform(ra_action_pxextractdatawithargs_af9552bf7ad754cbdac2e3d257607afb.java:103)
at com.pega.pegarules.session.internal.mgmt.Executable.doActivity(Executable.java:3500)
at com.pega.pegarules.session.internal.async.agent.QueueProcessor.runActivity(QueueProcessor.java:721)
at com.pega.pegarules.session.internal.async.agent.QueueProcessor.execute(QueueProcessor.java:602)
at com.pega.pegarules.session.internal.async.BatchRequestorTask.run(BatchRequestorTask.java:945)
at com.pega.pegarules.session.internal.PRSessionProviderImpl.performTargetActionWithLock(PRSessionProviderImpl.java:1259)
at com.pega.pegarules.session.internal.PRSessionProviderImpl.doWithRequestorLocked(PRSessionProviderImpl.java:1008)
at com.pega.pegarules.session.internal.PRSessionProviderImpl.doWithRequestorLocked(PRSessionProviderImpl.java:901)
at com.pega.pegarules.session.internal.async.BatchRequestorTask.run(BatchRequestorTask.java:670)
at com.pega.jsr166backport.java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:991)
at com.pega.jsr166backport.java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:532)
at java.lang.Thread.run(Thread.java:745)
Environment details: Pega 7.1.8
BIX: 7.1
DB: IBM DB2
We created below DSS but no luck.
Owning Ruleset: Pega-Engine
Setting Purpose: prconfig/database/batchUpdates/default
Value: -1
Any help would be appreciated.
Bharatesh
***Updated by moderator: Lochan to update Categories***
Accepted Solution
Incessant Technologies
IN
Issue was due to datatype mismatch in work table & extract table. TimeStamp columns from work tables were mapped to VARCHAR column in extracted table to store the date value only. After correcting the type mismatch, we were able to run the Extract using agent without any issues.
Pegasystems
IN
We have configured the BIX rule from agent but we are seeing exceptions when the agent runs.
Are you using the pxExtractDataWithArgs activity to execute BIX via agent?
We created below DSS but no luck.
Owning Ruleset: Pega-Engine
Setting Purpose: prconfig/database/batchUpdates/default
Value: -1
This DSS has not effect on BIX. You should be using the -b command line argument to control the batch size.
Also, share the full log file to understand the issue correctly.
Incessant Technologies
IN
Initially we tried with -b 1000 parameter to pxExtractDataWithArgs activity but the same issue was observed. Attached the log file for your reference.
Bharatesh
Accepted Solution
Incessant Technologies
IN
Issue was due to datatype mismatch in work table & extract table. TimeStamp columns from work tables were mapped to VARCHAR column in extracted table to store the date value only. After correcting the type mismatch, we were able to run the Extract using agent without any issues.