64bit server memory problems
-
Hi,
We've setup a new 64bit 2005 box, and it's crashing and rebooting a lot. We've got a hunch it's memory problems but we're a bit stuck, and so I've attached as much info as possible. Any input or help is much appreciated, and thanks for even taking the time to look this over, we appreciate the time of busy people!
It's a SQL Server 2005 Standard edition, 64 bit, 32Gb RAM, page file is currently set to 32Gb min and 45Gb max.
3 instances, 2 used and 1 default instance which is unused. The 2 instances are set:
Minimum server memory(in MB):8096
Maximum server memory(in MB):10240
AWE is unselected, but the SQL Server service accounts have been given the right to Lock Pages in Memory. dbcc memorystatus AWE allocated still shows 0 though, even after service and server restarts. (does this right need AWE explicitly?)
Beginning of SQLDump log file:
=====================================================================
BugCheck Dump
=====================================================================
This file is generated by Microsoft SQL Server
version 9.00.3042.00
upon detection of fatal unexpected error. Please return this file,
the query or program that produced the bugcheck, the database and
the error log, and any other pertinent information with a Service Request.
Computer type is AT/AT COMPATIBLE.
Current time is 13:40:04 09/10/07.
8 Unknown CPU 9., 2333 Mhz processor (s).
Windows NT 5.2 Build 3790 CSD Service Pack 2.
Memory
MemoryLoad = 9%
Total Physical = 32765 MB
Available Physical = 29649 MB
Total Page File = 64591 MB
Available Page File = 61615 MB
Total Virtual = 8388607 MB
Available Virtual = 8355469 MB
***Stack Dump being sent to E:\Program Files\Microsoft SQL Server\MSSQL.2\MSSQL\LOG\SQLDump0180.txt
SqlDumpExceptionHandler: Process 68 generated fatal exception c0000005 EXCEPTION_ACCESS_VIOLATION. SQL Server is
terminating this process.
----------------------
dbcc memorystatus:
Memory Manager¦ KB
VM Reserved¦33665472
VM Committed¦462904
AWE Allocated¦0
Reserved Memory¦1024
Reserved Memory In Use¦0
(5 row(s) affected)
Memory node Id = 0¦ KB
VM Reserved¦33659712
VM Committed¦457232
AWE Allocated¦0
MultiPage Allocator¦20608
SinglePage Allocator¦252936
(5 row(s) affected)
MEMORYCLERK_SQLGENERAL (Total)¦ KB
VM Reserved¦0
VM Committed¦0
AWE Allocated¦0
SM Reserved ¦0
SM Commited ¦0
SinglePage Allocator ¦3456
MultiPage Allocator ¦4608
(7 row(s) affected)
MEMORYCLERK_SQLBUFFERPOOL (Total)¦ KB
VM Reserved¦33603584
VM Committed¦401664
AWE Allocated¦0
SM Reserved ¦0
SM Commited ¦0
SinglePage Allocator ¦0
MultiPage Allocator ¦24
(7 row(s) affected)
MEMORYCLERK_SQLOPTIMIZER (Total)¦ KB
VM Reserved¦0
VM Committed¦0
AWE Allocated¦0
SM Reserved ¦0
SM Commited ¦0
SinglePage Allocator ¦464
MultiPage Allocator ¦112
(7 row(s) affected)
MEMORYCLERK_SQLUTILITIES (Total)¦ KB
VM Reserved¦960
VM Committed¦960
AWE Allocated¦0
SM Reserved ¦0
SM Commited ¦0
SinglePage Allocator ¦136
MultiPage Allocator ¦0
(7 row(s) affected)
MEMORYCLERK_SQLSTORENG (Total)¦ KB
VM Reserved¦832
VM Committed¦832
AWE Allocated¦0
SM Reserved ¦0
SM Commited ¦0
SinglePage Allocator ¦1168
MultiPage Allocator ¦528
(7 row(s) affected)
MEMORYCLERK_SQLCONNECTIONPOOL (Total)¦ KB
VM Reserved¦0
VM Committed¦0
AWE Allocated¦0
SM Reserved ¦0
SM Commited ¦0
SinglePage Allocator ¦488
MultiPage Allocator ¦0
(7 row(s) affected)
MEMORYCLERK_SQLCLR (Total)¦ KB
VM Reserved¦0
VM Committed¦0
AWE Allocated¦0
SM Reserved ¦0
SM Commited ¦0
SinglePage Allocator ¦8
MultiPage Allocator ¦0
(7 row(s) affected)
MEMORYCLERK_SQLSERVICEBROKER (Total)¦ KB
VM Reserved¦0
VM Committed¦0
AWE Allocated¦0
SM Reserved ¦0
SM Commited ¦0
SinglePage Allocator ¦96
MultiPage Allocator ¦304
(7 row(s) affected)
MEMORYCLERK_SQLHTTP (Total)¦ KB
VM Reserved¦0
VM Committed¦0
AWE Allocated¦0
SM Reserved ¦0
SM Commited ¦0
SinglePage Allocator ¦8
MultiPage Allocator ¦0
(7 row(s) affected)
MEMORYCLERK_SNI (Total)¦ KB
VM Reserved¦0
VM Committed¦0
AWE Allocated¦0
SM Reserved ¦0
SM Commited ¦0
SinglePage Allocator ¦48
MultiPage Allocator ¦48
(7 row(s) affected)
MEMORYCLERK_FULLTEXT (Total)¦ KB
VM Reserved¦0
VM Committed¦0
AWE Allocated¦0
SM Reserved ¦0
SM Commited ¦0
SinglePage Allocator ¦16
MultiPage Allocator ¦0
(7 row(s) affected)
MEMORYCLERK_SQLXP (Total)¦ KB
VM Reserved¦0
VM Committed¦0
AWE Allocated¦0
SM Reserved ¦0
SM Commited ¦0
SinglePage Allocator ¦16
MultiPage Allocator ¦0
(7 row(s) affected)
MEMORYCLERK_HOST (Total)¦ KB
VM Reserved¦0
VM Committed¦0
AWE Allocated¦0
SM Reserved ¦0
SM Commited ¦0
SinglePage Allocator ¦16
MultiPage Allocator ¦0
(7 row(s) affected)
MEMORYCLERK_SOSNODE (Total)¦ KB
VM Reserved¦0
VM Committed¦0
AWE Allocated¦0
SM Reserved ¦0
SM Commited ¦0
SinglePage Allocator ¦3856
MultiPage Allocator ¦12568
(7 row(s) affected)
MEMORYCLERK_SQLSERVICEBROKERTRANSPORT (Total)¦ KB
VM Reserved¦0
VM Committed¦0
AWE Allocated¦0
SM Reserved ¦0
SM Commited ¦0
SinglePage Allocator ¦48
MultiPage Allocator ¦0
(7 row(s) affected)
CACHESTORE_OBJCP (Total)¦ KB
VM Reserved¦0
VM Committed¦0
AWE Allocated¦0
SM Reserved ¦0
SM Commited ¦0
SinglePage Allocator ¦50272
MultiPage Allocator ¦0
(7 row(s) affected)
CACHESTORE_SQLCP (Total)¦ KB
VM Reserved¦0
VM Committed¦0
AWE Allocated¦0
SM Reserved ¦0
SM Commited ¦0
SinglePage Allocator ¦179576
MultiPage Allocator ¦1920
(7 row(s) affected)
CACHESTORE_PHDR (Total)¦ KB
VM Reserved¦0
VM Committed¦0
AWE Allocated¦0
SM Reserved ¦0
SM Commited ¦0
SinglePage Allocator ¦2840
MultiPage Allocator ¦0
(7 row(s) affected)
CACHESTORE_XPROC (Total)¦ KB
VM Reserved¦0
VM Committed¦0
AWE Allocated¦0
SM Reserved ¦0
SM Commited ¦0
SinglePage Allocator ¦72
MultiPage Allocator ¦0
(7 row(s) affected)
CACHESTORE_TEMPTABLES (Total)¦ KB
VM Reserved¦0
VM Committed¦0
AWE Allocated¦0
SM Reserved ¦0
SM Commited ¦0
SinglePage Allocator ¦24
MultiPage Allocator ¦0
(7 row(s) affected)
CACHESTORE_NOTIF (Total)¦ KB
VM Reserved¦0
VM Committed¦0
AWE Allocated¦0
SM Reserved ¦0
SM Commited ¦0
SinglePage Allocator ¦16
MultiPage Allocator ¦0
(7 row(s) affected)
CACHESTORE_VIEWDEFINITIONS (Total)¦ KB
VM Reserved¦0
VM Committed¦0
AWE Allocated¦0
SM Reserved ¦0
SM Commited ¦0
SinglePage Allocator ¦16
MultiPage Allocator ¦0
(7 row(s) affected)
CACHESTORE_XMLDBTYPE (Total)¦ KB
VM Reserved¦0
VM Committed¦0
AWE Allocated¦0
SM Reserved ¦0
SM Commited ¦0
SinglePage Allocator ¦8
MultiPage Allocator ¦0
(7 row(s) affected)
CACHESTORE_XMLDBELEMENT (Total)¦ KB
VM Reserved¦0
VM Committed¦0
AWE Allocated¦0
SM Reserved ¦0
SM Commited ¦0
SinglePage Allocator ¦8
MultiPage Allocator ¦0
(7 row(s) affected)
CACHESTORE_XMLDBATTRIBUTE (Total)¦ KB
VM Reserved¦0
VM Committed¦0
AWE Allocated¦0
SM Reserved ¦0
SM Commited ¦0
SinglePage Allocator ¦8
MultiPage Allocator ¦0
(7 row(s) affected)
CACHESTORE_STACKFRAMES (Total)¦ KB
VM Reserved¦0
VM Committed¦0
AWE Allocated¦0
SM Reserved ¦0
SM Commited ¦0
SinglePage Allocator ¦0
MultiPage Allocator ¦8
(7 row(s) affected)
CACHESTORE_BROKERTBLACS (Total)¦ KB
VM Reserved¦0
VM Committed¦0
AWE Allocated¦0
SM Reserved ¦0
SM Commited ¦0
SinglePage Allocator ¦288
MultiPage Allocator ¦0
(7 row(s) affected)
CACHESTORE_BROKERKEK (Total)¦ KB
VM Reserved¦0
VM Committed¦0
AWE Allocated¦0
SM Reserved ¦0
SM Commited ¦0
SinglePage Allocator ¦8
MultiPage Allocator ¦0
(7 row(s) affected)
CACHESTORE_BROKERDSH (Total)¦ KB
VM Reserved¦0
VM Committed¦0
AWE Allocated¦0
SM Reserved ¦0
SM Commited ¦0
SinglePage Allocator ¦8
MultiPage Allocator ¦0
(7 row(s) affected)
CACHESTORE_BROKERUSERCERTLOOKUP (Total)¦ KB
VM Reserved¦0
VM Committed¦0
AWE Allocated¦0
SM Reserved ¦0
SM Commited ¦0
SinglePage Allocator ¦8
MultiPage Allocator ¦0
(7 row(s) affected)
CACHESTORE_BROKERRSB (Total)¦ KB
VM Reserved¦0
VM Committed¦0
AWE Allocated¦0
SM Reserved ¦0
SM Commited ¦0
SinglePage Allocator ¦8
MultiPage Allocator ¦0
(7 row(s) affected)
CACHESTORE_BROKERREADONLY (Total)¦ KB
VM Reserved¦0
VM Committed¦0
AWE Allocated¦0
SM Reserved ¦0
SM Commited ¦0
SinglePage Allocator ¦72
MultiPage Allocator ¦0
(7 row(s) affected)
CACHESTORE_BROKERTO (Total)¦ KB
VM Reserved¦0
VM Committed¦0
AWE Allocated¦0
SM Reserved ¦0
SM Commited ¦0
SinglePage Allocator ¦8
MultiPage Allocator ¦0
(7 row(s) affected)
CACHESTORE_EVENTS (Total)¦ KB
VM Reserved¦0
VM Committed¦0
AWE Allocated¦0
SM Reserved ¦0
SM Commited ¦0
SinglePage Allocator ¦16
MultiPage Allocator ¦0
(7 row(s) affected)
CACHESTORE_SYSTEMROWSET (Total)¦ KB
VM Reserved¦0
VM Committed¦0
AWE Allocated¦0
SM Reserved ¦0
SM Commited ¦0
SinglePage Allocator ¦1800
MultiPage Allocator ¦0
(7 row(s) affected)
USERSTORE_SCHEMAMGR (Total)¦ KB
VM Reserved¦0
VM Committed¦0
AWE Allocated¦0
SM Reserved ¦0
SM Commited ¦0
SinglePage Allocator ¦2360
MultiPage Allocator ¦0
(7 row(s) affected)
USERSTORE_DBMETADATA (Total)¦ KB
VM Reserved¦0
VM Committed¦0
AWE Allocated¦0
SM Reserved ¦0
SM Commited ¦0
SinglePage Allocator ¦2256
MultiPage Allocator ¦0
(7 row(s) affected)
USERSTORE_TOKENPERM (Total)¦ KB
VM Reserved¦0
VM Committed¦0
AWE Allocated¦0
SM Reserved ¦0
SM Commited ¦0
SinglePage Allocator ¦1200
MultiPage Allocator ¦0
(7 row(s) affected)
USERSTORE_OBJPERM (Total)¦ KB
VM Reserved¦0
VM Committed¦0
AWE Allocated¦0
SM Reserved ¦0
SM Commited ¦0
SinglePage Allocator ¦328
MultiPage Allocator ¦0
(7 row(s) affected)
USERSTORE_SXC (Total)¦ KB
VM Reserved¦0
VM Committed¦0
AWE Allocated¦0
SM Reserved ¦0
SM Commited ¦0
SinglePage Allocator ¦80
MultiPage Allocator ¦0
(7 row(s) affected)
OBJECTSTORE_LBSS (Total)¦ KB
VM Reserved¦0
VM Committed¦0
AWE Allocated¦0
SM Reserved ¦0
SM Commited ¦0
SinglePage Allocator ¦80
MultiPage Allocator ¦256
(7 row(s) affected)
OBJECTSTORE_SNI_PACKET (Total)¦ KB
VM Reserved¦0
VM Committed¦0
AWE Allocated¦0
SM Reserved ¦0
SM Commited ¦0
SinglePage Allocator ¦792
MultiPage Allocator ¦48
(7 row(s) affected)
OBJECTSTORE_SERVICE_BROKER (Total)¦ KB
VM Reserved¦0
VM Committed¦0
AWE Allocated¦0
SM Reserved ¦0
SM Commited ¦0
SinglePage Allocator ¦272
MultiPage Allocator ¦0
(7 row(s) affected)
OBJECTSTORE_LOCK_MANAGER (Total)¦ KB
VM Reserved¦32768
VM Committed¦32768
AWE Allocated¦0
SM Reserved ¦0
SM Commited ¦0
SinglePage Allocator ¦648
MultiPage Allocator ¦0
(7 row(s) affected)
Buffer Distribution¦Buffers
Stolen¦1234
Free¦283
Cached¦30383
Database (clean)¦12902
Database (dirty)¦574
I/O¦0
Latched¦0
(7 row(s) affected)
Buffer Counts¦Buffers
Committed¦45376
Target¦1310720
Hashed¦13476
Stolen Potential¦1213566
External Reservation¦0
Min Free¦256
Visible¦1310720
Available Paging File¦8010012
(8 row(s) affected)
Procedure Cache¦Value
TotalProcs¦3361
TotalPages¦29335
InUsePages¦1360
(3 row(s) affected)
Global Memory Objects¦Buffers
Resource¦260
Locks¦84
XDES¦30
SETLS¦8
SE Dataset Allocators¦16
SubpDesc Allocators¦8
SE SchemaManager¦294
SQLCache¦405
Replication¦2
ServerGlobal¦48
XP Global¦2
SortTables¦2
(12 row(s) affected)
Query Memory Objects¦Value
Grants¦0
Waiting¦0
Available (Buffers)¦972160
Maximum (Buffers)¦972160
Limit¦972160
Next Request¦0
Waiting For¦0
Cost¦0
Timeout¦0
Wait Time¦0
Last Target¦984960
(11 row(s) affected)
Small Query Memory Objects¦Value
Grants¦0
Waiting¦0
Available (Buffers)¦12800
Maximum (Buffers)¦12800
Limit¦12800
(5 row(s) affected)
Optimization Queue¦Value
Overall Memory¦8606711808
Target Memory¦7960084480
Last Notification¦1
Timeout¦6
Early Termination Factor¦5
(5 row(s) affected)
Small Gateway¦Value
Configured Units¦32
Available Units¦32
Acquires¦0
Waiters¦0
Threshold Factor¦380000
Threshold¦380000
(6 row(s) affected)
Medium Gateway¦Value
Configured Units¦8
Available Units¦8
Acquires¦0
Waiters¦0
Threshold Factor¦12
(5 row(s) affected)
Big Gateway¦Value
Configured Units¦1
Available Units¦1
Acquires¦0
Waiters¦0
Threshold Factor¦8
(5 row(s) affected)
MEMORYBROKER_FOR_CACHE¦Value
Allocations¦30370
Rate¦84
Target Allocations¦1000559
Future Allocations¦0
Last Notification¦1
(5 row(s) affected)
MEMORYBROKER_FOR_STEAL¦Value
Allocations¦1226
Rate¦359
Target Allocations¦971690
Future Allocations¦0
Last Notification¦1
(5 row(s) affected)
MEMORYBROKER_FOR_RESERVE¦Value
Allocations¦0
Rate¦-328
Target Allocations¦1050624
Future Allocations¦243040
Last Notification¦1
(5 row(s) affected)
DBCC execution completed. If DBCC printed error messages, contact your system administrator.
--------------------------
output from
select * from sys.dm_os_performance_counters where object_name like '%memory%' or object_name like '%buffer%' :
MSSQL$MPS:Buffer Manager, Buffer cache hit ratio 4408537003264
MSSQL$MPS:Buffer Manager, Buffer cache hit ratio base 45381073939712
MSSQL$MPS:Buffer Manager, Page lookups/sec 2577038272696576
MSSQL$MPS:Buffer Manager, Free list stalls/sec 0272696576
MSSQL$MPS:Buffer Manager, Free pages 19365792
MSSQL$MPS:Buffer Manager, Total pages 6832065792
MSSQL$MPS:Buffer Manager, Target pages 131072065792
MSSQL$MPS:Buffer Manager, Database pages 1525865792
MSSQL$MPS:Buffer Manager, Reserved pages 065792
MSSQL$MPS:Buffer Manager, Stolen pages 5286965792
MSSQL$MPS:Buffer Manager, Lazy writes/sec 0272696576
MSSQL$MPS:Buffer Manager, Readahead pages/sec 9737272696576
MSSQL$MPS:Buffer Manager, Page reads/sec 14927272696576
MSSQL$MPS:Buffer Manager, Page writes/sec 870272696576
MSSQL$MPS:Buffer Manager, Checkpoint pages/sec 645272696576
MSSQL$MPS:Buffer Manager, AWE lookup maps/sec 0272696576
MSSQL$MPS:Buffer Manager, AWE stolen maps/sec 0272696576
MSSQL$MPS:Buffer Manager, AWE write maps/sec 0272696576
MSSQL$MPS:Buffer Manager, AWE unmap calls/sec 0272696576
MSSQL$MPS:Buffer Manager, AWE unmap pages/sec 0272696576
MSSQL$MPS:Buffer Manager, Page life expectancy 190265792
MSSQL$MPS:Buffer Partition, Free pages 007 8665792
MSSQL$MPS:Buffer Partition, Free list requests/sec 007 673272696576
MSSQL$MPS:Buffer Partition, Free list empty/sec 007 93272696576
MSSQL$MPS:Buffer Partition, Free pages 006 365792
MSSQL$MPS:Buffer Partition, Free list requests/sec 006 422272696576
MSSQL$MPS:Buffer Partition, Free list empty/sec 006 82272696576
MSSQL$MPS:Buffer Partition, Free pages 005 565792
MSSQL$MPS:Buffer Partition, Free list requests/sec 005 139272696576
MSSQL$MPS:Buffer Partition, Free list empty/sec 005 37272696576
MSSQL$MPS:Buffer Partition, Free pages 004 3265792
MSSQL$MPS:Buffer Partition, Free list requests/sec 004 199184272696576
MSSQL$MPS:Buffer Partition, Free list empty/sec 004 17363272696576
MSSQL$MPS:Buffer Partition, Free pages 003 5065792
MSSQL$MPS:Buffer Partition, Free list requests/sec 003 135826272696576
MSSQL$MPS:Buffer Partition, Free list empty/sec 003 17214272696576
MSSQL$MPS:Buffer Partition, Free pages 002 965792
MSSQL$MPS:Buffer Partition, Free list requests/sec 002 105589272696576
MSSQL$MPS:Buffer Partition, Free list empty/sec 002 13618272696576
MSSQL$MPS:Buffer Partition, Free pages 001 865792
MSSQL$MPS:Buffer Partition, Free list requests/sec 001 112846272696576
MSSQL$MPS:Buffer Partition, Free list empty/sec 001 14317272696576
MSSQL$MPS:Buffer Partition, Free pages 000 065792
MSSQL$MPS:Buffer Partition, Free list requests/sec 000 187272696576
MSSQL$MPS:Buffer Partition, Free list empty/sec 000 24272696576
MSSQL$MPS:Buffer Node, Free pages 000 19365792
MSSQL$MPS:Buffer Node, Total pages 000 6832065792
MSSQL$MPS:Buffer Node, Foreign pages 000 065792
MSSQL$MPS:Buffer Node, Database pages 000 1525865792
MSSQL$MPS:Buffer Node, Stolen pages 000 5286965792
MSSQL$MPS:Buffer Node, Target pages 000 131072065792
MSSQL$MPS:Buffer Node, Page life expectancy 000 190265792
MSSQL$MPS:Memory Manager, Connection Memory (KB) 60065792
MSSQL$MPS:Memory Manager, Granted Workspace Memory (KB) 065792
MSSQL$MPS:Memory Manager, Lock Memory (KB) 67265792
MSSQL$MPS:Memory Manager, Lock Blocks Allocated 255065792
MSSQL$MPS:Memory Manager, Lock Owner Blocks Allocated 505065792
MSSQL$MPS:Memory Manager, Lock Blocks 765792
MSSQL$MPS:Memory Manager, Lock Owner Blocks 2465792
MSSQL$MPS:Memory Manager, Maximum Workspace Memory (KB) 777728065792
MSSQL$MPS:Memory Manager, Memory Grants Outstanding 065792
MSSQL$MPS:Memory Manager, Memory Grants Pending 065792
MSSQL$MPS:Memory Manager, Optimizer Memory (KB) 64065792
MSSQL$MPS:Memory Manager, SQL Cache Memory (KB) 472065792
MSSQL$MPS:Memory Manager, Target Server Memory (KB) 1048576065792
MSSQL$MPS:Memory Manager, Total Server Memory (KB) 54656065792
-
Unfortunately Standard Edition ignores the Lock Pages in Memory option (There's a KB reference - I don't have the number handy but do a search on member problems and you'll find it).
Install the latest service pack - there's a remote terminal access issue.
If you're using an HP box, try disabling ILO (integrated lights out monitoring).
We're running Standard Edition with 16GB memory (dedicated server and lightly loaded at the time) and every 10 minutes or so it would swap out SQL memory down to 100 mb - connections would time out - nothing would run. By the time enough SQL was back in memory to run in a reasonable manner, it would dump everything again - never used more than about 50% of memory.
Did the above two steps and resolved our problem....YMMV
-
we've applied the service pack, but we are running an HP box... I'll disable the ILO in the morning.
Thanks for the reply, really appreciate it, was starting to tear bits of hair out (soon to become a precious commodity).
I'll post again to confirm it fixed the problem. I doubt we're the only ones!
-
Have you looked at the hardware diagnostics? It may just be you have a faulty component. Even if the hardware log is clear, your HP engineer should have some programs that put the box under various loads to confirm the hardware is OK.
Original author: https://github.com/SQL-FineBuild/Common/wiki/ 1-click install and best practice configuration of SQL Server 2019, 2017 2016, 2014, 2012, 2008 R2, 2008 and 2005.
When I give food to the poor they call me a saint. When I ask why they are poor they call me a communist - Archbishop Hélder Câmara
-
I had a similar issue with a brand new HP proliant server. We ended up rebuilding the server, this time ensuring the latest 64 bit HP Proliant Support Pack was installed (not sure what was on it previously as it was built by an ex-employee) as well as ensuring all the latest firmware was applied. This fixed the problem.
-
I concur with Stu about getting the latest 64 Bit HP Proliant Support Pack. The current one is 7.90 and was released in August (although HP's site indicates late July). Just be sure to get the 64 bit one.
For those who don't work with HP equipment, the Proliant Support pack is a collection of drivers, management agents, and utilities to manage the HP hardware. HP updates individual utilities as required, but updates the Support Packs (usually updating everything in them) are released 2-3 times per year.
Once the Proliant Support Pack is installed and rebooted, you will have the latest HP System Management Home Page icon on the desktop. Double Click on it and log in using an administrator account. If there is a current problem with any hardware (including having your iLO enabled but not having anything connected to it), it will be noted in yellow above all of the other categories.
While you are fetching the latest Proliant Support Pack, also fetch the latest HP Firmware Maintenance CD (version 7.90, released July/August). This is an .ISO image of a bootable CD and is 600MB. Burn the .ISO to a CD and boot the server off the CD. Have it update firmware.
HP updates firmware for main system boards and RAID controllers every couple months for currently shipping servers ( G5 models), but if you haven't been keeping the firmware up to date, the CD may still find something to flash.
Before you decide to rebuild the server OS, go get the latest Smartstart CD (also version 7.90, date says July, but it wasn't on HPs site till last week). Boot from the Smart Start and you can run offline diagnostics that should detect a hardware memory problem. If you do decide to rebuild the server, boot off the SmartStart CD for assisted OS installation that will install the 7.90 Proliant Support Pack as part of the install. Be aware that using Smart Start for OS install will delete all partitions on your boot drive
Disclaimer: I don't work for HP. I just manage a lot of HP Proliant Servers.
-
I had a similar issue with a Dell server experiencing multiple memory access violations in a day; sometimes locking up the SQL server; and even blue screening a couple of times at restart. I had a MS PSS case open but the issue was finally resolved when one of our network/server admins found an OS driver patch that was required on a 64 bit OS when you had more than 4gb of memory installed. Since that patch the system hasn't had the slightest blip.
Moral of the story... if I were you I would definitely look at the HP driver updates.
-
I had a client that was spanked by BOTH of the bugs covered in this thread: HP iLO and Windows Large File Copy. Symptoms were the same for both bugs: SQL Server would have ALL of it's memory yanked out from underneath it. I watched allocated RAM go from 9+ GB to ZERO instantaneously!! Talk about a performance killer. 🙂 Fortunately both bugs have patches avaiable and they worked like a charm, and the client now thinks I walk on water. hehehe
I would also recommend triple-checking that you installed the 64bit version of SQL Server. Had a client that screwed that one up too.
Best,
Kevin G. Boles
SQL Server Consultant
SQL MVP 2007-2012
TheSQLGuru on googles mail service -
Got the latest HP service pack applied, and now we're monitoring the server to see if anything... no, I won't tempt fate!
Thanks for all the help, it does seem that this is the issue. Do HP know about this, as I didn't see anything on their site - or perhaps they don't want to let anyone know...?
-
I had to get the information for both bugs from a third-level sql server support staff at MS. The HP bug is so disasterous for the box that I would have expected HP to notify every registered server owner via email about the issue and the fix. Of course the key word there is registered. The winserver2003 large file copy OS bug is kind of esoteric, only occurring if you copy very large files from a fast drive to a slower one. Of course my client was copying there sql backup files to an attached USB drive for off-site storage.
Best,
Kevin G. Boles
SQL Server Consultant
SQL MVP 2007-2012
TheSQLGuru on googles mail service -
Could you post the MSKB # for the "large file copy OS bug."
I've got one server, Win2003 R1 ENT SP1, 32 bit that keeps failing large file copies (120GB), particularly when sending the file to/from a network drive.
Initially it looked like a STORPORT problem, but after installing the appropriate patch (I don't have the number with me right now), I was able to do a couple copies, but when I needed to do the copies, it failed.
I was able to get around the issue by doing a SQL backup to a UNC path accross the network
-
We are also having problems with a Dell Server, SQL 2005 64-bit.. 8gb ram. I'm curious what specific patch you had applied? Thanks!
======================================
I had a similar issue with a Dell server experiencing multiple memory access violations in a day; sometimes locking up the SQL server; and even blue screening a couple of times at restart. I had a MS PSS case open but the issue was finally resolved when one of our network/server admins found an OS driver patch that was required on a 64 bit OS when you had more than 4gb of memory installed. Since that patch the system hasn't had the slightest blip.
Moral of the story... if I were you I would definitely look at the HP driver updates.
-
http://support.microsoft.com/kb/KB920739
Best,
Kevin G. Boles
SQL Server Consultant
SQL MVP 2007-2012
TheSQLGuru on googles mail service -
Robert,
Here is what my tech remembers about the Dell server patch:
"I got the updated 64-bit SAS driver for the 1955 Blade"
hth,
Ed
Viewing 14 posts - 1 through 13 (of 13 total)
You must be logged in to reply to this topic. Login to reply