In the split schema upgrade process,  coming from one old 6.x pega schema converting to 7.x pega_data and pega_rules, there is a manual cleanup step to identify unused tables that are residual in the PEGA_DATA schema from the old originating system.   These tables could vary depending on what pega version one is upgrading from.  Pega provides a manual step to remove these.   The problem is, I am currently helping with 17 upgrades in process, more on the way, and would like a general script to solve most of this cleanup by our script conversion team.  I anticipate we will still want to check manually for any misses, and improve this list.

This is the script we have derived by one of our upgrading teams.  Can we get confirmation that there is no issue removing these from PEGA_DATA schema for our script conversion team?   All of these should be unused in the PEGA_DATA schema correct?...

drop table pega_data.pr_index_circumstance_def;

drop table pega_data.pr_index_css;

drop table pega_data.pr_index_customfields;

drop table pega_data.pr_index_reference;

drop table pega_data.pr_index_trackstatus;

drop table pega_data.pr_index_warnings;

drop table pega_data.pr_link_usecase;

drop table pega_data.pr_sys_app_ruleset_index;

drop table pega_data.pr_sys_cache_dep;

drop table pega_data.pr_sys_cache_entry;

drop table pega_data.pr_sys_cache_impl;

drop table pega_data.pr_sys_class_ancestors;

drop table pega_data.pr_sys_decchg;

drop table pega_data.pr_sys_ruleset_index;

drop table pega_data.pr4_base;

drop table pega_data.pr4_fieldvalue;

drop table pega_data.pr4_rule;

drop table pega_data.pr4_rule_autotest;

drop table pega_data.pr4_rule_file;

drop table pega_data.pr4_rule_flow;

drop table pega_data.pr4_rule_property;

drop table pega_data.pr4_rule_ruleset;

drop table pega_data.pr4_rule_shortcut;

drop table pega_data.pr4_rule_sysgen;

drop table pega_data.pr4_rule_vw;