Question
De Volksbank NV
NL
Last activity: 7 Nov 2019 9:28 EST
Rule Schema Upgrade using the IUA ( Installation Upgrade Assistance)
I am trying to upgrade my application using the Out of place upgrade method with Single Migration. While using the IUA / Command prompt to upgrade (only the rule schema) what should be the input for the Data Schema Name ?
We use Split Schema. We have Pega Rules and Pega Data.
Below is the screenshot of the setupDatabase.properties file
Note : In IUA, the field for Data Schema Name is mandatory.
De Volksbank NV
NL
Thanks Kevin For the input.
We tried doing the upgrade using the new rule Schema name both as the Data Schema Name and Rule Schema Name. The upgrade process eventually failed creating Tables of Data Schema which was not supposed to be created on rule schema.
Example : OWNER_SSR.PR_INDEX_ACCESSGROUPROLES
De Volksbank NV
NL
We followed the aforementioned procedure and found the Tables of Data Schema were being created under the new rule schema. we are trying to do the rule schema upgrade only but i would like to know what value to pass for the DATA SCHEMA NAME
De Volksbank NV
NL
We use Split Schema. We have Pega Rules and Pega Data.
But running the script with DATA SCHEMA NAME and RULE SCHEMA NAME as the new rule schema creates unrequired Tables of Data Schema.
Proximus
BE
for now in your DB you've got
sourceDataSchema
sourceRulesSchema
targetRulesSchema: empty one for now, right?
you want to run migrate.sh to create the new target before the upgrade?
or you already did this step, you also executed upgrade.sh on targetRulesSchema and you're back on migrate.sh post upgrade?
De Volksbank NV
NL
1. Previously
We performed migration to targetRulesSchema. As Pega suggested for out of place upgrade, we only want to upgrade the rule schema first. Before running the upgrade script, we modified the setupDatabase.properties with following input :
Rule Schema Name : <target rule schema name>
Data Schema Name : <blank>
By default, Pega takes the name of the targetRulesSchema if the Data Schema name is kept blank. After the upgrade, we found that tables that belong to Data Schema were created in targetRulesSchema.
Note : We also tried to run the upgrade script keeping DATA SCHEMA NAME input commented. This resulted in failing of the upgrade as the DATA SCHEMA NAME input is mandatory.
2. Present Condition
We started from the beginning. We ran migrate.sh successfully and would like to upgrade the new rule schema only now. The targetRulesSchema is already migrated.
Query : What should be the input for the DATA SCHEMA NAME?
Proximus
BE
For the first upgrade.sh, I always put same value for both, ie, the RULES Schema name you want to upgrade.
I never let it blank.
Regards
Anthony
Pegasystems Inc.
US
Yes. During the upgrade of the rules schema it will create some dummy data tables in the rules schema. As a post upgrade step the guide tells you how to cleanup unused tables from the rules and data schemas.
Proximus
BE
I've not cleaned.
For deeper details on why are these tables are in RULES schema (actually both schemas), you'll need someone from PEGA :)
sorry
Regards
Anthony