Geodatabase error: Out of client memory?

Question

Hello ESRI community, need some help here. Trying to make a sense of an error in ArcGIS log

Geodatabase error: Out of client memory.

It is being generated by ArcGIS 10.6.1 on Windows Server 2016 when a large detailed polygon data is being submitted for intersect operation. Same process works fine when smaller/simpler polygons are being processed. We use SQL Server 2014 as a back end. Both SQL and ArcGIS machines have plenty of RAM (ArcGIS machine: 32 GB, SQL Server: 16 GB) and generously increased page file, still no help. Did anybody run to this issues? What is Out of client memory really means? What is acting as a client here?

Thanks!

JonathanFarmer_oldaccount · Answer

Hi Vitaly,

I think we need a case opened with Support to troubleshoot this. If there is an issue with outStatistics in our later versions that is not present in the earlier versions, we need to better understand it.

Can you contact Support so they can create a case for you on this?

Jonathan

VitalyVogel · Answer

I was able to narrow it down. I did constructed the same query and sent it via ArcGIS web UI receiving the identical error : "Unable to complete operation". After various combinations I realized which parameters were causing the failure, it is outStatistics. When not passed, the query does return the results, however we need the counts, so statistics need to work (they used to before with 10.3.1) So the issue is not with the polygon as the query does correct intersect just not returning the counts.

Just to test, I tried a much simpler polygon and it did work as expected returning the count with outStatistics. For some reason large polygons started to cause Out of client memory exception.

Other things I've tried - increasing application server and web server memory heap size, but no luck.

JonathanFarmer_oldaccount · Answer

Vitaly,

If you submit the same queries directly from REST and do not use the web application, do you see the same behavior? It may help to narrow this down some more if we can to rule out an issue specifically on the application side.

Jonathan