Select to view content in your preferred language

ArcSDE 10 Error: Out of Server Memory

9708
14
11-03-2011 11:44 AM
MatthewGerbrandt
Emerging Contributor
Good morning. Some of my users are getting the following error intermitantly:

Error
Out of server memory [sde.sde.GDB_Items]

I'm not sure how to keep this error from recurring. If anyone could help me out, I'd sure appreciate it.

Here are the server specs:
ArcSDE 10
MS SQL Server 2005
Windows Server 2003 - 15 GB RAM


Thanks for your help!
0 Kudos
14 Replies
MariaGiarrusso
Occasional Contributor
Just started having similar issues.  I have more than one SQL server 2008 R2 SDE database running on the same virtual server.  I only get the error when trying to connect to one of the databases but not the other.  Any success getting it resolved?
0 Kudos
DennisGilbertson
Emerging Contributor
Just experienced the same error today. Any luck determining the problem?
0 Kudos
ScottLongerbeam
Deactivated User
Any solution to this yet?  I am getting the same error messages in my nightly update scripts.
0 Kudos
JonDeRose
Esri Contributor
Is this behavior occurring with all connection types (ie. direct-connections/ application server connections [3-t], OLEDB)?

Have you been able to capture any extended error information from the SQL Server logs, Event Viewer, sde_intercept, sdedc_SqlServer.log, etc.?

Viewing the SQL Server Error Log
http://msdn.microsoft.com/en-us/library/ms187885.aspx

HowTo:  Diagnose ArcSDE connection and performance issues using SDEINTERCEPT
http://support.esri.com/en/knowledgebase/techarticles/detail/35704
0 Kudos
by Anonymous User
Not applicable
I have been getting this same error for a while now. Its driving me and my users crazy!!
0 Kudos
JonDeRose
Esri Contributor
If you are able to capture any error logs (mentioned in my previous post) while this issue occurs please post this information for review or contact Esri Technical Support for further assistance.
0 Kudos
by Anonymous User
Not applicable

[/HR]Ok, Have been trying to trouble shoot this issue for a while. The trick was replicating the problem. It seemed to only happen every once in a while with no consistency. What I found is that if I Disable and then re-enable my network card with ArcMap open and layers loaded I can get the "Out of Server Memory" error. Interestingly, I also discovered that simply unplugging your network cable and plugging it back in does not cause ArcMap to throw the error.


I have also been using SDEIntercept and found that when I do receive the "out of server memeory" error. I find the message below in the logs.


[W 09:49:23.757] Command: NextBuffer
[W 09:49:23.757] Long: 1
[R 09:49:23.757] Long: -409
========================================
[W 09:49:23.757] Command: GetstreamError
[W 09:49:23.757] Long: 1
[W 09:49:23.757] Long: -51
[W 09:49:23.757] Long: 0
[R 09:49:23.757] NString: "Microsoft SQL Server Native Client 10.0: Communication link failure"
[R 09:49:23.757] NString: ""
========================================
[W 09:49:23.757] Command: CloseStream
[W 09:49:23.757] Long: 1
[W 09:49:23.757] Long: 1
[R 09:49:23.757] Long: 0
========================================
0 Kudos
NAOMIPAUL
Regular Contributor
One of our users received the same error this morning, I have never seen it before.

Out of server memory [PublicGIS.sde.GDB_Items]

Has anyone found a solution to this?

ArcSDE10
MSSQL 2008
Windows Server 2008
0 Kudos
by Anonymous User
Not applicable
I called esri support to discuss this issue. They had no concrete fix but did recomend the following:

1. Please close all ArcGIS ArcObjects applications (ArcCatalog, ArcMap) when not in use and at the end of each day.

2. Verify within the SQL Server database table, sde.sde_process_information table that client connections are closed, or to review the time stamp listed for open connections.

3. It is highly recommended, though not required, to verify that all client connections are disconnected prior to executing an ArcSDE database compress.  Any connection to the database will generate locks on the data and will thus prevent a full compress from being achieved.

4. Check the Firewall refresh / recycle rate, it may be possible that it could be conflicting with the ArcGIS Server map services refresh / recycle rate

5. It may be possible that the many scheduled tasks being completed each night are competing for server memory resources, please review and evaluate the concurrency of these tasks and consider alter the start times of these tasks so that they are more evenly spread out when using these server resources.

If additional errors continue to persist, please attempt to capture a Client Intercept trace, in hope that we can gather additional error logging.
0 Kudos