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

Upgrade error "${}!BATCH" not found



Attempting to upgrade from PRPC 6.1 to Pega 7.1.8, the upgrade script encounters an error: Data-Admin-Requestor instance "${}!BATCH" not found

Error Messages Data-Admin-Requestor instance "${}!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.


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.


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