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 ORA-22835 when executing a query for Report Definition

SA-45759

Summary



ORA-22835 error occurs when executing a query for a Report Definition.


Error Messages



There was a problem getting a list: code: 22835 SQLState: 99999 Message: ORA-22835: Buffer too small for CLOB to CHAR or BLOB to RAW conversion (actual: 13146, maximum: 4000)


Steps to Reproduce

  1. Create a Report Definition
  2. Refer a property (Column: CLOB).
  3. Run the report.


Root Cause



A defect or configuration issue in the operating environment.

A database is limited to 4000 bytes in a VARCHAR2 column. When the property value length is greater than 4000, a CLOB column must be used. However, support for a CLOB was not available until Pega 7.2.2.



Resolution



Perform the following local-change:
  1. Set the reporting/retrieveFullClobContent Dynamic System Setting (DSS) defined on Pega-RULES to True.
  2. Install HFix-37641.
  3. Restart the server.
After performing the local-change, delete the distinct clause from the query if the below error occurs.

ERROR - Not returning connection 8 for database "pegadata" to the pool as it previously encountered the following error
(rd.queryexec.SqlQueryExecutor) ERROR - An error occured on executing the query for the report definition - There was a problem getting a list: code: 932 SQLState: 42000 Message: ORA-00932: inconsistent datatypes: expected - got CLOB



Published March 8, 2018 - Updated October 8, 2020

Was this useful?

66% 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