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 process to 7.1.6 fails with errors in upgrade logs



User has observed multiple errors in the log file and the upgrade process has stopped while inserts were attempted on tables that are defined in the DATA schema but the SQL was attempting in the RULES schema.

Error Messages

ORA-00942: table or view does not exist
[java] From: (A7878B7E0F9E7507494FE02A8BD79F2E0)
[java] SQL: INSERT INTO ACE_RULES.pr_sys_updatescache (pzClearCacheType, pzCreateDateTime, pzNodeName, pzSystemName, pzObjClass, pzKeyString, pzParameters) VALUES (?, sysdate, ?, ?, ?, ?, ?)

Steps to Reproduce

Upgrade PRPC 6.1 SP2 to 7.1.6 application using split-schema approach.

Root Cause

During the upgrade process, user has incorrectly configured the user details and has set bypass.pega.schema as TRUE in the file which should be left blank.

Additionally, user has not configured the '-dataOnly TRUE' argument while running the\Upgrade.bat file to upgrade the Data schema. This has caused duplicate tables, procedures of the RULES schema, created in the DATA schema.


User has re-run the upgrade process with correct set of configurations and upgrade options. To clean-up unused tables, refer the installation guide, Clean Up Unused Tables section.


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