Discussion
Accenture Services Pvt Ltd
IN
Last activity: 6 Apr 2018 19:26 EDT
Upgrade from PRPC6.3 SP1 to PRPC 7.1.8
We are upgrading our PRPC 6.3 SP1 environment to PRPC 7.18. We have one query regarding this.
1. PR_DATA_ADMIN - while upgrading from PRPC 6.3 to PRPC 7.1.8 using single schema to Split schema method, where do we need to keep the table PR_DATA_ADMIN? In Rules schema or Data schema? And why?
Kindly let us know the details as sonn as possible.
**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.
Pegasystems Inc.
The PR_DATA_ADMIN table would be part of Rules schema. During Migrating the Rule tables for split-schema upgrade, this table would be also part of Rules Schema. Because during the upgrade process the PRPC engine would be brought up multiple times and hence it requires the data admin table.
NIIT Technologies Limited
AU
PR_DATA_ADMIN table will be part of rules schema when upgrading new rules schema. This is needed to bootstrap the upgrade process.
migrate.bat utility takes care of moving required list of tables to a particular schema.
Accenture
IN
Then why in fresh/new 7.X installation, PR_DATA_ADMIN stay in the data schema?
I think during upgrade process PR_DATA_ADMIN shd be migrated to rules schema, but after when the upgrade done, the PR_DATA_ADMIN of the data schema (old 6.x schema) get used, hence no matter if you drop the table from the rules schema.
I have tested this and it is working
Regards
Shankha
Pegasystems Inc.
IN
NIIT Technologies Limited
AU
Yes.
When you do rules schema upgrade in split schema mode, data schema will not be available to upgrade process. Thats the reason PRPC copies pr_data_Admin table from data to rules schema only for upgrade process.
pr_data_admin table in data schema gets upgraded seperately when you do standalone data schema upgrade.