Select to view content in your preferred language

ArcGIS Enterprise upgrade 10.7.1 to 10.9.1 - PostgreSQL version 10, which is not compatible with this version 12.4

2085
3
Jump to solution
06-08-2023 08:40 PM
dedimi
by
Occasional Contributor

I have ArcGIS Enterprise 10.7.1  with OS RHEL 7.9, planning to upgrade to 10.9.1.

As recommended at ESRI website, I started with upgrading Portal for ArcGIS which were 2 steps:

1. Running Portal for ArcGIS 10.9.1 installer silently - > succeeded.

2. Running the Portal upgrade silently -> failed.

The error message was : 'The data directory was initialized by PostgreSQL version 10, which is not compatible with this version 12.4.'

Appreciate any comment and feedback to resolve.

Thanks.

0 Kudos
1 Solution

Accepted Solutions
dedimi
by
Occasional Contributor

This is to update what I have done to resolve the issue.

First of all it's very important to have a back up or snapshots before proceeding to upgrade. In my environment each component of ArcGIS Enterprise is High Availability; Portal for ArcGIS, Web adaptor, ArcGIS Server as well as ArcGIS Datastore, in MS Azure Cloud, RHEL 7.9. OS.

After facing the above issue, I reverted back the VMs with snapshots, and then restarted the upgrade process. I found the issue was caused by the sequence was not in place, what I had done was to install and upgrade the Portal at once on one node first and then continue to the second node.

While the correct sequence is only to install the Portal on both nodes first, once complete then continue to upgrade them.

Following is the high level order of what I have done which was successfully upgrading ArcGIS Enterprise 10.7.1 to 10.9.1: (actually these steps are already mentioned on Esri Website as well)

1. To install the Portal 10.9.1 on both nodes first, once complete then continue to upgrade the portal on both nodes as well.

2. To uninstall ArcGIS Web Adaptor 10.7.1, and then to remove/un-deploy web adaptor for Portal as well as for Server directories in tomcat/webapps. After that to install Web Adaptor 10.9.1, and then deploy the generated arcgis.war file to tomcat/webapps folder for Portal web adaptor. Continue to run the script for configuring the web adaptor for Portal. Those processes done sequentially on each ArcGIS Web Adaptor node.

3. To install ArcGIS Server 10.9.1 and upgrade it at once on primary node and then continue to do the same on the second node.

4. Again to deploy the generated arcgis.war file (as result of installation process at step no 2) to tomcat/webapps folder and this time is for Web Adaptor for Server. Continue to run the script for configuring the web adaptor for Server. Those processes done sequentially on each ArcGIS Web Adaptor node.

5. To install ArcGIS Datastore 10.9.1 on all datastore nodes, once complete, and then configure it on each node.

Hope this is useful.

Cheers.

View solution in original post

0 Kudos
3 Replies
A_Wyn_Jones
Esri Contributor

Sounds like the upgrade may have failed - you can dig deeper into the logs located here <ContentDirectory>\arcgisportal\logs\database\pg_log

Hope this helps you find out what happened

"We've boosted the Anti-Mass Spectrometer to 105 percent. Bit of a gamble, but we need the extra resolution."
0 Kudos
dedimi
by
Occasional Contributor

Thanks  A_Wyn_Jones for replying.

following is the complete steps what I've done:

1. Installing Portal for ArcGIS 10.9.1 (OS RHEL 7.9)

dedimi_0-1686633781982.png

2. running upgradeportal and the error encountered.

dedimi_1-1686633887002.png

3. opening the pgsql.log

dedimi_2-1686633952598.png

2023-06-08 13:32:23 PDT: [25206]: FATAL: database files are incompatible with server
2023-06-08 13:32:23 PDT: [25206]: DETAIL: The data directory was initialized by PostgreSQL version 10, which is not compatible with this version 12.4.

I think this PostgreSQL version 10 was by default embedded in ArcGIS Enterprise 10.7.1 installation, and I think it should be covered or able to be handled during the upgrade process to ArcGIS Enterprise 10.9.1.

Any suggestion or feedback is appreciated. Thanks.  

0 Kudos
dedimi
by
Occasional Contributor

This is to update what I have done to resolve the issue.

First of all it's very important to have a back up or snapshots before proceeding to upgrade. In my environment each component of ArcGIS Enterprise is High Availability; Portal for ArcGIS, Web adaptor, ArcGIS Server as well as ArcGIS Datastore, in MS Azure Cloud, RHEL 7.9. OS.

After facing the above issue, I reverted back the VMs with snapshots, and then restarted the upgrade process. I found the issue was caused by the sequence was not in place, what I had done was to install and upgrade the Portal at once on one node first and then continue to the second node.

While the correct sequence is only to install the Portal on both nodes first, once complete then continue to upgrade them.

Following is the high level order of what I have done which was successfully upgrading ArcGIS Enterprise 10.7.1 to 10.9.1: (actually these steps are already mentioned on Esri Website as well)

1. To install the Portal 10.9.1 on both nodes first, once complete then continue to upgrade the portal on both nodes as well.

2. To uninstall ArcGIS Web Adaptor 10.7.1, and then to remove/un-deploy web adaptor for Portal as well as for Server directories in tomcat/webapps. After that to install Web Adaptor 10.9.1, and then deploy the generated arcgis.war file to tomcat/webapps folder for Portal web adaptor. Continue to run the script for configuring the web adaptor for Portal. Those processes done sequentially on each ArcGIS Web Adaptor node.

3. To install ArcGIS Server 10.9.1 and upgrade it at once on primary node and then continue to do the same on the second node.

4. Again to deploy the generated arcgis.war file (as result of installation process at step no 2) to tomcat/webapps folder and this time is for Web Adaptor for Server. Continue to run the script for configuring the web adaptor for Server. Those processes done sequentially on each ArcGIS Web Adaptor node.

5. To install ArcGIS Datastore 10.9.1 on all datastore nodes, once complete, and then configure it on each node.

Hope this is useful.

Cheers.

0 Kudos