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

Reporting feature is not optimized in database



User notices thread dump from Pega Log and suspects reporting performance issue due to presence of ra_action_pzshowlvorsvreport_ activity logs statements.

Error Messages

Thread dump revealed one thread with a stacktrace pointing to activity ra_action_pzshowlvorsvreport.

Steps to Reproduce

The report is standard in Pega - getcontenthistorydetailedperf. The table created is an extension of Pega's pc_history tables and is named with customer's ruleset name.

Root Cause

The root cause of this problem is related to the absence of indices on database table pc_History_<appl-ruleset-name>.


This issue is resolved by tuning the database table.

Published August 13, 2015 - 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