Select to view content in your preferred language

ArcGIS Server SDE Datastore connection forward compatibility

1295
3
Jump to solution
11-26-2023 01:22 PM
MarekSambor
New Contributor

Hi,

I have ArcGIS Enterprise servers in versions 10.9.1 and 11.2.0 that are connected to the same SDE Oracle Geodatabase.

I'm planning to upgrade the SDE EGDB to version 11.2.

Is it necessary to upgrade all ArcGIS Server (Enterprise) nodes to version 11.2, or is it not obligatory? Will registered Datastore SDE connections still work when connecting from ArcGIS Server 10.9.1 to a Geodatabase in version 11.2?

Let's assume that Oracle clients will be upgraded to be compatible with Oracle 19c.

Thanks!

 

0 Kudos
1 Solution

Accepted Solutions
Scott_Tansley
MVP Regular Contributor

It's a bit more of a story than just geodatabase version to ArcGIS Server version.  There's the whole driver, and database version thing to consider as well.

10.9.1 - https://enterprise.arcgis.com/en/system-requirements/10.9.1/windows/database-requirements-oracle.htm

11.2 - https://enterprise.arcgis.com/en/system-requirements/latest/windows/database-requirements-oracle.htm 

Fortunately for you, both support 19c!  🙂

You also need to consider support for drivers, which I don't think will be an issue here.

You also need to consider what versions of ArcGIS Pro you are using and their support to that database version and geodatabase version.

Geodatabase now offer a degree of forward/backward compatibility.  It used to be that you kept them at the lowest common denominator.  There also used to be a matrix saying exactly what GDB versions were supported by application version.  Now the 'advice' is stay as close as you can.

Obviously, if you use a 11.2 GDB with 10.9.1 then 10.9.1 will not be able to use any new functionality in there.

You also need to consider if you're using advanced types, like Parcel Fabrics or Utility Models.  In those situations, I believe there are strong rules about Pro versions being matched to Enterprise versions, being matched to EGDB version and possibly even database versions.  

Quite a bit to consider, sorry if I've muddied the waters.

 

Scott Tansley
https://www.linkedin.com/in/scotttansley/

View solution in original post

3 Replies
Scott_Tansley
MVP Regular Contributor

It's a bit more of a story than just geodatabase version to ArcGIS Server version.  There's the whole driver, and database version thing to consider as well.

10.9.1 - https://enterprise.arcgis.com/en/system-requirements/10.9.1/windows/database-requirements-oracle.htm

11.2 - https://enterprise.arcgis.com/en/system-requirements/latest/windows/database-requirements-oracle.htm 

Fortunately for you, both support 19c!  🙂

You also need to consider support for drivers, which I don't think will be an issue here.

You also need to consider what versions of ArcGIS Pro you are using and their support to that database version and geodatabase version.

Geodatabase now offer a degree of forward/backward compatibility.  It used to be that you kept them at the lowest common denominator.  There also used to be a matrix saying exactly what GDB versions were supported by application version.  Now the 'advice' is stay as close as you can.

Obviously, if you use a 11.2 GDB with 10.9.1 then 10.9.1 will not be able to use any new functionality in there.

You also need to consider if you're using advanced types, like Parcel Fabrics or Utility Models.  In those situations, I believe there are strong rules about Pro versions being matched to Enterprise versions, being matched to EGDB version and possibly even database versions.  

Quite a bit to consider, sorry if I've muddied the waters.

 

Scott Tansley
https://www.linkedin.com/in/scotttansley/
MarceloMarques
Esri Regular Contributor

Client and geodatabase compatibility—ArcGIS Server | Documentation for ArcGIS Enterprise

Geodatabase and ArcGIS releases

You do not have to keep your geodatabase and ArcGIS clients at the same release, but it is recommended that you do so. Geodatabases and client software are designed to work together, and if you let one get too many releases away from the other, you risk encountering problems or unexpected behavior. ( read more in the link above !!! )

ArcGIS 11.2 and ArcGIS Pro 3.2 requirements for Oracle—ArcGIS Enterprise | Documentation for ArcGIS ...

| Marcelo Marques | Esri Principal Product Engineer | Cloud & Database Administrator | OCP - Oracle Certified Professional | "In 1992, I embarked on my journey with Esri Technology, and since 1997, I have been working with ArcSDE Geodatabases, right from its initial release. Over the past 32 years, my passion for GIS has only grown stronger." | “ I do not fear computers. I fear the lack of them." Isaac Isimov |
0 Kudos
MarceloMarques
Esri Regular Contributor

community.esri.com

Mapping and Charting Solutions (MCS) Enterprise Databases Best Practices

How to Move the Oracle Enterprise Geodatabase with the Oracle Data Pump Utility
Oracle eGDB SDE Repo Upgrade Using Oracle Restore Point | Download PDF Version
| Marcelo Marques | Esri Principal Product Engineer | Cloud & Database Administrator | OCP - Oracle Certified Professional | "In 1992, I embarked on my journey with Esri Technology, and since 1997, I have been working with ArcSDE Geodatabases, right from its initial release. Over the past 32 years, my passion for GIS has only grown stronger." | “ I do not fear computers. I fear the lack of them." Isaac Isimov |