Discussion
pc_assign_worklist,workbasket,pc_data_uniqueID in Pega Rules schema post Upgrade
We have done upgrade of a 6.2 application to 7.1.7 Split Schema using Upgrade scripts provided. Post upgrade we observed that in Pega Rules schema we are seeing some tables like pc_assign_worklist ,pc_assign_workbasket, pc_data_uniqueid, pc_link_attachment etc. Is this expected behavior and we should remove them post upgrade using Optimize Schema?
**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.
We have used Optimize Schema and got rid of few tables like these post upgrade. But what I wanted to check was why they were getting generated in Pega Rules schema in first place. We have observed this trend in couple of projects and wanted to check if this is an issue with migration scripts or if we are doing something incorrectly.
Assuming you are performing a split schema out-of-place upgrade in your projects.
This could occur if we have specified the following properties incorrectly in the upgrade process.
@ migrateSystem.properties
- pega.target.rules.schema=NEW_P7_RULES_SCHEMA
- pega.target.data.schema=EXISTING_P6_SINGLE_SCHEMA
@ setupDatabase.properties
- rules.schema.name=NEW_P7_RULES_SCHEMA
- data.schema.name=EXISTING_P6_SINGLE_SCHEMA
Post split schema upgrade these 4 tables should be in your data schema and not in the rules schema.
You could certainly use the optimize schema wizard to drop them from your rules schema.