Support Article
Reporting feature is not optimized in database
SA-13040
Summary
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>.
Resolution
This issue is resolved by tuning the database table.
Published August 13, 2015 - Updated October 8, 2020
Have a question? Get answers now.
Visit the Collaboration Center to ask questions, engage in discussions, share ideas, and help others.