Question
AIG
US
Last activity: 29 Aug 2018 8:26 EDT
SPPR_PURGE_TABLE table huge time
SPPR_PURGE_TABLE store proc at restart time is taking huge time.
following table has multiple million of record and queries are timeing out since long. DBA is recommending to truncate instead of datatime delete. Can we trauncate following cleanup tables? what will bethe impact?
PR_LOG_REPORTSTATS
pr_perf_stats
pr4_log_rule_usage
pr4_log_rule_usage_details
Pegasystems Inc.
IN
See if systemcleaner agent is running properly. you can truncate data of these tables
Kindly go through Pega Help here to understand these tables usages and about retention of data in perf table:
Pegasystems Inc.
PL
Hi,
The best option is to use the Purge Agents which will remove unnecessary data from the database. You can look at other options :
Hi,
The best option is to use the Purge Agents which will remove unnecessary data from the database. You can look at other options :
- Purge/Archive of old work objects: https://community.pega.com/sites/default/files/help_v72/procomhelpmain.htm
- Review System Cleaner to see how big the table has grown: https://community.pega.com/support/support-articles/system-cleaner-not-cleaning-perf-stats-table
General Database information can be found here:
In case of the emergency situation where the system is not responding you can
- take a snapshot of the DB
- run below queries
#Rules Schema
TRUNCATE TABLE pegarules.pr_assembledclasses;
TRUNCATE TABLE pegarules.pr_sys_cache_entry;
TRUNCATE TABLE pegarules.pr_sys_cache_impl;
TRUNCATE TABLE pegarules.pr_sys_class_ancestors;
TRUNCATE TABLE pegarules.pr_sys_ruleset_index;
TRUNCATE TABLE pegarules.pr4_rule_sysgen;
TRUNCATE TABLE pegarules.pr_sys_app_hierarchy_flat;
TRUNCATE TABLE pegarules.pr_sys_app_ruleset_index;
TRUNCATE TABLE pegarules.pr_sys_rule_impl;
TRUNCATE TABLE pegarules.pr_sys_appcache_dep;
TRUNCATE TABLE pegarules.pr_sys_appcache_entry;
TRUNCATE TABLE pegarules.pr_sys_appcache_shortcut;#Data Schema
TRUNCATE TABLE pegadata.pr_sys_statusnodes;
TRUNCATE TABLE pegadata.pr_sys_locks;
TRUNCATE TABLE pegadata.pr_sys_updatescache;
TRUNCATE TABLE pegadata.prpc_ignite_server_addr;
TRUNCATE TABLE pegadata.pr_sys_queue_ftsindexer;
- clear the cache on the application server and restart the docker.
Thanks,
Lukasz