Pega Out Of place Upgrade - Data schema Rollback

General
, ,
1

We are working on out of place upgrade where we create new schemas for rules, data where we name them as Pegarules88, pegadata88 and old schema names are pegarules86 and Pegadata.

According to Pega’s documentation pegadata88 is a temporary schema which will be used during upgrade process and applications will point to Pegadata schema once upgrade is complete where as rules schema will be pegarules88.

The question I have is on rollback where I can point to old rules schema but can I point my application to upgraded pegadata schema? There are chances where pegadata schema might have got altered with new changes and if we point to old rules schema we expect the system not to behave accurately. is that assumption right?

Is restoring the pegadata schema from backup is the only option? I don’t see any documentation around the rollback on out of place upgrade. Please point me towards it if there are any.

2

@KarthickRajasingh We are working on a similar upgrade format for another application. Wondering the same exact thing. What happens to the data schema during that data only upgrade.

Is it safe to move back and forth between upgraded pegarules88 and old pega_rules schema with pega_data never being rolled back.

Is anyone able to expand upon this?

3

@SriHarsha Anika @PrakashKaragi

is this a question you could help with?

4

@KarthickRajasingh

Ideally, data schema is backward compatible. If there is sufficient testing performed and verified, upgrade data schema can be used with old rules schema.

However there is NO official document available which confirms backward compatibility of data schema, it is recommended to revert the database from backup.