Support Article

Commit failed as the queries are not running in sequence

SA-33859

Summary



Committing the differed pages does not happen in sequence. For example, Page A, Page B, and Page C are saved in sequence, but during execution Page C is commited before Page B. Page B contains the parent table data in foreign key, and relationships commit fails. The same batch worked in PRPC 6.1.

Error Messages



Error in commit()
com.pega.pegarules.pub.database.IntegrityConstraintViolationException: [jcc][t4][102][10040][4.19.56] 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
DatabaseException caused by prior exception: com.ibm.db2.jcc.am.BatchUpdateException:[jcc][t4][102][10040][4.19.56] 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
| SQL Code: -4229 | SQL State: null


Steps to Reproduce



Unknown

Root Cause



A defect in Pegasystems' code or rules

Resolution



Perform the following local-change:
Use the following XML tag in prconfig.xml:

To Disable Merge: <env name= ‘’classmap/usemergestatement" value="false"/>
To Disable Batch: <env name= ”database/batchUpdates" value="-1"/>

Published February 17, 2017 - Updated March 7, 2017

Have a question? Get answers now.

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