Question
Post Upgrade Cleanup
We recently upgraded from Pega 6.1 to Pega 7.2.2. Post Upgrade I wanted to cleanup the PRPC rulesets from previous versions. I ran cleanup utility by setting ruleset cleanup as false and got the scripts to cleanup the old rulesets. The Scripts have condition on ruleset like "Pega%" and rulesetversion <'07-10' and pxobjclass like 'Rule-%'. To me scripts look ok, however I was going through the upgrade guide document for 7.2.2 and it says caution "Running this post upgrade might delete needed rulsets", hence my question here,is there anything specific that I need to take care when I run cleanup scripts post upgrade?
**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.
Thanks Dhev, I will validate what rulesets are being considered for deletion before I run the scripts.
Hi Chetan, if the clean up script works, can you share the script name ?
From where you executed those scripts?
does pega have any OOTB ?
cleanup.bat or cleanup.sh will be available in scripts folder of distribution image.
Hi Dhev,
In Dev environment, While upgrading from 6.2 to 7.2 we didn't run the cleanup script.
Currently we have upgraded the TEST Env by coping the rules schema from Dev and have run the cleanup script.
Lot of framework related rules got deleted due to this clean up. we have imported the frameworks again to restore the deleted rules.
Do you see any issues in this approch.
Thanks & Regards,
Mathew George
I am not sure whether you are performing this step immediate after Pega 7 platform upgrade is completed or after framework upgrades are completed.
If you are doing this step after platform upgrade is done then there wont be any issue.
If you are doing it after the framework upgrade is done and if any of the Pega 7 framework has rulesets which starts with Pega and ruleset version is less than 07-10 then all those rules get deleted. please check your application step before you proceed with it.
Also take the backup of the database.