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

Reverse script fails with an error

SA-97769

Summary



The system is upgraded from Pega Platform 7.3.1 to Pega Platform 8.2.1 using the out-of-place Upgrade process. The Reverse script fails with an error.


Error Messages



Verify ML Reversal Readiness:
This Reversal requires distribution image of 08-02-03, but found 08-02-02



Steps to Reproduce

  1. Upgrade Pega Platform 7.3.1 to Pega Platform 8.2.1
  2. Configure setupDatabase.properties with PEGARULES and Reverse_timestamp.xml.
  3. Run reverse.sh from Pega Platform 8.2.1 installer.


Root Cause



This behavior is as per Pega product design.

For more information, refer to: https://community.pega.com/knowledgebase/documents/pega-platform-82-upgrade-guide-apache-tomcat-and-postgresql



Resolution



Here’s the explanation for the reported behavior:

The Reverse script must be used only to reverse patch release updates and not the full platform version updates.  That is, the user can reverse Pega Platform 8.2.1 to Pega Platform 8.2; but cannot reverse Pega Platform 8.2.1 to Pega Platform 7.3.1 using this script.

In order to reverse the upgrade to what is required, backup the database from before the upgrade. Since the user is already on a split schema and would have the rules schema intact to revert, data schema must be backed up before starting the dataOnly upgrade (if the user required a method to revert the version back for any reason).

Published February 10, 2020 - 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