Discussion
upgrade PRPC6.3 SP1 to PRPC 7.1.8 general query
Hi,
We are upgading from PRPC6.3 SP1 to PRPC 7.1.8 single schema to split schema and have few queries regarding this.
1. what the dataOnly upgrade process does? What changes it used to do in the schema?
2. We have seen, in dataOnly upgrade process doesnot make any changes in the custom application specific tables. Why is so?
3. Few columns has ben added in PRPC7.1.8 which was not there in PRPC 6.3. Do we need to manually add those columns (like PXCOMMITDATETIME/PXSAVEDATETIME)? Any other steps we need to follow for custom application tables apart of columns addition? Will there be any impact if we don't add those columns?
Kindly suggest.
**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.
1. what the dataOnly upgrade process does? What changes it used to do in the schema?
DataOnly upgrade is used to upgrade only data schema. It ignores the ant targets related to rules schema upgrade. For example - Load engine, Rules Upgrade, etc.
2. We have seen, in dataOnly upgrade process doesnot make any changes in the custom application specific tables. Why is so?
Because Pega doesn't want to touch customer created objects. Also, Pega will not have any information related to custom database objects, so upgrade process cannot generate DB scripts to update application specific tables. After upgrade process is done, run Optimize schema wizard which shows the list of missing indexes, columns and tables to create them.
3. Few columns has ben added in PRPC7.1.8 which was not there in PRPC 6.3. Do we need to manually add those columns (like PXCOMMITDATETIME/PXSAVEDATETIME)? Any other steps we need to follow for custom application tables apart of columns addition? Will there be any impact if we don't add those columns?
Missing columns must be added for the application to run properly. If columns are missing in Pega shipped tables, Pega upgrade process will take care of it. For custom tables, run Optimize schema wizard post upgrade.