Select to view content in your preferred language

Error connecting to DB after 2024.0 upgrade

1603
18
Jump to solution
08-27-2024 02:27 PM
WhitneyLoy
Regular Contributor

Getting the following error after upgrading to 2024.0.  The Database is not ready. Database schema not up to date

I have tried restarting both the ArcMonitor and PostgreSQL service and reinstalling the update and the same error is occurring.

 

1 Solution

Accepted Solutions
GeoJosh
Esri Regular Contributor

Hi everyone. The development team has identified the issue and provided the solution to Esri Support. I also want to provide the solution here for those who are comfortable running SQL commands against PostgreSQL databases. If you do not have experience administering PostgreSQL, please reach out to Esri Support for help performing this workflow.

The cause of this issue is the presence of empty Analysis Views or Analysis Views that only contain Header elements. The solution to this issue is to remove all empty Analysis Views and restart the ArcGIS Monitor Server process.

If you have already rolled back to a previous release, you can simply delete any empty Analysis Views through the web GUI and then re-run the upgrade. If your ArcGIS Monitor installation is stuck in the state described in this post, you can manually delete the Analysis Views from the database. To do so:

  1. Stop the ArcGIS Monitor Server service.
  2. Connect to the ArcGIS Monitor database in pgAdmin.
  3. Open a new query window.
  4. Issue this query: SELECT * FROM ANALYSES
  5. Take a CSV backup of the results.

GeoJosh_2-1725378007247.png

6. Delete any row where the expressions array under the configuration column is empty or is missing entirely. For example, a row with the configuration object below would be deleted, because the expressions array is [] (empty):

GeoJosh_3-1725378085739.png

7. Start the ArcGIS Monitor Server service and try accessing the application again. If the problem persists, please reach out to Esri Support for further troubleshooting.

Alternatively, a patch that addresses this issue will be available in the coming weeks.

Josh

View solution in original post

18 Replies
EdenPunter
Occasional Contributor

Same issue in my organization after upgrading. Have restarted the ArcGIS Monitor Server and PostgreSQL services also.

NicholasEverdell
Occasional Contributor

We are also seeing this error after upgrading from 2023.1 in our environment.

BrendaButton
Emerging Contributor

Our 2023.1 Environment is also experiencing these issues.

GeoJosh
Esri Regular Contributor

Hi @WhitneyLoy and @EdenPunter,

Are you also upgrading from 2023.1 --> 2024.0 or are you upgrading from another version? Dev team is investigating.

Thanks,

Josh

0 Kudos
WhitneyLoy
Regular Contributor

@GeoJosh  CORRECTION I am upgrading from 2023.3.1

0 Kudos
EdenPunter
Occasional Contributor

@GeoJosh upgrading from 2023.3.1

0 Kudos
Joshua-Young
Frequent Contributor

I am getting the same error message. Upgrading from 2023.3.1 to 2024.0.

"Not all those who wander are lost" ~ Tolkien
0 Kudos
BrendaButton
Emerging Contributor

My department is also upgrading from 2023.3.1, apologies

0 Kudos
RexNeville
Occasional Contributor

No one should use Monitor 2024.0 it has other bugs with no patch released. wait for 2024.1.

0 Kudos