Support Article
SQL errors thrown on case update
Summary
When attempting to update a case, SQL errors are thrown.
Error Messages
Encountered problem when performing a Commit.
com.pega.pegarules.pub.database.DatabaseException: 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.
Resolution
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:
https://pdn.pega.com/passing-custom-properties-oracle-database/passing-custom-properties-oracle-database
Published May 27, 2016 - 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.