January 15, 2009 at 2:32 pm
I have a SQL server 2005 sp2 no CUs on a window 2003 sp2 32-bit with 12GB ram, 6GB allocated to SQL Server via AWE. SQL Server is using the startup switch -g with a value of 2048 (Quite high, I know). I am getting the 701 memory error but at the times when it happens I cannot see anything that would indicate that the server is out of memory.
I have attached the output of dbcc memory status for three times that the server ran out of memory and looking through them the only thing i see that could be a memory problem is Query Memory Objects available = 0. At any other time the available is not 0. Is this why i am getting the out of memory errors? If so what is Query Memory Objects, and any way I can monitor its usage by dmv/perfmon?
I have already recommended that the -g switch value is lowered because to me it seems like we are averaging 25MB of usage. Also I cannot increase the amount of server memory allocated to SQL Server because there are other processes on the server that are using it. I know this is not desired but it is unavoidable for now.
also below is the result from sys.dm_os_ring_buffers for the OOM type (i have replaced ' ' with curly brackets because it wasnt showing correctly and couldnt figure out how to do it)
{Record id="1006" type="RING_BUFFER_OOM" time="508641923"}
{OOM}
{Action}FAIL_PAGE_ALLOCATION{/Action}
{Resources}1{/Resources}
{/OOM}
{MemoryNode id="0"}
{ReservedMemory}1163692{/ReservedMemory}
{CommittedMemory}131408{/CommittedMemory}
{SharedMemory}0{/SharedMemory}
{AWEMemory}6144000{/AWEMemory}
{SinglePagesMemory}321928{/SinglePagesMemory}
{MultiplePagesMemory}24512{/MultiplePagesMemory}
{CachedMemory}39928{/CachedMemory}
{/MemoryNode}
{MemoryRecord}
{MemoryUtilization}100{/MemoryUtilization}
{TotalPhysicalMemory}12582140{/TotalPhysicalMemory}
{AvailablePhysicalMemory}4153616{/AvailablePhysicalMemory}
{TotalPageFile}30857152{/TotalPageFile}
{AvailablePageFile}22766592{/AvailablePageFile}
{TotalVirtualAddressSpace}2097024{/TotalVirtualAddressSpace}
{AvailableVirtualAddressSpace}571664{/AvailableVirtualAddressSpace}
{AvailableExtendedVirtualAddressSpace}0{/AvailableExtendedVirtualAddressSpace}
{/MemoryRecord}
{Stack}
{frame id="0"}0X02405793{/frame}
{frame id="1"}0X015BC000{/frame}
{frame id="2"}0X0101B242{/frame}
{frame id="3"}0X0102385E{/frame}
{frame id="4"}0X0145F1FE{/frame}
{frame id="5"}0X01248C9C{/frame}
{frame id="6"}0X011CFEB6{/frame}
{frame id="7"}0X01149F4C{/frame}
{frame id="8"}0X011CFCA2{/frame}
{frame id="9"}0X01024F02{/frame}
{frame id="10"}0X01046196{/frame}
{frame id="11"}0X01042675{/frame}
{frame id="12"}0X01006E94{/frame}
{frame id="13"}0X01006FBA{/frame}
{frame id="14"}0X01006CCA{/frame}
{frame id="15"}0X0145AF36{/frame}
{/Stack}
{/Record}
If more info is needed I would be happy to provide it and thanks in advance for any suggestions.
January 19, 2009 at 6:44 am
Did you try lowering down -g switch memory? Is your problem still exists?
MJ
January 22, 2009 at 9:43 am
I have not yet changed the -g switch setting because I wanted to be sure that it would help before doing so. The setting was in place when I started with this employer and i believe it was set to that value on either the advice of PSS or application vendor. I wanted to be sure that this was either an issue or 2048 is over allocating memory outside buffer pool.
Viewing 3 posts - 1 through 2 (of 2 total)
You must be logged in to reply to this topic. Login to reply