Question
Mindtree
IN
Last activity: 24 Jun 2024 9:49 EDT
Pega Upgrade to Infinity 24
As part of our Pega upgrade implementation we are moving from Version 7.2.2 to infinity 24. The Client application being upgraded is highly critical application and cannot go down in production. Client team had the following ask:
Is it possible for us to upgrade it to have upgraded schema available before production deployment window (can be fresh instance or upgraded data schema) and then move all the inflight cases thorough golden gate replication or any other way of converting in flight data from version 7.22 format to infinity 24 format and keep replicating it so that we save the time required for data only upgrade during upgrade window and we just switch it during deployment window.
Accepted Solution
Updated: 24 Jun 2024 9:49 EDT
Pegasystems Inc.
IN
@ChetanNaik Upgrade from 7.22 to infinity 24 is a major change, which also requires underlying infrastructure change. Specific to data-upgrade phase, as per my knowledge, it is not possible to sync changes, due to changes in table structure between source Pega 722 data schema and target infinity 24 data schemas.
Some amount of downtime is must. Below steps can be considered to reduce the downtime requirement in data-upgrade step.
1. Generate and apply data-upgrade DDLs before downtime.
2. Disable "Upgrade application schema" and perform this post upgrade from dev studio.
3. Provide additional resources to database ( CPU cores and RAM)
These needs to be tested before implementing to validate the downtime requirement.