11/26/13

Out of Memory exception, SQL Server 2012 hotfix

I'm back from the MVP Summit 2013 R2, a cool week of SQL nerdness in Bellevue, WA. I've Heard all the juicy, cool stuff about SQL Server now and the future and it really hurts not being able to talk much about it. Being a MVP is surrounded with much NDA and supersecrets that are not available for disclosure yet. I'll promise you all I'll get back on this when time is right.

Anyways, for this post I've chosen to give you readers a link, http://support.microsoft.com/kb/2769594.

It's for a hotfix, fixing something unusual. It fixes a Out of Memory Exception that occurs on SQL Server 2012. What happens is a memory leak by the MEMORYCLERK_SQLLOGPOOL which is used for transaction log activity. If you're running AlwaysOn and have a huge buch of availability databases this could occur in your setup.

Failed allocate pages: FAIL_PAGE_ALLOCATION 8
Error: 701, Severity: 17, State: 107.
There is insufficient system memory in resource pool 'internal' to run this query.
Error: 701, Severity: 17, State: 123.
There is insufficient system memory in resource pool 'PoolName' to run this query.
Error: 701, Severity: 17, State: 107. (Params:). The error is printed in terse mode because there was error during formatting. Tracing, ETW, notifications etc are skipped.
Error: 17312, Severity: 16, State: 1.
SQL Server is terminating a system or background task HADR Task due to errors in starting up the task (setup state 1).
AppDomain 3181 (<appdomain>) is marked for unload due to memory pressure.
AppDomain 3181 (<appdomain>) unloaded.
Error: 9602, Severity: 16, State: 1.
Failed to start a system task with error code 28709, state 19.
Error: 17300, Severity: 16, State: 1.
SQL Server was unable to run a new system task, either because there is insufficient memory or the number of configured sessions exceeds the maximum allowed in the server. Verify that the server has adequate memory. Use sp_configure with option 'user connections' to check the maximum number of user connections allowed. Use sys.dm_exec_sessions to check the current number of sessions, including user processes.
Error: 17312, Severity: 16, State: 1.
SQL Server is terminating a system or background task HADR Task due to errors in starting up the task (setup state 1).
Error: 18054, Severity: 16, State: 1.



No comments:

Post a Comment