WARNING: Failed to reserve contiguous memory of Size= Can anyone help?
-
We are getting these messages in our sql server errorlog every day. Sometimes they are benign, sometimes they are correllated with client-side SQLException, and the queries on client fail. These do not reoccur regularly, but rather sporadically.
We are win2k3, enterprise edition sql server 2000, sp3 plus security patch, 8 proc, 8GB, NAS disk device.
Any experience with memory problems or advice would be greatly appreciated!
2004-08-02 18:39:19.97 spid111 WARNING: Failed to reserve contiguous memory of Size= 131072.
2004-08-02 18:39:19.97 spid108 WARNING: Failed to reserve contiguous memory of Size= 131072.
2004-08-02 18:39:20.06 spid152 WARNING: Failed to reserve contiguous memory of Size= 131072.
2004-08-02 18:39:20.08 spid111 Buffer Distribution: Stolen=4294962102 Free=1068 Procedures=226183
Inram=0 Dirty=17110 Kept=0
I/O=0, Latched=1803, Other=525668
2004-08-02 18:39:20.09 spid111 Buffer Counts: Commited=766638 Target=766638 Hashed=544580
InternalReservation=346 ExternalReservation=2232 Min Free=472
2004-08-02 18:39:20.09 spid111 Procedure Cache: TotalProcs=69335 TotalPages=226183 InUsePages=102704
2004-08-02 18:39:20.09 spid111 Dynamic Memory Manager: Stolen=219831 OS Reserved=33432
OS Committed=29744
OS In Use=26400
Query Plan=235911 Optimizer=138
General=8863
Utilities=390 Connection=555
2004-08-02 18:39:20.09 spid111 Global Memory Objects: Resource=2422 Locks=104
SQLCache=5880 Replication=2
LockBytes=2 ServerGlobal=76
Xact=40
2004-08-02 18:39:20.09 spid111 Query Memory Manager: Grants=4 Waiting=0 Maximum=178149 Available=174757
2004-08-02 18:39:20.09 spid108 Buffer Distribution: Stolen=4294962104 Free=1066 Procedures=226183
Inram=0 Dirty=17110 Kept=0
I/O=0, Latched=1803, Other=525668
2004-08-02 18:39:20.09 spid108 Buffer Counts: Commited=766638 Target=766638 Hashed=544580
InternalReservation=346 ExternalReservation=2232 Min Free=472
2004-08-02 18:39:20.09 spid108 Procedure Cache: TotalProcs=69334 TotalPages=226183 InUsePages=102704
2004-08-02 18:39:20.09 spid108 Dynamic Memory Manager: Stolen=219832 OS Reserved=33432
OS Committed=29744
OS In Use=26400
Query Plan=235911 Optimizer=139
General=8863
Utilities=390 Connection=555
2004-08-02 18:39:20.09 spid108 Global Memory Objects: Resource=2422 Locks=104
SQLCache=5880 Replication=2
LockBytes=2 ServerGlobal=76
Xact=40
2004-08-02 18:39:20.09 spid108 Query Memory Manager: Grants=4 Waiting=0 Maximum=178149 Available=174757
2004-08-02 18:39:20.19 spid152 Buffer Distribution: Stolen=43803 Free=1209 Procedures=177046
Inram=0 Dirty=17110 Kept=0
I/O=0, Latched=1802, Other=525668
2004-08-02 18:39:20.19 spid152 Buffer Counts: Commited=766638 Target=766638 Hashed=544580
InternalReservation=346 ExternalReservation=2240 Min Free=472
2004-08-02 18:39:20.19 spid152 Procedure Cache: TotalProcs=67789 TotalPages=177046 InUsePages=102449
2004-08-02 18:39:20.19 spid152 Dynamic Memory Manager: Stolen=219642 OS Reserved=33400
OS Committed=29718
OS In Use=26376
Query Plan=235834 Optimizer=0
General=8855
Utilities=390 Connection=555
2004-08-02 18:39:20.19 spid152 Global Memory Objects: Resource=2422 Locks=104
SQLCache=5881 Replication=2
LockBytes=2 ServerGlobal=76
Xact=40
2004-08-02 18:39:20.19 spid152 Query Memory Manager: Grants=4 Waiting=0 Maximum=178149 Available=174757
-
also take a look at KB 832674 (hotfix available !)
Johan
Learn to play, play to learn !Dont drive faster than your guardian angel can fly ...
but keeping both feet on the ground wont get you anywhere :w00t:- How to post Performance Problems
- How to post data/code to get the best help[/url]- How to prevent a sore throat after hours of presenting ppt
press F1 for solution, press shift+F1 for urgent solution 😀
Need a bit of Powershell? How about this
Who am I ? Sometimes this is me but most of the time this is me
-
What is the value of max server memory ?
-
Min server memory = 0
Max server memory = 6GB
Thus, 2GB open for OS. The only other software running on this machine is SQLLitespeed, which has a small memory footprint, because it is only invoked from code (never manually), and only invoked for 2 short periods per 24 hour day.
-
We opened an issue with Microsoft, and their resolution was the hotfix in this KB (below); .
I'm surprised by the article, which basically says there is a memory managment problem happening somewhere between the OS & SQL Server or something, on a multiprocessor multiGB memory machine. I am surprised because
1) we are using the best software Microsoft provides: SQL 2000 Enterprise Edition, Windows 2003 Enterprise Edition, all software up to most recent service pack
2) I was under the impression that Microsoft's strategy with Yukon/SQL 2005 is to do exactly as this KB problem is stating: serve a single db on a large multiprocessor, multiGB memory machine, as opposed to many smaller distributed machines ("server farm").
Anyone have any opinions on this? I'm wondering that if we have trouble with the software we have now, will we have similar trouble with Yukon/SQL 2005?
Here is the KB:
http://support.microsoft.com/default.aspx?scid=kb;EN-US;838765
-
We ran into this on a 4-way machine running win2k and sql2k. MS recommended that we have use the '-g 384' switch for SQL Server startup. That reserves more space for COM objects and extended stored procedures.
We ended up having to increase to '-g 512'. But the problem has not reoccurred since then.
Viewing 6 posts - 1 through 5 (of 5 total)
You must be logged in to reply to this topic. Login to reply