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

Agents crashed with "Database save using an insert" error



You observe agents for Pega-ProCom: Correspondence, SLA events, & Bulk Processing (Assign-.ProcessServiceLevelEvents) for all nodes abort.

Error Messages

Error in commit() Database-Saver-Insertfail
Caused by SQL Problems.
Problem #1, SQLState 22001, Error code -302: DB2 SQL error: SQLCODE: -302, SQLSTATE: 22001, SQLERRMC: null
Caused by: DB2 SQL error: SQLCODE: -302, SQLSTATE: 22001, SQLERRMC: null

Steps to Reproduce

Have a third party job manipulate the source database tables which causes instability which in turn prevents proper agent processing.

Root Cause

The root cause of this problem is defect/misconfiguration in the PRPC operating environment. The agents are working on tables that are being manipulated by an external source.


You will want to integrate the third party database maintenance job into the Pega environment or make the process manual and halt agents during the operation.

Published June 12, 2015 - 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