Question
What cache tables should be truncated?
We have multiple projects running on different versions of PRPC. Does anyone know if the cache tables that need to be truncated vary depending on the PRPC version? If so, does anyone have recommendations by version?
***Updated by moderator: Lochan to close 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.
We are advised to truncate the following cache tables to avoid performance issues. Please advise me that how often we can do this cache tables truncation? Can we do this while Pega is online? Do we have to restart after truncation by deleting the PegaRULES_Extract_Marker.txt file? Is this following list is enough or do we have to consider any different cache table(s) for Pega 7.1.9? Would it be feasible to have an Agent activity to truncate these tables by weekly without system restart?
TRUNCATE TABLE PR_SYS_APP_HIERARCHY_FLAT;
TRUNCATE TABLE PR_SYS_APP_RULESET_INDEX;
TRUNCATE TABLE PR_SYS_CLASS_ANCESTORS;
TRUNCATE TABLE PR_ASSEMBLEDCLASSES;
TRUNCATE TABLE PR4_RULE_SYSGEN;
TRUNCATE TABLE PR_SYS_APPCACHE_ENTRY;
TRUNCATE TABLE PR_SYS_APPCACHE_DEP;
TRUNCATE TABLE PR_SYS_APPCACHE_SHORTCUT;
TRUNCATE TABLE PR_SYS_CACHE_DEP;
TRUNCATE TABLE PR_SYS_CACHE_ENTRY;
TRUNCATE TABLE PR_SYS_CACHE_IMPL;
TRUNCATE TABLE PR_SYS_CACHE_DEP;
This comment has been branched out as a new node and the new thread can be followed here
Hi Anurathan,
Since this question is Answered and your question, even though related, looks like it needs its own thread of discussion. To facilitate this, we have branched your reply into a new post. Please update this new post for any details and continue troubleshooting: Seeking Advise on cache tables truncation in order to avoid performance issues
Thank you
The short answer is none of them. Truncating cache tables is not something that should be done as part of a standard operating procedure. If there is a specific issue that leads you to think you might want to truncate the cache tables, you should contact GCS. Either it's a known issue for which there is a fix (and you'll want it) or you've found an unknown defect in the code and truncating the tables will remove key artifacts that would allow us to identify and address that defect. Unfixed cache defects avoided with a cache truncation will eventually pop up again, which is why you are better off engaging GCS before truncating the cache tables. There may be times when support recommends that you take that step. If so, we can guide you through which tables you want to truncate for your specific version of the product.