Skip to main content

This content has been archived and is no longer being updated. Links may not function; however, this content may be relevant to outdated versions of the product.

Support Article

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 set to prpc in file.

Trying to run the data schema upgrade with set to prpc but it is failing saying the prpc!BATCH requestor is not found.

Error Messages

[java] Caused by:
[java] Data-Admin-Requestor instance "prpc!BATCH" not found
[java] From: (B1471AC370E356805C142FEF5660D4052)
[java] at com.pega.pegarules.session.internal.authorization.SessionAuthorization.reset(
[java] at com.pega.pegarules.session.internal.authorization.SessionAuthorization.<init>(
[java] ... 59 more

Steps to Reproduce

run dataOnly true

Root Cause

The root cause of this problem is software use/operation error.  The property in 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<Pega6.3sp1CombinedSchema> in file and then run with the dataOnly option.

Published January 31, 2016 - Updated October 8, 2020

Was this useful?

0% found this useful

Have a question? Get answers now.

Visit the Collaboration Center to ask questions, engage in discussions, share ideas, and help others.

Did you find this content helpful?

Want to help us improve this content?

We'd prefer it if you saw us at our best.

Pega Community has detected you are using a browser which may prevent you from experiencing the site as intended. To improve your experience, please update your browser.

Close Deprecation Notice
Contact us