Production Upgrade Approach Challenge
Issue Description:
We have upgraded our environment from Pega 62sp2 to Pega7.2 . We have upgraded from single schema to split schema in our lower environments.
We are planning to perform the upgrade on our Production environment.
We have current schema of Pega62sp2 lets say (rule+data) "X".
We will be planning to push the upgrade onto new schemas DataSchema "Y" and rule schema "Z".
Post upgrade onto production the environment will be tested for stability for a week. During that week the users will continue to use Pega62sp2 (schema "X").
Once we get a sign off on Upgraded environment we will require to move the delta transaction data which was created by user on previous week from schema "X" onto the new split schema "Y" and "Z".
Could you please suggest what's the best way to move the delta from single schema onto split schema ?
Would you recommmend anyother approach for PROD upgrade?
Database: Oracle 11g
Webserver: Apache
Appserver: Tomcat
Server OS: Linux
***Updated by Moderator: Marissa to move to Pega 7 Upgrade Center from Product Support Community***
**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.
TAL
AU
If the delta in V6 is transaction data (case and related data), you could think of moving the work object and related information (assignment/ attachment/ history etc.) using package work wizard.
You may also think about migrating the delta using in SQL statements.
Pegasystems Inc.
IN
We do not recommend to run Pega 7 and Pega 6 in parallel because identifying the delta records will be very difficult. Package work wizard will not package any Queue items including SLA items.
JP Morgan
US
Hi Devendra,
The straight forward approach to address the production upgrade scenario we have would be as follows:
- Perform the upgrade with new schemas say Y(new data schema) and Z(new rule schema)
- Smoke test for the specified period of time. (a week or two)
- Cleanup the new data schema (Y).
- Perform the DataOnly upgrade from X (Pega 62sp2 schema [rule + data]) onto Y(New Data Schema)
Validate your new environment and sunset the older environment
Please share your thoughts on this ?
Let us know if anything we need to take care during the above process.
Pegasystems Inc.
IN
only thing which need to be consider is you can't migrate any cases created/processed during smoke test in schema X to Schema Y (data schema). Also you have to make sure that there are no new deployments are happening in Pega 6 during this pilot period.
JP Morgan
US
Hi Devendra,
There will be no deployments on Pega 6 environment. The only point being the delta which gets created on X (Pega6 schema) when Pega7 is being smoke tested will be moved after a week by running data only upgrade step.
Do you see any challenge with this ?
Pegasystems Inc.
IN
After smoke test is done , if you are performing the data only upgrade on Pega 6 schema pointing to Pega7 rules schema will not cause any issues(Assuming that you are discarding the Pega7 smoke tested data schema) .
But the data created during the smoke test period on Pega 7 data schema will be lost.