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

Error while opening history of work object



User gets conclusion cache error while opening the work object history.

Error Messages

Status fail:

Message caught Database Exception while trying to open conclusion FieldValue!SALES: code: -302 SQLState: 22001 Message: DB2 SQL Error: SQLCODE=-302, SQLSTATE=22001, SQLERRMC=null, DRIVER=3.57.110

Steps to Reproduce

1. Add one history record for work object with long text. That is ‘pymessagekey’ field should have the large text value.
2. Try to open the work-object history.

Root Cause

When 'pymeassagekey' value is long, sqlstate "22001" was thrown. PRPC float an exception for this error while retrieving work object history which is causing the reported issue.


Changes were made in PRPC v5.3 code for catching up the errors. If error is for sqlstate “22001” then it will return null instead of floating the exception and also log a warning message in log file instead of an error message. These code changes are provided in ‘HFIX-10141’. Installing ‘HFIX-10141’ addresses the reported issue.
Suggest Edit

Published January 31, 2016 - Updated December 2, 2021

Did you find this content helpful? Yes No

Have a question? Get answers now.

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

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