Support Article
Agents crashed with "Database save using an insert" error
SA-639
Summary
You observe agents for Pega-ProCom: Correspondence, SLA events, & Bulk Processing (Assign-.ProcessServiceLevelEvents) for all nodes abort.
Error Messages
Error in commit()
com.pega.pegarules.pub.database.DatabaseException: Database-Saver-Insertfail
Caused by SQL Problems.
Problem #1, SQLState 22001, Error code -302: com.ibm.db2.jcc.b.SqlException: DB2 SQL error: SQLCODE: -302, SQLSTATE: 22001, SQLERRMC: null
Caused by:
com.ibm.db2.jcc.b.SqlException: 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.
Resolution
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
Have a question? Get answers now.
Visit the Collaboration Center to ask questions, engage in discussions, share ideas, and help others.