Question
Deleting the DB cache after the rules import is mandatory?
Is it mandatory to truncate these DB tables everytime rules are imported into the instance? even after the deleting the file system cache and restarting the server?
pega_rules.pr_assembledclasses;
pega_rules.pr4_rule_sysgen;
pega_rules.pr_sys_appcache_entry;
pega_rules.pr_sys_appcache_dep;
pega_rules.pr_sys_appcache_shortcut;
pega_rules.pr_sys_cache_dep;
pega_rules.pr_sys_cache_entry;
pega_rules.pr_sys_cache_impl;
Are there any operations guide for Pega 7.1.9 that displays list of steps that need to be done after the import/deplyment?
Accepted Solution
Hello Veeranjan,
I strongly disagree with Arvind. You should NOT be making changes to the content of those internal tables unless there is an issue and you have been guided to do so by a customer support engineer. The system should update the content of those tables correctly as part of the import. If it is failing to do so, it's a product defect that should be addressed with customer support. You shouldn't even need to delete the file system cache or restart the server for a rules import. Please don't truncate tables or delete system generated content unless it is absolutely necessary. Best case scenario you take a significant performance hit early on as everything goes through assembly, worst case, you do it wrong and severely impact your system in hard to predict (and possibly hard to identify/correct) ways.
Thanks,
Mike
Accepted Solution
Hello Veeranjan,
I strongly disagree with Arvind. You should NOT be making changes to the content of those internal tables unless there is an issue and you have been guided to do so by a customer support engineer. The system should update the content of those tables correctly as part of the import. If it is failing to do so, it's a product defect that should be addressed with customer support. You shouldn't even need to delete the file system cache or restart the server for a rules import. Please don't truncate tables or delete system generated content unless it is absolutely necessary. Best case scenario you take a significant performance hit early on as everything goes through assembly, worst case, you do it wrong and severely impact your system in hard to predict (and possibly hard to identify/correct) ways.
Thanks,
Mike
Mike,
I thought the same, it doesn't make sense to deployment users worrying about the PRPC internal cache, I thought once the deployment is done system should take care of invalidating the cache and making the new rules into affect.
There was lot of misinformation out there about the post import actions that has to be done.
If we have some kind of operation guide for deployment users, that would be very helpful, especially for the people who automate the deployments with collaboration tools like jenkins ..etc.
Thank You,
Veeranjan Bonthu