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

Pega 7.4 upgrade fails at Update Existing Applications stage

SA-66765

Summary



Pega 7.4 upgrade fails at the 'Update Existing Applications' stage with an error.


Error Messages



[java] [ ] [STANDARD] [ ] [ ] (_Landing_System_Upgrade.Action) INFO - Update Wizard is done!
[java] [ ] [STANDARD] [ ] [ ] (internal.util.UpdateWizard) INFO - Upgrading customer application schema.
[java] [ ] [STANDARD] [ ] [ ] (ternal.store.DataSourceManager) ERROR - Unable to obtain DataSource for jdbc/MyDataSource
[java] [ ] [ STANDARD] [ ] [ ] (etier.impl.EngineStartup) WARN - PegaRULES shutdown initiated.



Steps to Reproduce

  1. Upgrade Pega 7.2 to Pega 7.4.
  2. Run the Pega in-place upgrade.


Root Cause



A defect in Pegasystems’ code or rules.
The application has an external datasource, jdbc/MyDataSource, with classes in Pega which point to tables in the database. The Update script must skip these references; however, it attempts to process them.


Resolution



Perform either of the following local-changes:
  1. Remove the Data-Admin-DB-Name rule with jdbc/MyDataSource reference.
  2. Remap the tables to PegaRULES
  3. Run the migrate and upgrade scripts of the rules schema objects and the rest of the upgrade steps.
  4. Post upgrade, reinstate the deleted rule and update the table mappings.
If required, replace the data source reference in Data-Admin-DB-Name rule jdbc/MyDataSource with a JDBC URL connection.

For more information, refer to: https://community.pega.com/support/support-articles/database-general-unable-obtain-data-source

Alternatively, since the 'Update Existing Applications' step that the in-place upgrade fails on, can be performed as a post-processing step, another option is to bypass the step during the upgrade. Perform the step after the upgrade when the jdbc/MyDataSource is available on the application server or specified using a URL in prpcUtils.

Published April 3, 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