Skip to main content

This content has been archived and is no longer being updated. Links may not function; however, this content may be relevant to outdated versions of the product.

Support Article

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.

Error Messages

<date> [PRPCWorkManager : 18] [ ] [your_app:01.01.01] ( internal.access.ExtractImpl) ERROR your_user - Batch Update Exception: [jcc][t4][102][10040][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.

Root Cause

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.

Published July 16, 2016 - Updated October 8, 2020

Was this useful?

0% found this useful

Have a question? Get answers now.

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

Did you find this content helpful?

Want to help us improve this content?

We'd prefer it if you saw us at our best.

Pega Community has detected you are using a browser which may prevent you from experiencing the site as intended. To improve your experience, please update your browser.

Close Deprecation Notice
Contact us