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

Sorting Case ID in numeric order causes DB errors



Currently Pega sorts CASE ID as Text, as in, after C-1, C-10, C-11... C-100, C-101 comes C-2.

User followed the article:http://
works fine for system with 4000 to 5000 cases. But when case number increase, user encounters database errors.

Error Messages

Log error noticed:
2017-11-08 22:30:40,875 [ WebContainer : 6] [TABTHREAD1] [ ] [#####:01.01.01] ( rd.queryexec.SqlQueryExecutor) ERROR #####|$$$.$$$.$$$.$$$ ##### - An error occured on executing the query for the report definition - There was a problem getting a list: code: 1013 SQLState: 72000 Message: ORA-01013: user requested cancel of current operation
DatabaseException caused by prior exception: java.sql.SQLTimeoutException: ORA-01013: user requested cancel of current operation
| SQL Code: 1013 | SQL State: 72000

Steps to Reproduce

1. Follow this article
2. Define the Function alias as in the above link.
3. Include around 30 to 40,000 cases in the system.
4. Sort on Case ID.

Root Cause

An issue in the custom application code or rules:

A property in the report was not exposed. Extracting the values from the blob was causing the query overhead.


Perform the following local-change:

Expose the affected property in the report.

Published March 28, 2018 - 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