7.1.7 dataOnly upgrade failing with "prpc!BATCH" not found
Admin upgrading from Pega 6.3sp1 to 7.1.7 split schema
Rules upgrade has been completed with system.name set to prpc in setupdatabase.properties file.
Trying to run the data schema upgrade with system.name set to prpc but it is failing saying the prpc!BATCH requestor is not found.
[java] Caused by:
[java] com.pega.pegarules.pub.context.InvalidConfigurationException: Data-Admin-Requestor instance "prpc!BATCH" not found
[java] From: (B1471AC370E356805C142FEF5660D4052)
[java] at com.pega.pegarules.session.internal.authorization.SessionAuthorization.reset(SessionAuthorization.java:446)
[java] at com.pega.pegarules.session.internal.authorization.SessionAuthorization.<init>(SessionAuthorization.java:241)
[java] ... 59 more
Steps to Reproduce
run upgrade.sh dataOnly true
The root cause of this problem is software use/operation error. The data.schema.name property in setupDatabase.properties was not set to the database schema which contains the current data tables. For a split schema upgrade the original combined schema which has the 6.3sp1 versions of your rules and data tables will become the data schema of the 7.1.7 split schema configuration.
This issue is resolved by making the following change to the PRPC operating environment:
Updated data.schema.name=<Pega6.3sp1CombinedSchema> in setupDatabase.properties file and then run upgrade.sh with the dataOnly option.
Published January 31, 2016 - Updated October 8, 2020