Posted: 31 Aug 2015 2:54 EDT Last activity: 6 Apr 2018 19:26 EDT
Delete unused tables from rules and data schemas post upgrade
We have completed Out-Of-Place Upgrade of 6.1 SP1 to 7.1.6. Now we have two schemas abc_rules and abc_data. Problem we see is, there are unused duplicate tables left over in both the schemas. I want to understand which utilities do i need to run to delete these tables
Thanks in advance
**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.
By end of Upgrade, Your PegaRules schema will have few data tables ( such as PR_DATA_ADMIN ) and your PegaData schema will have rules tables of older version OR tables without any class associations. These tables can be dropped as explained by Saikhom.
But, be careful before dropping the tables. Try to understand how & why the table is there in first place before dropping it.
After the upgrade from pega6.3 to pega 7 some of the tables are below available in rule schema. But those tables are not having class association from PRPC(Means all these tables are referring to Data schema from data table instances). Can you tell whether we can delete these tables in rule schema as they did not have class association. And one more observation is one of the data base table instance is referring to 'data base' is data schema and 'Reports data base' is rule schema. So do we needs to keep this table in both schemas or it should map to Data schema for both? Data table instance is "Pega-CEP-Subscription".
And also it will help us to validate the rule schema if you post the list of tables (if you have)that should be available in rule schema after upgrade and cleanup.