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

Issues while upgrading from Pega 5.4 to Pega 7.4



Invalid Identifier exception occurs while upgrading PRPC 5.4 to Pega 7.4.

Error Messages

[java] User ID: (unknown)

     [java] Last SQL: SELECT pxInsName as "product", pySetting as "pySetting" FROM PEGARULE_LSP_OWNER.pr_data_admin WHERE pxObjClass = 'Data-Admin-Product' AND pxProductName = 'PegaRULES Process Commander' ORDER BY pxCreateDateTime DESC

     [java] java.sql.SQLSyntaxErrorException: ORA-00904: "PYSETTING": invalid identifier

Steps to Reproduce

  1. Set up the database user with appropriate roles and privileges.
  2. Execute the script for rules only. The execution fails with an error.

Root Cause

While processing the upgrade step, in the, both the rules.schema and the data.schema must be set to the new rules schema.
The rules.schema was set to the new rules schema, while the data.schema was set to the old_single_schema.


Perform the following local-change:

Setup as below


Perform either of the following to move the entire data to a new database server (both schemas):
  • Migrate the entire data to the new database and then perform the upgrade.
  • Upgrade the current environment and then use the migrate.bat or to migrate to the new database server.

Published August 19, 2019 - Updated December 2, 2021

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