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

SQL errors thrown on case update



When attempting to update a case, SQL errors are thrown.

Error Messages

Encountered problem when performing a Commit. Database-General    Problem saving instance of class

DB2 SQL Error: SQLCODE=-206, SQLSTATE=42703, SQLERRMC=INPUTS.ColumnNameAbbr, DRIVER=4.19.26

Steps to Reproduce

Update and attempt to save a work object with Pega 7.1.9.

Root Cause

Pega 7.1.7 and later versions, add MERGE transactions as a default mode for saving instances.

The Merge statement is updating a column whose name is mismatched between Pega and the database schema.



1. Add the following setting to prconfig.xml file to disable use of MERGE statements.
<env name="classmap/usemergestatement" value ="false" />
2. Restart PRPC to update the environment.

Further details on this operation are described in the PDN article:

Published May 27, 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