Extract rule causing BatchUpdateException ERRORCODE=-4229
While running a BIX Extract that outputs to a target database, a batch exception is thrown. This only occurs if one or more of the work objects being extracted had already been extracted, but there have been updates to it since.
<date> [PRPCWorkManager : 18] [ ] [your_app:01.01.01] ( internal.access.ExtractImpl) ERROR your_user - Batch Update Exception: [jcc][t4][4.19.49] 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
Steps to Reproduce
1. Create a work object in the source system.
2. Run the Extract rule that outputs to a target database.
2. Update the record from step 1.
3. Run the Extract rule again.
A defect or configuration issue in the operating environment. When Pega generates a schema DDL for an Extract rule, no primary keys are defined. This issue is occurring because a primary key had been added to the pzInsKey column on the target table. BIX Extracts only insert into the target table, they do not update existing records.
Remove the primary key on the target table.
0% found this useful