topic Re: Cluster Postgres anomaly pg_dist_node in ArcGIS Pro Questions

Cluster Postgres anomaly pg_dist_node

Oiligriv — Tue, 02 Aug 2022 14:14:27 GMT

Hello

we are experiencing an anomaly during the creation of an Enterprise GeoDB on a PostgreSQL Cluster.

the PostgreSQL version is 12

The ArcGIS Pro version is 3.0

the ST_Geometry file we are using is the following. "ArcGISPro_30_ST_Geometry_PostgreSQL_182272"

during creation the Pro writes a log reporting this SDE DBMS Error: -37 ERROR: relation "pg_dist_node" does not exist

from my information, the PostgreSQL cluster configuration uses for the HA pgpool2 version 4.3.2.

how can we create the GeoDB Enterprise correctly?

Attached is the Pro log

Re: Cluster Postgres anomaly pg_dist_node

Zagorki — Tue, 23 Aug 2022 19:40:51 GMT

I am having a very similar issue with Pro 3.0 and an AWS Postgres RDS with PostGIS. Did you get this resolved?

Re: Cluster Postgres anomaly pg_dist_node

imranrajjad_cc — Tue, 07 Mar 2023 13:18:23 GMT

Was anyone able to solve this?

I am having same issues

File: C:\Users\azure\AppData\Local\Temp\2\ArcGISProTemp4800\sde_setup.log
Mode:
GMT Time: 2023-03-07T06:38:30+00.00
Local Time: 2023-03-07T06:38:30+00:00
--------------------------------------------------------------------

[06:38:30.854] Connection to database 'arcgis_db_dev' failed.
[06:38:31.096] ev.SQLstate = 42P01
SDE DBMS Error: -37 ERROR: relation "pg_dist_node" does not exist
LINE 1: SELECT nodename FROM pg_dist_node LIMIT 1
^
[06:38:33.256] Connected RDBMS instance is setup for PostGIS spatial type configuration.
Creating cloud base PostGIS-only geodatabase.

[06:38:33.347] VERSION table created...
[06:38:33.349] COORDINATE_SYSTEMS table being created...
[06:38:33.386] COORDINATE_SYSTEMS table created...
[06:38:33.389] SPATIAL_REFERENCES table being created...
[06:38:33.494] SPATIAL_REFERENCES table created...
[06:38:33.500] LAYERS table being created...
[06:38:33.551] LAYERS table created...
[06:38:33.554] METADATA table being created...
[06:38:33.586] METADATA table created...
[06:38:33.588] RASTER_COLUMNS table being created...
[06:38:33.626] RASTER_COLUMNS table created...
[06:38:33.632] TABLE_REGISTRY table being created...
[06:38:33.677] TABLE_REGISTRY table created...
[06:38:33.680] STATES table being created...
[06:38:33.734] STATES table created...
[06:38:33.737] VERSIONS table being created...
[06:38:33.799] VERSIONS table created...
[06:38:33.803] MVTABLES_MODIFIED table being created...
[06:38:33.828] MVTABLES_MODIFIED table created...
[06:38:33.830] STATE_LINEAGES table being created...
[06:38:33.892] STATE_LINEAGES table created...
[06:38:33.898] LOCATORS table being created...
[06:38:33.941] LOCATORS table created...
[06:38:33.944] XML tables being created...
[06:38:34.122] Warning: Error querying tsearch2 system table schema. You will
need to grant select access to public to pg_ts_cfg,pg_ts_cfgmap
pg_ts_dict,pg_ts_parser for xml functionality
[06:38:34.122] XML tables created...
[06:38:34.128] COLUMN_REGISTRY table being created...
[06:38:34.174] COLUMN_REGISTRY table created...
[06:38:34.177] ARCHIVES table being created...
[06:38:34.217] ARCHIVES table created...
[06:38:34.220] LAYER_STATS table being created...
[06:38:34.254] LAYER_STATS table created...
[06:38:34.256] BRANCHES table being created...
[06:38:34.343] BRANCHES table created...
[06:38:34.345] BRANCH_TABLES_MODIFIED table being created...
[06:38:34.373] BRANCH_TABLES_MODIFIED table created...
[06:38:34.375] MULTIBRANCH_TABLES table being created...
[06:38:34.413] MULTIBRANCH_TABLES table created...
[06:38:34.416] TABLES_LAST_EDIT_TIME table being created...
[06:38:34.470] TABLES_LAST_EDIT_TIME table created...
[06:38:35.021] LOGFILE_POOL tables being created...
[06:38:35.054] LOGFILE_POOL tables created...
[06:38:35.057] DBTUNE table being created...
[06:38:35.111] DBTUNE table created...
[06:38:35.114] SERVER_CONFIG tables being created...
[06:38:35.145] SERVER_CONFIG tables created...
[06:38:35.147] S_get_functions_release prepare error.
[06:38:35.147] DBMS stored procedures being created or updated...
[06:38:39.331] DBMS stored procedures created or updated...
[06:38:47.330] TABLES_LAST_EDIT_TIME table registered as hidden...
[06:38:47.331]
Successfully installed ArcSde.

File: C:\Users\azure\AppData\Local\Temp\2\ArcGISProTemp4800\sde_setup.log
Mode:
GMT Time: 2023-03-07T06:38:48+00.00
Local Time: 2023-03-07T06:38:48+00:00
--------------------------------------------------------------------

[06:38:48.326] Successfully created GDB_Tables_Last_Modified table...
[06:38:50.086] Successfully created GDB_Items table...
[06:38:50.984] Successfully created GDB_ItemRelationships table...
[06:38:51.523] Successfully created GDB_ItemTypes table...
[06:38:52.268] Successfully created GDB_ItemRelationshipTypes table...
[06:38:52.702] Successfully created GDB_ReplicaLog table...
[06:38:53.196] Successfully created GDB_Locks table...
[06:38:53.489] Successfully created GDB_Conflicts table...
File: C:\Users\azure\AppData\Local\Temp\2\ArcGISProTemp4800\sde_setup.log
Mode:
GMT Time: 2023-03-07T06:38:47+00.00
Local Time: 2023-03-07T06:38:47+00:00
--------------------------------------------------------------------

File: C:\Users\azure\AppData\Local\Temp\2\ArcGISProTemp4800\sde_setup.log
Mode:
GMT Time: 2023-03-07T06:38:55+00.00
Local Time: 2023-03-07T06:38:55+00:00
--------------------------------------------------------------------

File: C:\Users\azure\AppData\Local\Temp\2\ArcGISProTemp4800\sde_setup.log
Mode:
GMT Time: 2023-03-07T06:52:54+00.00
Local Time: 2023-03-07T06:52:54+00:00
--------------------------------------------------------------------

File: C:\Users\azure\AppData\Local\Temp\2\ArcGISProTemp4800\sde_setup.log
Mode:
GMT Time: 2023-03-07T11:58:22+00.00
Local Time: 2023-03-07T11:58:22+00:00
--------------------------------------------------------------------

[11:58:22.455] ev.SQLstate = 42P01
SDE DBMS Error: -37 ERROR: relation "pg_dist_node" does not exist
LINE 1: SELECT nodename FROM pg_dist_node LIMIT 1
^
[11:58:22.476] ev.SQLstate = 42501
SDE DBMS Error: -25 ERROR: must be owner of database sde
[11:58:22.476] DB_instance_open() LIBPQ connect error: -25
[11:58:22.476] Error: Underlying DBMS error (-51).
[11:58:22.477] Error: DB_arcsde_setup: Unable to connect
[11:58:22.477] DBMS error (-25)
[11:58:22.478] ERROR installing/upgrading ArcSDE, Error = -51
File: C:\Users\azure\AppData\Local\Temp\2\ArcGISProTemp4800\sde_setup.log
Mode:
GMT Time: 2023-03-07T12:51:51+00.00
Local Time: 2023-03-07T12:51:51+00:00
--------------------------------------------------------------------

[12:51:51.388] ev.SQLstate = 42P01
SDE DBMS Error: -37 ERROR: relation "pg_dist_node" does not exist
LINE 1: SELECT nodename FROM pg_dist_node LIMIT 1
^
[12:51:51.400] ev.SQLstate = 42501
SDE DBMS Error: -25 ERROR: must be owner of database sde
[12:51:51.400] DB_instance_open() LIBPQ connect error: -25
[12:51:51.400] Error: Underlying DBMS error (-51).
[12:51:51.400] Error: DB_arcsde_setup: Unable to connect
[12:51:51.400] DBMS error (-25)
[12:51:51.401] ERROR installing/upgrading ArcSDE, Error = -51

Re: Cluster Postgres anomaly pg_dist_node

tempRodrigo_DaSilva — Tue, 06 Jun 2023 19:35:40 GMT

Hellou guys, did you manage to solve this. I'm having the same problem mentioned by @Oiligriv

Re: Cluster Postgres anomaly pg_dist_node

RachaelHarbes — Thu, 28 Mar 2024 16:51:09 GMT

We are seeing a similar issue with our postgres/sde. Was this ever resolved?

Re: Cluster Postgres anomaly pg_dist_node

JVig — Mon, 29 Apr 2024 18:04:37 GMT

I too am having this problem, but it does not appear it has been resolved.

Re: Cluster Postgres anomaly pg_dist_node

RachaelHarbes — Tue, 30 Apr 2024 12:44:29 GMT

I wonder if anyone ever looks at these post. I often see issues similar to mine with no resolution.

Re: Cluster Postgres anomaly pg_dist_node

JVig — Wed, 01 May 2024 16:02:57 GMT

My hope is that with enough activity someone will realize it's a problem ha. But in all honesty, it's a confusing error. Their instructions for creating a cloud based SDE: Create a geodatabase on Amazon RDS for PostgreSQL or Aurora PostgreSQL—ArcGIS Enterprise in the cloud | Documentation for ArcGIS Enterprise

suggest you only need the PostGIS extension to run the DB, but then when I try to enable the db (step 11) I get the error:

,EXT_ERROR1 = ERROR: type "st_geometry" does not exist
LINE 1: ALTER TABLE sde.gdb_items ADD Shape ST_GEOMETRY

Which I think may be caused by the error we are discussing in this thread (which also shows up in my setup.log file).

Re: Cluster Postgres anomaly pg_dist_node

ShaunGibbins — Wed, 02 Jul 2025 11:35:46 GMT

Same behaviour here, we have postgresql 16 without st_geometry added, we can connect to it and create a new geo enterprise database from pro selecting postgis instead of st_geometry and we can create feature classes but we get lots of similar errors in the logs despite everything seeming to work.

2025-07-02 10:57:13.590 BST [3079] ERROR: relation "sde.sde_spatial_references" does not exist at character 15
2025-07-02 10:57:13.590 BST [3079] STATEMENT: SELECT * FROM sde.sde_spatial_references LIMIT 0
2025-07-02 10:57:13.612 BST [3079] ERROR: function sde.st_geometry_release_installed() does not exist at character 8
2025-07-02 10:57:13.612 BST [3079] HINT: No function matches the given name and argument types. You might need to add explicit type casts.
2025-07-02 10:57:13.612 BST [3079] STATEMENT: select sde.st_geometry_release_installed()
2025-07-02 10:57:13.637 BST [3079] ERROR: relation "sde.sde_logfiles" does not exist at character 29
2025-07-02 10:57:13.637 BST [3079] STATEMENT: SELECT logfile_data_id FROM sde.SDE_logfiles LIMIT 0
2025-07-02 10:57:13.645 BST [3079] ERROR: relation "pg_temp_10.sde_logfiles" does not exist at character 29
2025-07-02 10:57:13.645 BST [3079] STATEMENT: SELECT logfile_data_id FROM pg_temp_10.SDE_logfiles LIMIT 0

Re: Cluster Postgres anomaly pg_dist_node

George_Thompson — Wed, 02 Jul 2025 11:49:03 GMT

Here is another post related to those log file entries: https://community.esri.com/t5/arcgis-enterprise-portal-questions/datastore-missing-table-sde-logfiles/m-p/1613615