Optimize Schema not cleaning up all unused tables
After completing a split schema upgrade to 7.1.5 there are unused tables in the PegaRULES and PegaData schemas that can be cleaned up. Admin used the Optimize Schema tool to determine the tables that need to be cleaned up. After dropping all of the tables the schema identified, there are still 20 tables in the PegaRULES schema which should have been dropped as they are now part of the PegaData schema.
Steps to Reproduce
Complete a split schema upgrade using one database per the upgrade guide. You will end up with unused data tables in the PegaRULES schema and unused rules tables in the PegaData schema. Use the Optimize Schema tool to generate list of unused tables that can be cleaned up from both schemas. After applying this DDL the Optimize Schema tool no longer shows any tables that can be cleaned up but there are still unused tables in the PegaRULES schema.
The root cause of this problem is a defect in Pegasystems’ code/rules.
This issue is resolved through the following local change:
These additional 20 tables can be dropped from your rules schema as they are now located in the data schema.
0% found this useful