Question
Pegasystems Inc.
JP
Last activity: 11 Jul 2019 2:57 EDT
Out-of-place with single migration upgrade
Hi,
Currently I am conducting upgrade Pega Platfrom from 7.4 to 8.2.1 following the upgrade guide (https://community.pega.com/knowledgebase/documents/pega-platform-82-upgrade-guide-apache-tomcat-and-postgresql). I am trying "out-of-place upgrade with single migration (page 31 - 37)" but I am finding the guide a bit hard to follow.
Currently I have "rules" and "data" schema in my working 7.4 environment. Additionally I have created a "newrules" schema in the same database for migration.
Question:
#1. In "Migrating the rules schema with one database" section (page 33), what should I enter for source schema and target schema?
#2. In "Upgrade methods for the migrated rules schema" section (page 34), what should I enter for Rules schema and Data schema in IUA (I am not taking command line upgrade approach)?
#3. In "Upgrading the data schema" section (page 37), what should I enter for rules schema and data schema for setupDatabase.properties file? Why should we do upgrade twice by different tools and what is the exact difference between #3 and #2?
I made my best guess but it ended up with "newrules" schema being 314 tables which is too much for ootb tables (rules tables are 210 in 7.4, and 239 in 8.2.1) and I guess I made a mistake on what to set for schema. Please advise.
Thanks,
Pegasystems Inc.
IN
Hi Tsuchihashi,
#1. In "Migrating the rules schema with one database" section (page 33), what should I enter for source schema and target schema?
When you are migrating, you are just shifting the data in schema to a new schema(new rules).
pega.source.rules.schema=Your current rules schema name.
pega.source.data.schema=Your current data schema name.
pega.target.rules.schema= Newly created rules schema name(new rules)
#2. In "Upgrade methods for the migrated rules schema" section (page 34), what should I enter for Rules schema and Data schema in IUA (I am not taking command line upgrade approach)?
after migrating, you will upgrade the new rules schema, So, the values for Rules schema is 'New Rules'
and the data schema value need not be changed, since data is not getting upgraded in this step.
Data schema name is 'your current data schema name'
Hi Tsuchihashi,
#1. In "Migrating the rules schema with one database" section (page 33), what should I enter for source schema and target schema?
When you are migrating, you are just shifting the data in schema to a new schema(new rules).
pega.source.rules.schema=Your current rules schema name.
pega.source.data.schema=Your current data schema name.
pega.target.rules.schema= Newly created rules schema name(new rules)
#2. In "Upgrade methods for the migrated rules schema" section (page 34), what should I enter for Rules schema and Data schema in IUA (I am not taking command line upgrade approach)?
after migrating, you will upgrade the new rules schema, So, the values for Rules schema is 'New Rules'
and the data schema value need not be changed, since data is not getting upgraded in this step.
Data schema name is 'your current data schema name'
#3. In "Upgrading the data schema" section (page 37), what should I enter for rules schema and data schema for setupDatabase.properties file? Why should we do upgrade twice by different tools and what is the exact difference between #3 and #2?
After upgrading the rules in 'new rules' schema, you have to upgrade data schema to upgrade the data and to make the data schema point to new rules schema.
The schema name is 'new rules' schema
Data schema name is 'your current data schema'
After this, both the rules and data schema will be updated.
let me know if you have any queries.
Pegasystems Inc.
JP
Hi Sravani,
Thanks for your response. I have "rules" and "data" in my existing 7.4 working environment and created a new blank schema named "newrules". Here are the steps I went through.
#1. "Migrating the rules schema with one database" section (page 33)
I have modified .\scripts\migrateSystem.properties as below.
pega.source.rules.schema=rules
pega.source.data.schema=data
pega.target.rules.schema= newrules
I think I did the same as you described. And, after this step, 55 tables got created in "newrules" schema.
#2. "Upgrade methods for the migrated rules schema" section (page 34)
I entered "newrules" for Rules schema and "data" for Data schema as below screen shot.
I think I did the same as you described. And, after this step, tables in "newrules" schema increased up to 314 from 55. This schema now includes both rules & data tables. (Is this really correct? Isn't this step supposed to upgrade rules schema? My expectation was something like 75 instead of 314.)
Hi Sravani,
Thanks for your response. I have "rules" and "data" in my existing 7.4 working environment and created a new blank schema named "newrules". Here are the steps I went through.
#1. "Migrating the rules schema with one database" section (page 33)
I have modified .\scripts\migrateSystem.properties as below.
pega.source.rules.schema=rules
pega.source.data.schema=data
pega.target.rules.schema= newrules
I think I did the same as you described. And, after this step, 55 tables got created in "newrules" schema.
#2. "Upgrade methods for the migrated rules schema" section (page 34)
I entered "newrules" for Rules schema and "data" for Data schema as below screen shot.
I think I did the same as you described. And, after this step, tables in "newrules" schema increased up to 314 from 55. This schema now includes both rules & data tables. (Is this really correct? Isn't this step supposed to upgrade rules schema? My expectation was something like 75 instead of 314.)
#3. "Upgrading the data schema" section (page 37)
I have modified .\scripts\setupDatabase.properties as below.
rules.schema.name=newrules
data.schema.name=data
I think I did the same as you described. And, after this step, tables in "data" schema increased up to 247 from 212.
Now, instruction ends. The rest of step is to edit Tomcat's context.xml to replace the current "rules" schema with "newrules". Is that right? If so, newrules now contains too many unnecessary tables and that has to be cleaned up. As I stated above (#2), tables in "newrules" are now as many as 314. But of course it is too much, because ootb tables in data schema in 8.2.1 is 239. 2 tables are additional in my custom application, so it has to be 241 at end of upgrade process. Not 314.
Thanks,
Pegasystems Inc.
IN
Hi Tsuck,
After you are done with the steps, you need to update prconfig file of the server.
I am not sure about the number of tables in the new rules schema. Some tables might be added because of the upgrade.
Pegasystems Inc.
JP
>After you are done with the steps, you need to update prconfig file of the server.
No, to change the schema name you need to modify context.xml in Tomcat, not prconfig.xml or DSS.
>I am not sure about the number of tables in the new rules schema. Some tables might be added because of the upgrade.
Well this was all about my question. We can't have duplicate whole data tables (more than two hundred) in newrules schema for no use. Actually even number of tables in data are also different from what it is supposed to be with new installation. If, there are unknown tables created that no one knows, the upgrade process is defective.
Thanks,