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 script failure with Pega 7.1.6



User ran the upgrade shell script for 7.5 hours to upgrade from PRPC 6.2 SP2 to Pega 7.1.6 and then it failed with "Error: Failed to save page: Database-BadTableMapping-KeyPropertyTooBig "

Error Messages

Error: Failed to save page: Database-BadTableMapping-KeyPropertyTooBig

Steps to Reproduce

Run single schema upgrade from PRPC 6.2 SP2 to Pega 7.1.6.

Root Cause

The root cause of this problem is software use or operation error. When creating private synonyms to work around an Oracle issue, the synonym was created incorrectly, that lead to the wrong table being used.


Perform the following local-change step to the PRPC operating environment:

Recreate the private synonyms, and then run the script to continue the upgrade.

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