Question
TCS
IN
Last activity: 7 Aug 2023 10:33 EDT
Failed system startup after upgrade to 8.6.1
In-Place Upgrade is successful for 8.6.1 through IUA, using Tomcat server and Postgres DB. The Bypass Automatic DDL Application was cleared and Update applications schema, Update existing applications and Rebuild database indexes were selected during the Upgrade. But post upgrade the system is not starting. The prweb.war file has been replaced with the one shipped with the 8.6 package. Attaching the logs here.
Couple of logs that stood out were -
1. Encountered bad Data-Admin-DB-Name definition
2. Failed to perform ClosePrprivateJar cleanup, Shutting down cluster provider: HazelcastEmbeddedClusterProvider
Saw an article on similar issue but its for Oracle Db. Is there anything similar for Postgres?
Citicorp Services India Private Limited
IN
Hi @AparnaGopakumar,
I have reviewed the attached logs. The following support article should help here.
https://community.pega.com/support/support-articles/upgrade-fails-application-schema-upgrade-step
Thanks,
Updated: 8 Oct 2021 7:46 EDT
TCS
IN
Hi @GOWRISHANKAR,
The mentioned article encountered error while upgrading and setupDatabase.properties file was updated to run the upgrade again. In my case, upgrade has completed. Should I make these changes are do an upgrade again? The application schema and application have been updated in the previous run.
TCS
IN
Hi @GOWRISHANKAR,
I took care of the second error - Failed to perform ClosePrprivateJar cleanup, Shutting down cluster provider: HazelcastEmbeddedClusterProvider - by upgrading HazelCast
For the first error - Encountered bad Data-Admin-DB-Name definition - deleted the rogue record from pr_base table of the database. Is there any config file (like contect.xml or any such) that has to be updated?