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

Work objects taking a long time to open in production



Work objects taking a long time to open in production
The work objects do eventually open but take 5-6 minutes to show on UI.

Error Messages

From alert logs:

Database operation took more than the threshold of 500 ms: 489,474 ms SQL: SELECT PXHISTORYFORREFERENCE AS "pxHistoryForReference" , PYMEMO AS "pyMemo" , PXTIMECREATED AS "pxTimeCreated", PZINSKEY as "pxInsHandle" from yourTable WHERE pxObjClass LIKE ? AND ( ( PXHISTORYFORREFERENCE = ? ) )


Steps to Reproduce

Try to open a Work Object.

Root Cause

A defect or configuration issue in the operating environment.  From the alert logs see that the database query taking a long time.  Oracle histograms are calculated on the first 32 characters of a column.  Since the values in the column are the same for more than the first 32 characters the histogram is actually blocking the index from being used and the result is a full table scan.  In this case both the pxObjClass and pxHistoryForReference column values are running into this issue.


Make the following change to the operating environment: 

Delete the histogram on the database table columns per this article to improve the performance in query execution.

Suggest Edit

Published October 28, 2016 - Updated October 8, 2020

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