Procedure to upgrade to Pega 7.1.8 without using deployment user
Pega 7.1.8 Upgrade Guide indicates that for an upgrade to a split schema on an Oracle database a deployment user is needed with DBA like privileges. The requirement is to upgrade without a deployment user.
The explanation for this behavior is as follows:
See the Pega 7.1.8 Upgrade Guide for further details on each of these steps. For this example the original combined 6.x schema which will become the new 7.1 data schema is called PEGA. The temporary rules schema is called RULES_TEMP and the new 7.1 rules schema is called V71RULES.
1. Migrate the rules tables from the combined 6.x schema to a new rules upgrade schema. pega.source.jdbc.username=PEGA pega.target.jdbc.username=RULES_TEMP.
2. Upgrade the rules schema which will involve schema changes to the rules schema and making dummy data tables within the rules schema in order to start the engine to run the upgrade. Used schema user for upgrade. pega.jdbc.username=RULES_TEMP, rules.schema.name=RULES_TEMP data.schema.name=RULES_TEMP.
3. a. Run migrate script to migrate rules tables back and create the rules objects and grants needed between rules and data schemas. pega.source.jdbc.username=RULES_TEMP pega.target.jdbc.username=V71RULES, pega.target.rules.schema=V71RULES, pega.target.data.schema=PEGA.
b. Manually apply generated SQL. There are statements that the rules schema cannot apply and others that the data schema cannot apply. Either divide the statements by schema user or have DBA apply entire SQL file.
4. Run the data schema upgrade which will involve schema changes to the data schema and upgrading the data schema. Since all of the grants were done in previous steps you can start the engine as the data schema user to run this upgrade. pega.jdbc.username=PEGA, rules.schema.name=V71RULES data.schema.name=PEGA
0% found this useful