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

Update to 7.2.1 fails with BadDatabaseDefinitionException



Running update from 7.1.9 to 7.2.1 fails during "Upgrade Applications Schema" task because JDBC reference to an external database is unavailable during upgrade.

Error Messages

[java] Caused by: Unable to find the schema name for the connection to YOURDB: code: <none>
SQLState: Database-BadDBDef-Missing Message: madm
[java] Caused by: Database-BadDBDef-Missing madm
[java] From: (A1B89B19B82F153E93720F4BC5CFCAF37)
[java] at
[java] at

Steps to Reproduce

Design a database rule as JDBC in system, that is JDBC/yourDB.

Root Cause

The JDBC data source on the application server is not available during an update. The update should log that the data source is not available and continue instead of failing.


Perform the following local-change:
To skip this step, set update.applications.schema=false in the file or on the user interface. Run the update again.
After the update is complete, the Update Applications Schema utility can be run from prpcUtils or by directly starting the utility in the Pega 7 platform to update the cloned Rule, Data, Work, and Work history tables with the schema changes in the latest base tables.

Note: This issue is scheduled to be resolved in future release.
Suggest Edit

Published October 8, 2020

Did you find this content helpful? Yes No

Have a question? Get answers now.

Visit the Collaboration Center to ask questions, engage in discussions, share ideas, and help others.

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