Question
TCS
GB
Last activity: 27 Sep 2016 7:44 EDT
Procedures and Views are invalidated when moving into higher environments for upgrade - Life & Shift approach
We are moving from QA to NFT environment as part of Upgrade Route to Live with Life & Shift approach. Our upgrade is Pega 6.1SP2 to 7.2
I copied the Pega 6 NFT schema into Pega 7 NFT Data Schema and Pega 7 QA Rule Schema into Pega 7 NFT Rules Schema.
We are planning to do the Data Only Upgrade. This only would update the Data schema to be compatible with Pega 7.
However, in the cloned NFT Pega 7 Rules schema, I see the following Stored Procedures and Views referring the source QA Schemas
Views:
PWBV4_CIRCUMSTANCE_DUPLICATES
PWBV4_RULE_LOCKING
PWBV4_RULE_OVERRIDES
Stored Procedures:
sppr_aggregate_usage
sppr_sys_statusnodes_set
sppr_sys_updatescache_flush
I believe the above need to be recreated in NFT Rules Schema with the appropriate schema. Or Is there any other way ?
- Am I missing any views & stored procedures in Rule Schema that ought to be rectified ?
- Apart from Views & Stored Procedures, Is there any other DB objects in Rules schema that ought to be rectified ?
Pegasystems Inc.
US
Also if you are using database specific tools to copy the upgraded rules to higher environment instead of using the migrate script that comes with the media you will need to truncate the pr_data_products and pr_data_restore tables in the rules schema of the higher environment. If you do not truncate these tables you may see an issue with the dataOnly upgrade or even if you do not see an issue on that step you will see issues installing, committing, and rolling back hot fixes in the higher environment. If you use the migrate script it will take care of the truncating for you and as was previously pointed out will also allow you to recreate the rules schema objects and make the connections between the rules and data schemas.