Question
Royal Bank of Canada
CA
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
Yogen
Proximus
BE
Hello,
From what I've read this table is not perfectly cleaned and there's a DSS to reduce the retention.
It stores lots of performance information, but do you use them?
This table is part of the table list you can truncate when there's a major issue.
Have you checked the history data in it. By checking, I just saw that I've got more than a year of data in it which shouldn't be the case.
For me, if you don't need the data, you can safely truncate it. I do this after a refresh of non-prod with prod and it doesn't cause any issue. And when you start a fresh system, this table is empty by default and it's not creating an issue.
So at the end, it's more linked to your usage of this table.
Regards
Anthony