June 2, 2011 at 3:05 pm
I have SQL Server sp3 2 node cluster that restarted itself instead of failing over twice in couple of week. I am looking at the sql log and this is what I see:
2011-06-02 08:53:46.28 Server Detected 8 CPUs. This is an informational message; no user action is required.
2011-06-02 08:53:46.34 Server Cannot use Large Page Extensions: lock memory privilege was not granted.
2011-06-02 08:53:46.74 Server Using dynamic lock allocation. Initial allocation of 2500 Lock blocks and 5000 Lock Owner blocks per node. This is an informational message only. No user action is required.
2011-06-02 08:53:46.88 Server Attempting to initialize Microsoft Distributed Transaction Coordinator (MS DTC). This is an informational message only. No user action is required.
2011-06-02 08:53:46.95 spid1s A significant part of sql server process memory has been paged out. This may result in a performance degradation. Duration: 0 seconds. Working set (KB): 38296, committed (KB): 90104, memory utilization: 42%.
What is going on here? This guy is taking complaining about memory at startup. There is no indication of why it went down.
sql cluster is 64 bit windows 2003 enterprise edition.
Thoughts/ advice ???
Thanks
June 2, 2011 at 3:13 pm
check the event logs before and after that service restart and determine if something else happened (e.g. patches applied to server and it was rebooted)
Jason...AKA CirqueDeSQLeil
_______________________________________________
I have given a name to my pain...MCM SQL Server, MVP
SQL RNNR
Posting Performance Based Questions - Gail Shaw[/url]
Learn Extended Events
June 2, 2011 at 3:38 pm
2011-06-02 08:53:46.28 Server Detected 8 CPUs. This is an informational message; no user action is required.
2011-06-02 08:53:46.34 Server Cannot use Large Page Extensions: lock memory privilege was not granted.2011-06-02 08:53:46.74 Server Using dynamic lock allocation. Initial allocation of 2500 Lock blocks and 5000 Lock Owner blocks per node. This is an informational message only. No user action is required.
2011-06-02 08:53:46.88 Server Attempting to initialize Microsoft Distributed Transaction Coordinator (MS DTC). This is an informational message only. No user action is required.
2011-06-02 08:53:46.95 spid1s A significant part of sql server process memory has been paged out. This may result in a performance degradation. Duration: 0 seconds. Working set (KB): 38296, committed (KB): 90104, memory utilization: 42%.
sql cluster is 64 bit windows 2003 enterprise edition.
Two big clues there (highlighted). windows 2003 does not handle trimming the working set as well as windows 2008. Even though this is 64 bit the classic fix for this is to grant the sql service account the lock pages in memory right.
Set that and see how you go and meanwhile you can investigate where the memory pressure came from that forced SQL to give up its memory. This probably made SQL appear unresponsive so the cluster took it down, that should be apparent from the application or cluster log.
---------------------------------------------------------------------
June 3, 2011 at 1:32 am
Why SQL server B didnot fall back to Server A
Reason 1:
Server A is already consuming lot of Memory and when SQL Services of B falls over to server A, it wont allow the sql server to come online (as MIN Server Memory parameter in server B is more tha memory availble in server A)..... during this time, if server B os reboots and comes up again...
So SQL Server B will again come online on server B due to fallover and fallback property... usually sql server B should hang in such scenerios, but it will come online though
So please check MAX and MIN memory Parameters and also enable page locking in sql server, it will be very helpful.
Reason 2:
Check Hardware is fine, also please verify is BIOS version are up to date.
Viewing 4 posts - 1 through 3 (of 3 total)
You must be logged in to reply to this topic. Login to reply