Question
Virtusa
LK
Last activity: 16 Oct 2018 12:03 EDT
Database space full
Hi,
Pega installed Database has no space. Therefore cannot create rule rules and even create a case.
we don't have much data as in a large system and unable to increase size of database. Therefore what we have workaround.
Are their any tables can we clear?
Are their any tables storing temporary data able to clear?
we saw following tables take more space. Are there any tables able to clear?
pr_index_reference
pr4_rule
pr4_rule_property
pr4_rule_file_binary
pr4_rule_vw
pr_sysgen_static_content
pr4_rule_file
pr_assembledclasses
pr_engineclasses
pr4_rule_flow
pr_log_systemstate
pr_sys_appcache_shortcut
pr_perf_stats
pr_sys_appcache_dep
pr_index_css
pr4_rule_sysgen
pr4_rule_library
pr4_history_rule
Thank you.
***Edited by Moderator Marissa to update platform capability tags****
**Moderation Team has archived post**
This post has been archived for educational purposes. Contents and links will no longer be updated. If you have the same/similar question, please write a new post.
Virtusa
LK
We can't increase the table space. because we have limited space. That is what we are trying to clear tables or Is their any solution to compress tables and get space.
Pegasystems Inc.
US
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
Pegasystems Inc.
US
As far as I'm aware, there are no tables you can just clear to free up space. There are some caching tables, but if you clear them the will repopulate, so clearing them isn't going to do what you're looking for.
Rulesware LLC
US
Do we have updated list of cache clear tables from pega (for these situations). I am aware that in general truncation of cache tables is not a good practice, however we want to know the list of cache table per 7.3.1/7.4+
Pegasystems Inc.
PL
Hi,
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