Datastore. Missing table sde_logfiles

[PatricWiström]

Hi!

We are having some problems with datastore in our 11.3 Enterprise environment. In the postgres-logfile it constantly complains about not finding the table sde_logfiles. I can confirm that the table does not exist in the schema where it is supposed to be. The schema is the managed username for the relational data store.

"ERROR: relation "hsu_xxxxx.sde_logfiles" does not exist at character 29"
"STATEMENT: SELECT logfile_data_id FROM hsu_xxxxx.SDE_logfiles LIMIT 0"

Every 3-5 second this gets logged.

When comparing with our test-environment the table does exist in that schema and there is no error-messages in the log-file.

Anyone has an idea? Thanks in advance!

[DenisPithon]

Hi,

Same error here (PostgreSQL 15, ArcGis 11.3 Enterprise)

ERROR: relation "xyz.sde_logfiles" does not exist at character 29
STATEMENT: SELECT logfile_data_id FROM xyz.SDE_logfiles LIMIT 0

any ideas ?

Hace a good day.

Denis

[George_Thompson]

Those tables are probably system tables created by the datastore, especially if someone creates a selection with a hosted layer.

See this doc for more information on log files in PostgreSQL (go to the very bottom of the page): https://pro.arcgis.com/en/pro-app/latest/help/data/geodatabases/manage-postgresql/geodatabase-system...

I think behind the scenes, the datastore is an enterprise geodatabase managed by your Enterprise deployment.

I think that some of those messages are more red-herring and not an issue.

You can reach out to support and see if there is something else they may know about.

[RiceAdam]

@George_Thompson Is there any answers to this issue before I open a ticket?

I too am getting the issue on PROD for an 11.3 AWS multi-machine HA setup.

XXXXXreader@xyzxy:[2836]:STATEMENT:  SELECT logfile_data_id FROM XXXXXreader.SDE_logfiles LIMIT 0

ERROR:  relation "pg_temp_16.sde_logfiles" does not exist at character 29

HINT:  No function matches the given name and argument types. You might need to add explicit type casts.

ERROR:  relation "pg_dist_node" does not exist at character 22

ERROR:  relation "sde.sde_spatial_references" does not exist at character 15

STATEMENT:  SELECT * FROM sde.sde_spatial_references LIMIT 0

 @ShaunGibbins - Did you figure anything out?

[WoutervanderHulst]

@RiceAdam Did you find any reason/solution for the logs? Also having them on 11.3 ArcGIS Datastore

[RiceAdam]

Nope - bumped the RDS nodes to r8g on AWS to compensate aka "throw more resources at it". Our errors aren't coming from the Datastore either but an attached relational database.

Checking now and it's an ongoing ERROR within the RDS. If I had to hazard a guess, it seems related to the nightly refresh on Services and can also occur during a patch/outage. It may be a red herring like @George_Thompson suggests, but it's also a new ERROR in ESRI Enterprise (didn't not occur pre-10.9.1/11.3).

Ref:

[George_Thompson]

@RiceAdam I do not have any updates and would recommend working with technical support on this.

It is possible that these are logged but red herrings.

[RClavero]

Hello all, by any chance does anyone has more information on it now?

We are in ArcGIS Enterprise 11.3 and also in AWS machines. 

We do see some hosted feature layers losing connectivity from time to time. 

---

Checking, we see those logs in the ArcGIS Data Store > Database folder > PostgreSQL logs,

"ERROR: relation "hsu_xxxxx.sde_logfiles" does not exist at character 29"
"STATEMENT: SELECT logfile_data_id FROM hsu_xxxxx.SDE_logfiles LIMIT 0"

most of the times together with:

LOG: could not receive data from client: An established connection was aborted by the software in your host machine.

---

 In our case the timestamp of the previous logs matches with the following logs in ArcGIS Server:

SEVERE Hosted/LayerName/FeatureServer: The connection attempt failed. Rest

WARNING Unable to process request. java.io.IOException: An established connection was aborted by the software in your host machine. Rest

Any hint is welcomed,