Discussion
Pegasystems Inc.
IN
Last activity: 6 Apr 2018 19:26 EDT
Upgrade in Production when having Oracle Synonyms
Hi,
The application is having the PegaRULES schema in Oracle and has synonyms for each of the Pega DB object. The upgrade approach performed in the sand-box / Dev is in-place upgrade first and later split the schema.
In the Production should we repeat the process of performing in-place upgrade and then a split?
Or, if we do a lift-shift then will dataOnly upgrade be successful considering it having synonyms?
**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.
Paypal Inc
IN
You can follow the below approach in this scenario.
- Lift and shift the rules schema from lower environments
- Perform the Data Only upgrade with Rules Schema (shifted from lower env) and with actual data schema (do not give synonym user schema)
Mindtree
IN
Did we go for an in-place upgraded initially due to presence of synonyms, or it was the approch that was decided for some other reason. I am trying to understand why did we prefer in place upgrade here.
Paypal Inc
IN
According to Pega upgrade guide (preparing your database section), prior to split schema upgrade, synonyms have to be dropped.
If synonyms cannot be dropped for any particular reasons like enterprise compliance, in-place upgrade can be performed pointing to the synonym user