Postgres 13/sde 11/arcgis 10.7 "i" tables are not getting created

[ashizzle]

Copying feature class in arc catalog 10.7 (or python) results in a sql error.

ERROR 000210: Cannot create output C:\Users\xxx\AppData\Local\Temp\wutwygwb.zuu.sde\table
DBMS table not found [ERROR: relation "test.i7253" does not exist
LINE 1: INSERT INTO test.i7253 (id_type, base_id, num_ids, last_...
^::SQLSTATE=42P01] [db.test.table]
DBMS table not found
Failed to execute (FeatureClassToFeatureClass).

It looks like when it's trying to create this table, the accompanying "i" table is not being created before the insert happens.

When the same command is run through arcpro, it works smoothly as expected.

I realize that officially arcgis 10.7 does not support postgres 13 (https://desktop.arcgis.com/en/system-requirements/10.7/database-requirements-postgresql.htm), but was wondering if anyone had any insight into this.

[MarceloMarques]

Hello,

As you indicated PostgreSQL 13 is not supported nor certified with ArcGIS Desktop 10.7 - ArcMap & ArcCatalog.

PostgreSQL database requirements for ArcGIS 10.7.x and ArcGIS Pro 2.3 and 2.4—System Requirements | ...

ArcGIS Desktop 10.8.2 is the last release, ArcGIS Desktop is deprecated, and users need to move to ArcGIS Pro.

ArcMap Life Cycle | Esri Support
ArcMap Continued Support (esri.com)

ArcGIS Desktop 10.8.2 does not support PostgreSQL 13.

PostgreSQL database requirements for ArcGIS 10.8.x and ArcGIS Pro 2.5, 2.6, and 2.7—System Requireme...

FAQ: What PostgreSQL Database Versions Are Supported by ArcGIS Enterprise and ArcGIS Pro? (esri.com)

• Support for PostgreSQL13 was only added with the release of ArcGIS 10.9.1 / 2.9.
• This means PostgreSQL 13 is supported and certified starting with ArcGIS Pro 2.9 and ArcGIS Enterprise 10.9.1.
• Thus, we cannot use PostgreSQL 13 with ArcGIS Desktop 10.7 / 10.8.2 and expect it to work, it is not a supported/certified configuration.
• We need use PostgreSQL 13 with ArcGIS Pro 2.9 or higher 3.0 / 3.1
• if we try to use PostgreSQL 13 with ArcGIS Pro 2.8, 2.7, 2.6, ... then we might also encounter issues, it is not a supported/certified configuration.

I hope this clarifies your question.

[MarceloMarques]

Client and geodatabase compatibility—ArcGIS Pro | Documentation

"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.

This is especially true when you use a mix of client versions at your site. A newer client can create newer dataset types in the geodatabase that older clients cannot access. For enterprise geodatabases, waiting too long between geodatabase upgrades may mean you have to upgrade the underlying database more than once before you can upgrade the geodatabase."

Caveat: example, if using ArcGIS Pro 3.1 then upgrade the Enterprise Geodatabase ArcSDE Repository with Pro 3.1, this will bring the Geodatabase Version to 11.1.0.3.1, we also need to plan to upgrade to ArcGIS Enterprise 11.1 the companion release of ArcGIS Pro 3.1, and we also need to keep the RDBMS version updated to a version that is supported and certified with the Geodatabase Version that we are using.

FAQ: What PostgreSQL Database Versions Are Supported by ArcGIS Enterprise and ArcGIS Pro? (esri.com)