Yogenkumar Zalawadia (YogenkumarZ6328)
Royal Bank of Canada

Royal Bank of Canada
YogenkumarZ6328 Member since 2020 2 posts
Royal Bank of Canada
Posted: September 21, 2020
Last activity: September 22, 2020
Posted: 21 Sep 2020 15:34 EDT
Last activity: 22 Sep 2020 8:14 EDT

Do we need to consider PR_PERF_STATS for Reorg Job at DB side?

We have observed few issue in our weekly PEGA table reorganization process (i.e. exclusive mode) is taking too long to complete.

We noticed that, table PR_PERF_STATS takes a few hours (exceeding 5 hours) to complete Reorganizaiton process in our application. We also found that the 

table is kept increasing in size (due to insert of data rather than delete).  

Could any one help to ge the below information :-

1. How pega insert the value in table PR_PERF_STATS ? I have observed in few PDN article, It talks about Dynamic System Settings data instance Pega-RULES usage/usagetrackingenabled. This value determine the Login information captured in table PR_PERF_STATS for any performace analysis in future.

2. If we truncate the table PR_PERF_STATS, will it cause any impact?

3.    How often will the said table be cleaned up ? - Please correct me, System Cleaner agent runs daily which in turn call (UsageCleaner) stored procedure (sppr_purge_table) to purge the records, based on RententionDays.

4.    Would there be performance degradation or any consequence incurred, should we be stopping the PR_PERF_STATS table reorganization?   


Thank You


Pega Platform 7.1.8 System Administration Financial Services System Architect