We are upgrading single schema to split schema from PRPC6.3 SP1 to PRPC7.1.8. Have one query
If we made changes (added columns) in the pega out of box rules tables, then while upgrading Rules schema will here be any error? Is there any steps we need to follow in such scenarios where we have added columns in pega rules out of box tables?
**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.
If you have added any new columns are extended the existing column sizes in PRPC 6.3 for the respective tables it will be carry forwarded to Pega 7. However for new introduced tables these new columns and changed columns won't be applied automatically and your need to carry forwarded manually.
For example if you have added 2 columns to pr4_rule table in PRPC 6.3, after upgrade those 2 new columsn will be availble in PR4_RULE table after Pega 7 upgrade, however there are new tables like PR4_RULE_FIILE_BINARY are added in Pega 7 which will copy the respective binary rules from PR4_RULE table to PR4_RULE_FILE_BINAY table and it may fail due to new columns or column size changes wont be availble for PR4_RULE_FILE_BINARY table.
1. Do you have new table list which has been added in PRPC 7 and the dependencies of those on the PRPC6.3 tables? Like the same you gave an example that pr4_rules and pr4_rule_file_binary.
2. Also in case we have changes in PR4_RULE table then what should be our approach of upgrade as while running upgrade it will fail because our changes will not be available in PR4_RULE_FILE_BINARY? what step we need to follow?
This will help us to understand the impact in our environment.
unfortunately I do not have the new tables which are added in Pega 7 compare to PRPC 6.3. The table list will vary from the verion you are upgradding from to Pega7.
The easy way is before you start an upgrade after migrate run the generateDDL utility on the rules schema and verify the create table statemetns and add all your customizations to those new rule tables.
You can apply these changes on the rule schema and when you are running the upgrade you can turn off the schema changes flag in setupdatebase.properteis file by chaging the "bypass.pega.schema=true".