Skip to main content

This content is closed to future replies and is no longer being maintained or updated.
Links may no longer function. If you have a similar request, please write a new post.

Question

 Chandramouli Mukherjee (Chandramouli.M)
AI4Process

AI4Process
GB
Chandramouli.M Member since 2021 18 posts
AI4Process
Posted: Mar 7, 2018
Last activity: Apr 17, 2018
Posted: 7 Mar 2018 6:12 EST
Last activity: 17 Apr 2018 1:25 EDT
Closed
Solved

Upgrade/Update Pega Data Schema

We are planing to update from Pega 7.1.5 version to Pega 7.3.1 version. I am looking for following information -

During In-Place Update process of Data schema using following script -

./update.sh --dataOnly true

(A) what is/are the change(s) this script exactly make in existing Data Schema(of Pega 7.1.x version), so that it updated to Pega 7.3.1 Data Schema?

(B) Does this script make any change in DDL level ( e.g. - change definition of any table, view, trigger or any other database element) ? Or it changes at DML level (e.g. - add/modify/delete any extra row in any ).

(C) There are multiple Data Schema for different applications, do we need to update all of them separately? My understanding is - we have to update them individually, because our application is using classes mapped to some tables which reside on other Data Schema. Please confirm.

(D) There are few additional schema, some of the Pega classes are mapped to tables reside in this schema. Do I need to update them as well? My understanding is - we have to update these database schema as well. Please confirm.

Note -

1. Current Configuration -

OS - Red Hat Linux Server v6.5

Application Server - Oracle Weblogic Server 12c

Datbase Server - Oracle 12c R1 Enterprise DB Server ( Proprietary information hidden)

Database - Split Schema.

2. I do not have any update.sh script for reference, so that I can check from the script.

Thanks in advance for suggestion and help.

To see attachments, please log in.
Updates

Accepted Solution

Posted: 6 years ago
Posted: 13 Apr 2018 2:52 EDT
Dhevendra Earva (earvd)
PEGA
Senior Director of Cloud Engineering
Pegasystems Inc.
IN

Please find the answers

A) what is/are the change(s) this script exactly make in existing Data Schema(of Pega 7.1.x version), so that it updated to Pega 7.3.1 Data Schema?

This will not touch customer case objects 

(B) Does this script make any change in DDL level ( e.g. - change definition of any table, view, trigger or any other database element) ? Or it changes at DML level (e.g. - add/modify/delete any extra row in any ).

Yes it will make the DDL changes. This apply for only Pega OOTB shipped tables and all the changes are additive no deletes

(C) There are multiple Data Schema for different applications, do we need to update all of them separately? My understanding is - we have to update them individually, because our application is using classes mapped to some tables which reside on other Data Schema. Please confirm.

Show More

Please find the answers

A) what is/are the change(s) this script exactly make in existing Data Schema(of Pega 7.1.x version), so that it updated to Pega 7.3.1 Data Schema?

This will not touch customer case objects 

(B) Does this script make any change in DDL level ( e.g. - change definition of any table, view, trigger or any other database element) ? Or it changes at DML level (e.g. - add/modify/delete any extra row in any ).

Yes it will make the DDL changes. This apply for only Pega OOTB shipped tables and all the changes are additive no deletes

(C) There are multiple Data Schema for different applications, do we need to update all of them separately? My understanding is - we have to update them individually, because our application is using classes mapped to some tables which reside on other Data Schema. Please confirm.

Do you have multiple data schemas? I am not sure how that is configured. Could you please provide more details on what those multiple data schemas contains.

Generally there is one rules schema and one data schema (which includes OOTB pega shipped data schema tables). You can have multiple application specific schemas which holds work tables not Pega tables.

(D) There are few additional schema, some of the Pega classes are mapped to tables reside in this schema. Do I need to update them as well? My understanding is - we have to update these database schema as well. Please confirm.

Please clarify whether you have any OOTB shipped data schema related tables in those additional schema. If not then you no need to upgrade them separately.


Show Less
To see attachments, please log in.
Posted: 6 years ago
Posted: 13 Apr 2018 5:25 EDT
Chandramouli Mukherjee (Chandramouli.M)
AI4Process

AI4Process
GB

Thanks a million for your response.

For my Question (C) and (D) - there is no OOTB shipped data schema related tables in those additional schema. Hence, I understand - we do not need to upgrade them separately. 

To see attachments, please log in.
Posted: 6 years ago
Posted: 17 Apr 2018 1:25 EDT
Dhevendra Earva (earvd)
PEGA
Senior Director of Cloud Engineering
Pegasystems Inc.
IN

You no need to run the data schema upgrade seperately for other dedicated work schemas. However after upgrade is completed then there is a Upgrade->Application Schema Wizard landing page that will help you identify any new columns are added to OOTB pc_work and data related tables that need to be added your application specific tables,

To see attachments, please log in.

We'd prefer it if you saw us at our best.

Pega Collaboration Center has detected you are using a browser which may prevent you from experiencing the site as intended. To improve your experience, please update your browser.

Close Deprecation Notice