Quantcast
Viewing all articles
Browse latest Browse all 12963

Unexpected shutdown for SQL server creating mini dump file

We are using 3 SQL instances (2005 SP4) in cluster network (active passive) and all 3 instance would be running on same node. We have 18GB total memory and max memory for instance1 = 8, other 2 = 4 GB each. So we still have 2 GB for OS.

We got sudden stopping on instance 1 and created a mini dump. I am pasting the SQL logs below. Please anyone help me on this.

here are some errors I see in logs:

2014-02-06 12:34:18.300 Server       Error: 4014, Severity: 20, State: 2.
2014-02-06 12:34:18.300 Server       A fatal error occurred while reading the input stream from the network. The session will be terminated.
2014-02-06 12:47:04.430 Server       Error: 4014, Severity: 20, State: 2.
2014-02-06 12:47:04.430 Server       A fatal error occurred while reading the input stream from the network. The session will be terminated.
2014-02-06 13:02:42.260 Server       Error: 4014, Severity: 20, State: 2.
2014-02-06 13:02:42.260 Server       A fatal error occurred while reading the input stream from the network. The session will be terminated.
2014-02-06 13:15:24.530 Server       Error: 4014, Severity: 20, State: 2.

....

2014-02-06 15:44:10.280 spid1s       AppDomain 2 (OperationsManager2007.dbo[runtime].1) is marked for unload due to memory pressure.
2014-02-06 15:44:10.290 spid1s       AppDomain 2 (OperationsManager2007.dbo[runtime].1) unloaded.
2014-02-06 15:44:27.400 spid86        Failed Virtual Allocate Bytes: FAIL_VIRTUAL_RESERVE 589824
2014-02-06 15:44:27.440 spid86      
Memory Manager
 VM Reserved = 1765904 KB
 VM Committed = 137548 KB
 AWE Allocated = 8388608 KB
 Reserved Memory = 1024 KB
 Reserved Memory In Use = 0 KB 2014-02-06 15:44:27.440 spid86      

...

2014-02-06 15:44:27.450 spid86       Procedure Cache:  TotalProcs=36 TotalPages=1655 InUsePages=7442014-02-06 15:44:27.450 spid86       Process physical/virtual memory pressure: 0/0 System physical memory pressure: 02014-02-06 15:44:27.450 spid86       Global Memory Objects:
  Resource= 789
  Locks= 559
  SE Schema Mgr= 1180
  SQLCache= 237
  Replication= 2
  ServerGlobal= 28
  XPGlobal= 2
  Xact= 296
  SETLS= 8
  DatasetMemObjs= 16
  SubpDescPmos= 41
  SortTables= 22014-02-06 15:44:27.450 spid86       Query Memory Objects:  Grants=13 Waiting=0 Maximum=130473 Available=94406 Limit=1304732014-02-06 15:44:27.450 spid86       Query Memory Objects:  Next Request=0 Waiting For=0 Cost=0 Timeout=0 Wait Time=0 Last Target=1373402014-02-06 15:44:27.450 spid86       Small Query Memory Objects:  Grants=0 Waiting=0 Maximum=6867 Available=6867 Limit=68672014-02-06 15:44:27.450 spid86      
Optimization Queue
 Overall Memory = 1200144384 Target Memory = 1080016896 Last Notification = GROW Timeout = 6 Early Termination Factor = 5
2014-02-06 15:44:27.450 spid86      
Small Gateway
 Configured Units = 32 Available Units = 30 Acquires = 2
 Waiters = 0 Threshold Factor = 250000 Threshold = 250000
2014-02-06 15:44:27.450 spid86      
Medium Gateway
 Configured Units = 8 Available Units = 8 Acquires = 0
 Waiters = 0 Threshold Factor = 12 Threshold = 45000704
2014-02-06 15:44:27.450 spid86      
Big Gateway
 Configured Units = 1 Available Units = 1 Acquires = 0
 Waiters = 0 Threshold Factor = 8 Threshold = -1
2014-02-06 15:44:27.450 spid86      
MEMORYBROKER_FOR_CACHE
 Allocations = 5739
 Rate = -338
 Target Allocations = 128906
 Future Allocations = 0
 Last Notification = GROW 2014-02-06 15:44:27.450 spid86      
MEMORYBROKER_FOR_STEAL
 Allocations = 8261
 Rate = 410
 Target Allocations = 131838
 Future Allocations = 0
 Last Notification = GROW 2014-02-06 15:44:27.450 spid86      
MEMORYBROKER_FOR_RESERVE
 Allocations = 36067
 Rate = 0
 Target Allocations = 146502
 Future Allocations = 32618
 Last Notification = GROW 2014-02-06 15:44:27.460 spid86       Error: 701, Severity: 17, State: 123.
2014-02-06 15:44:27.460 spid86       There is insufficient system memory to run this query.
2014-02-06 15:44:31.030 spid86       Error: 701, Severity: 17, State: 123.

...

2014-02-06 23:54:09.960 Server       CImageHelper::Init () Failed load of dbghelp.dll - Not enough storage is available to process this command.
2014-02-06 23:54:11.210 Server       **Dump thread - spid = 0, PSS = 0x00000000, EC = 0x00000000
2014-02-06 23:54:11.770 Server       CImageHelper::Init () Version-specific dbghelp.dll is not used
2014-02-06 23:54:11.770 Server       CImageHelper::Init () Failed load of dbghelp.dll - Not enough storage is available to process this command.
2014-02-06 23:54:14.480 Server       ***Symbol load failed - Proceed to dump without any symbols
2014-02-06 23:54:15.460 Server       ***Stack Dump being sent to G:\MSSQL.1\MSSQL\LOG\SQLDump0053.txt
2014-02-06 23:54:15.460 Server       * *******************************************************************************
2014-02-06 23:54:15.460 Server       *
2014-02-06 23:54:15.460 Server       * BEGIN STACK DUMP:
2014-02-06 23:54:15.460 Server       *   02/06/14 23:54:15 spid 0
2014-02-06 23:54:15.460 Server       *
2014-02-06 23:54:15.460 Server       * Non-yielding Resource Monitor
2014-02-06 23:54:15.460 Server       *
2014-02-06 23:54:15.460 Server       * *******************************************************************************
2014-02-06 23:54:15.460 Server       * -------------------------------------------------------------------------------
2014-02-06 23:54:15.460 Server       * Short Stack Dump
2014-02-06 23:54:21.210 Server       Stack Signature for the dump is 0x00000242

Any suggestion please on this ??


Viewing all articles
Browse latest Browse all 12963

Trending Articles



<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>