Question
Maximus
US
Last activity: 7 Aug 2023 10:34 EDT
What is significance of temporary data schema in single out-of-place approach in 8.5
Hi Team,
We are planning to upgrade our pega application to 8.5.2 version(tomcat server,oracle database). While we were going through upgrade guide document, for single migration out-of-place approach, a temporary data schema creation step is introduced. Please find below statement copied from guide.
Upgrade guide: A temporary data schema (Dtmp) – a schema you create on the same database for temporarily staging the data during the upgrade. You discard this schema after the upgrade.
When we compare the section "Generating and applying DDL in an out-of-place upgrade for single migration", for the parameters we update in migrateSystem, setdatabase property files, we do not see that new "temporary data schema " mentioned any where in these two files.
Could you please help us understanding where this temp data schema is used and at which step. Please share more details.
Thanks
Deepa
Updated: 7 Jan 2021 2:23 EST
Citicorp Services India Private Limited
IN
Maximus
US
Hi GowriShankar,
Thank you for your response. We are currently upgrading our deployment manager pega version from 8.3.1 to 8.5.2.
After we migrate data from old rule schema to new rule schema, we modified setupdatabase properties file with following parameters. Generated scripts using generateddl.sh,applied manully and tried to run .upgrade.sh , then it was throwing attached error. Could you please share your input what is the issue with Datatmp schema which is introduced in 8.5. we have provided additional grants for DTmp schema for some data tables (pr_data_admin),but still did not work.
setupdatabase.properties:
rules.schema.name=New Rules Schema
data.schema.name=Temporary Data schema(DTmp)
bypass.pega.schema=true
bypass.udf.generation=true
rebuild.indexes=true
automatic.resume=true
Configured above parameters as per the below inputs from PDN article
To use the command line, configure the setupDatabase.properties file and run either upgrade.bat or upgrade.sh.
-
If you have not done so already, edit the
setupDatabase.propertiesfile.-
Open the
setupDatabase.propertiesfile in the scripts directory of your distribution image:Directories.distributionDirectory\scripts\setupDatabase.properties
-
Hi GowriShankar,
Thank you for your response. We are currently upgrading our deployment manager pega version from 8.3.1 to 8.5.2.
After we migrate data from old rule schema to new rule schema, we modified setupdatabase properties file with following parameters. Generated scripts using generateddl.sh,applied manully and tried to run .upgrade.sh , then it was throwing attached error. Could you please share your input what is the issue with Datatmp schema which is introduced in 8.5. we have provided additional grants for DTmp schema for some data tables (pr_data_admin),but still did not work.
setupdatabase.properties:
rules.schema.name=New Rules Schema
data.schema.name=Temporary Data schema(DTmp)
bypass.pega.schema=true
bypass.udf.generation=true
rebuild.indexes=true
automatic.resume=true
Configured above parameters as per the below inputs from PDN article
To use the command line, configure the setupDatabase.properties file and run either upgrade.bat or upgrade.sh.
-
If you have not done so already, edit the
setupDatabase.propertiesfile.-
Open the
setupDatabase.propertiesfile in the scripts directory of your distribution image:Directories.distributionDirectory\scripts\setupDatabase.properties -
Configure the connection properties. Use the new rules schema name for the Rules Schema Name and the temporary data schema for the Data Schema Name. Even if your system includes a separate customer data schema, leave it blank or use the temporary data schema name, it will be patched along with the original data schema in a later step.
-
Save and close the file.
-
-
Open a command prompt and navigate to the scripts directory.
-
Run either
upgrade.batorupgrade.sh.
Hi Deepa,
There won't be option to configure temporary data schema in both migratesystem.properties and setupdatabase.properties files. I believe the following steps will clarify your query.
Single out of place migration approach in 8.5.2.
1. Create new rules(Rnew) and data (Dtemp) in the existing oracle database. Assume the existing rules and data schema names are Rules and Data.
2. Migrate contents from existing rules and data schemas to newly created schemas.
Rules --> Rnew
Data --> Dtemp.
3. Perform in-place upgrade of newly created rules and data schema. (Rnew and Dtemp). Because there is no rules only upgrade option.
4. Migrate custom db objects (triggers, views, procedures ) from existing rules schema to new rules schema.
Rules --> (DB objects) -> Rnew.
5. Perform data only upgrade of existing data schema Data by configuring rule schema as Rnew and data schema as Data.
6. Reconfigure the application server to point to new rules schema Rnew and existing data schema Data.
7. Delete old rules schema Rules and temporary data schema Dtemp.
Thanks,