nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Adding time estimates to Upgrade

MichaelBartlett

I recently upgraded from 2024.1.1 to 2025.0.1.

It would not connect to the database. After several retries I found out the upgrade was updating some Integer to BIGINT datatypes. I understand it may be hard to estimate the actual time, but it seems like you could check the count of records it was going to update and at least display a message if it is anticipated to take a long time.

Also I found no mention of this in the installation instructions, just a heads up would be nice or some indication it was actually doing something.

Find more posts tagged with

Status: Open

Comments

jawhitacre@PA.LCL_PAGame

To add to the discussion here...we were on 2024.x and had the INT/BIGINT issue come up (we think...it is the only thing that makes sense). The Esri Support Documentation for BUG-000175372 was not available (we were getting a 404 error; also see the All Observers Stopped Reporting Metrics in Monitor 2024.1.1 post), so we weren't sure what to do, but then found this in the ArcGIS Monitor 2025.0 Release Notes:

BUG-000175372: ArcGIS Monitor deployments can stop persisting metric data after several consecutive years

After upgrading to 2025.0.1, we experienced about 1.5 hours of post-upgrade time for the PostgreSQL to do it's thing. We watched Task Manager and saw PostgreSQL processes spinning up and down and watched to see when ArcGIS Monitor had consistent activity (it will spin up and down a few times...then have a big spike at the end and then stay consistent).

We are monitoring a total of 16 hosts, consisting of 2 Web Adaptors, 2 Portals, 6 ArcGIS Servers, 2 ArcGIS Data Stores, 3 SQL Servers, and the ArcGIS Monitor machine. And have been monitoring those machines for just over a year.

The upgrade appears to have fixed the INT/BIGINT issue. Hope this helps!

SusanHmel__DOIT_

I ran into this during our upgrade and didn't realize it was doing post-installation steps in the database until I found this post. I had already restarted the server, Postgres service, and AGM service a few times and waited a while (24 hrs+) trying to get things running again with no luck.

I finally found in the postgres logs that the DB was running out of disk space on the server and was failing after about 30 minutes of trying the schema updates. We doubled the disk space and restarted and AGM came back up pretty quickly, upgrade in place.

We had previously applied the fix for BUG-000175372 (the BIGINT fields in the tables) back in July 2025.

I agree, some additional documentation or messaging about the schema updates timing would be helpful, or, in my case, notification of the postgres errors that were occuring and caused the schema update to fail.

Timothy

We applied the INT to BIGINT fields fix in 2024 under the direction from esri support. I wonder if the upgrade process will handle this appropriately or not. Waiting for 2025.1 before upgrading.

JamesBrattonVHB

I had a similar experience. ArcGIS Monitor install said it was done, but Monitor said it could not connect to the database. I checked again several times. Over 24 hours later, it started working. I found out that it was still upgrading after Esri Support asked me to check the database. The following query returned 2 rows instead of 12.

SELECT id, name from agm_schema where name LIKE '%2025%';

ChrisTaylor2

I JUST got past this exact issue this afternoon with the help of Support after over a week of troubleshooting. I couldn't figure out why my 2025.0.1 upgrade wasn't completing successfully after trying it several times. It turns out that the database portion of the upgrade took 1h 45m to complete! I didn't even know that was part of the process and had just been expecting it to be ready once the Server install was done, then assumed there was some other issue with the install when I hit the 'Configure Database' screen.