SA-17455

Summary

Attempting to upgrade from PRPC 6.1 to Pega 7.1.8, the upgrade script encounters an error: com.pega.pegarules.pub.context.InvalidConfigurationException: Data-Admin-Requestor instance "${current.system.name}!BATCH" not found

Error Messages

com.pega.pegarules.pub.context.InvalidConfigurationException: Data-Admin-Requestor instance "${current.system.name}!BATCH" not found

Steps to Reproduce

1. Run the installer
2. Supply a DBA user/password and two schemas, for split-schema approach
3. Choose to do rulebase cleanup

Root Cause

A software use or operation error.  The correct procedure for upgrading from a single 6.x to split 7.x environment was not being followed.

Resolution

Here’s the explanation for the reported behavior: 

Admin was attempting to upgrade from a single to split schema directly instead of following the 4 step process outlined in the Pega 7.1.x Upgrade Guide.

In general this is the process for upgrading from a single to split schema using one database.
 

1. Migrate 6.x rules tables to new schema
2. Upgrade new rules schema.  Dummy data tables created in rules schema as part of upgrade step.
3. Generate the rules schema objects, grant privileges between new rules and data schema.
4. Upgrade data schema
5. Post upgrade steps to run additional upgrade scripts, cleanup unused tables from rules and data schemas

Another option would be to upgrade to a single schema and then use the migrate script to split the upgrade schema into 2 schemas.  With this approach the post upgrade steps are still needed.