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 failed



The script fails with errors during DataOnly upgrade during the Out-of-Place upgrade from v5.5 to v7.1.5

Error Messages pyVTable-RuleNotFound-NoMatches RULE-OBJ-ACTIVITY PZUPGRADEDATASCHEMA Pega-Landing-System-Upgrade 1 The 1 rules named 'PZUPGRADEDATASCHEMA' defined in the rulebase are: 
[java] 1 related to applies-to class 'Pega-Landing-System-Upgrade', but were defined in rulesets which are not in your rulesetlist: 'Pega-LP-SystemSettings:07-10-01'. 

Steps to Reproduce

run --dataOnly true

Root Cause

If you are running RULE or DATA upgrade part of Update documentation using deployment user with DBA type privileges as specified in the installation/upgrade guide, the process fails if synonyms exist on tables such as pr4_base in schemas other than the one that is being upgraded. 


This issue is resolved through the following local change: Instead of directly upgrading PRPC 5.5 to a split-schema Pega 7.1.5, upgrading it to a single-schema 7.1.5 first, then run the script to split the schema as described in the SA-1916.

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