ArcGIS client and enterprise geodatabase compatibility depends on the ArcGIS and database releases used. When using different ArcGIS client and geodatabase versions, your database release must be supported by both the ArcGIS and geodatabase versions. See PostgreSQL database requirements for the ArcGIS client and geodatabase versions you want to use.
Note that if you create or upgrade a geodatabase from ArcGIS Pro, the version number stored in the geodatabase includes both the ArcGIS version and the ArcGIS Pro version. For example, if you create an enterprise geodatabase from ArcGIS Pro 2.2, the geodatabase version is 10.6.1.2.2.
The following summarizes which clients and geodatabases are interoperable:
10.2.x geodatabase | 10.3.x geodatabase | 10.4.x geodatabase | 10.5.x geodatabase | 10.6.x geodatabase | |
10.2.x client |
|
The DBMS must be PostgreSQL 9.1.14 or 9.2.9. |
The DBMS must be PostgreSQL 9.2.14. | ||
10.3.x client |
The DBMS must be PostgreSQL 9.1.14 or 9.2.9. |
|
The DBMS must be PostgreSQL 9.3.10 or 9.2.14. |
The DBMS must be PostgreSQL 9.3.13 or 9.4.8. | |
10.4.x client |
The DBMS must be PostgreSQL 9.2.14. |
The DBMS must be PostgreSQL 9.3.10 or 9.2.14. |
|
The DBMS must be PostgreSQL 9.3.13 or 9.4.8. |
The DBMS must be PostgreSQL 9.4.8. |
10.5.x client |
The DBMS must be PostgreSQL 9.3.13. |
The DBMS must be PostgreSQL 9.3.13 or 9.4.8. |
|
The DBMS must be PostgreSQL 9.4.8 or 9.5.3. | |
10.6, 2.0, 2.1, and 2.2 client |
The DBMS must be PostgreSQL 9.4.8. |
The DBMS must be PostgreSQL 9.4.8 or 9.5.3. |
|
Be aware that when you use clients that connect to an ArcGIS Server service, such as ArcGIS for iOS or ArcPad, ArcGIS Server is actually the client to the geodatabase. For these cases, make sure your ArcGIS Server and geodatabase versions are compatible.
Connecting from newer clients to older release geodatabases allows you to use the geodatabase without having to upgrade it at the same time the clients are upgraded. It also allows you to have mixed-release client installations at your site. For example, if one department uses a custom application that has not been updated to work with the latest ArcGIS client version, you can keep the geodatabase at the 10.4 release, keep this group of users on an older client release, and upgrade the clients for the rest of the agency to the current release. Keep in mind, though, that the current-release clients cannot use the latest geodatabase functionality until the geodatabase has been upgraded.
Note that if you create or upgrade a geodatabase from ArcGIS Pro, the version number stored in the geodatabase includes both the ArcGIS version and the ArcGIS Pro version. For example, if you create an enterprise geodatabase from ArcGIS Pro 1.3, the geodatabase version is 10.4.1.1.3.
Rules for mixed-release connections
Keep the following in mind when deciding whether to use mixed-release connections:
- When you make a connection from a newer client to an older enterprise geodatabase, you only have access to functionality that is available for the release of your geodatabase. This also applies to API functionality; if the functionality does not exist in the version of the geodatabase to which you want to connect, you cannot use the newer API function.
- To connect from an ArcGIS client to an older release enterprise geodatabase, the geodatabase has to be upgraded to the latest service pack or patch for its release. For example, if you want to connect from ArcGIS Server 10.4.1 to a 10.2.2 enterprise geodatabase, you must apply the most recent 10.2.2 patch to the geodatabase.
- While older ArcGIS client versions can open, query, edit, and save data in
newer release geodatabases, they cannot open datasets that participate in newer functionality and will encounter one of the following error messages when
trying to open one of these datasets:
- The version of the geodatabase client is incompatible with the dataset and cannot open it.
- Failed to add data, unsupported data type.
- You cannot open functionality specific to ArcGIS Pro inside ArcMap. For example, you cannot access geodatabases in SAP HANA or utility networks from ArcMap.