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.
[java] Caused by: com.pega.pegarules.pub.database.DatabaseException: Unable to find the schema name for the connection to YOURDB: code: <none>
SQLState: Database-BadDBDef-Missing Message: madm
[java] Caused by: com.pega.pegarules.pub.database.BadDatabaseDefinitionException: Database-BadDBDef-Missing madm
[java] From: (A1B89B19B82F153E93720F4BC5CFCAF37)
[java] at com.pega.pegarules.data.internal.access.DatabaseConfigurationMap.getDBConfig(DatabaseConfigurationMap.java:144)
[java] at com.pega.pegarules.data.internal.access.ConnectionManagerImpl.getDBConfig(ConnectionManagerImpl.java:2746)
Steps to Reproduce
Design a database rule as JDBC in system, that is JDBC/yourDB.
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 setupDatabase.properties 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.