We executed Rule upgrade while upgrading from 5.5 to 7.1.9 through Upgrade.sh script by updating the setupdatabase properties and giving New Rule schema name in both Rule and Data schema paramter of setupdatabase property because in the Upgrade guide it was mentioned to give both as New rule schema name. But we obeserved that all Data schema tables got created in Rule schema. We are not sure whether this is expected behaviour of Upgrade. Also, Upgrade guide asked to give Rule schema name in Both Data and Rule schema of setupdatabase property hence we did the same. Please adivse if this is the correct process and approach we are following.
This is expected behavior. Rulebase upgrade adds all the tables during upgrade. After completing all the steps of upgrade and bringing up the system these extra tables can be dropped by using optimize schema wizardd
We are using Appendix-c approach for our Pega 7 Upgrade. As part of Data Schema upgrade (step-4) we have generated DDL's (4a). (Page No. 138/145 )
We are not using deployment user instead we used DATA user. Generated script contains RULE schema statements. So we separated them and executed from RULE schema and rest of the DDL applied on DATA schema.
We would like to know whether this is correct approach or not? Please advise.
This comment has been branched out as a new node and the new thread can be followed here
Posted: 5 years ago
Posted: 19 May 2017 0:27 EDT
Dhevendra Earva (earvd)
Director, Cloud Engineering