https://www.betaarchive.com/wiki/index.php?title=Microsoft_KB_Archive/319477&feed=atom&action=history
Microsoft KB Archive/319477 - Revision history
2024-03-28T18:21:15Z
Revision history for this page on the wiki
MediaWiki 1.39.3
https://www.betaarchive.com/wiki/index.php?title=Microsoft_KB_Archive/319477&diff=175981&oldid=prev
3155ffGd: importing KB archive
2020-07-18T16:48:53Z
<p>importing KB archive</p>
<p><b>New page</b></p><div><div id="nsbanner"><br />
<br />
<div id="bannerrow1"><br />
<br />
{|<br />
| Knowledge Base<br />
|<br />
|}<br />
<br />
<br />
</div><br />
<div id="TitleRow"><br />
<br />
= <span id="KB319477"></span>FIX: Extremely Large Number of User Tables on AWE System May Cause BPool::Map Errors =<br />
<br />
<br />
</div><br />
<br />
</div><br />
<div id="nstext" valign="BOTTOM"><br />
<br />
Article ID: 319477<br />
<br />
Article Last Modified on 11/2/2007<br />
<br />
<br />
-----<br />
<br />
APPLIES TO<br /><br />
<br /><br />
<br />
* Microsoft SQL Server 2000 Developer Edition<br />
* Microsoft SQL Server 2000 Standard Edition<br />
* Microsoft SQL Server 2000 Enterprise Edition<br />
* Microsoft SQL Server 2000 Personal Edition<br />
* Microsoft SQL Server 2000 Enterprise Edition<br />
* Microsoft SQL Server 2000 Workgroup Edition<br />
* Microsoft SQL Server 2000 Desktop Engine (Windows)<br />
* Microsoft SQL Server 2000 Developer Edition<br />
* Microsoft SQL Server 2000 Enterprise Edition 64-bit<br />
<br />
<br />
-----<br />
<br />
<div class="notice_section"><br />
<br />
This article was previously published under Q319477<br />
<br />
</div><br />
<div class="notice_section"><br />
<br />
BUG #: 356784 (SHILOH_BUGS)<br />
<br />
</div><br />
<div class="symptoms_section"><br />
<br />
== SYMPTOMS ==<br />
<br />
On systems that have a large number of user tables (typically 100000 or more) that are running with Address Windowing Extensions (AWE) turned on, SQL Server may log the following error message in the SQL Server error log:<br />
<div class="errormessage"><br />
<br />
BPool::Map: no remappable address found.<br />
<br />
</div><br />
<div class="errormessage"><br />
<br />
Error: 17803, Severity 20, State 14<br /><br />
Insufficient memory available<br />
<br />
</div><br />
The 17803 error messages may have state numbers other than 14, but the BPool::Map error should always show up first.<br /><br />
<br /><br />
There may be additional information in the SQL Server error log similar to:<br />
<pre class="fixed_text">2002-04-09 15:09:18.82 spid77 Query Memory Manager: Grants=2 Waiting=0 Maximum=2229 Available=762<br />
2002-04-09 15:09:19.04 spid68 Buffer Distribution: Stolen=203317 Free=333 Procedures=161<br />
Inram=0 Dirty=16283 Kept=0<br />
I/O=0, Latched=479, Other=450547<br />
2002-04-09 15:09:19.04 spid68 Buffer Counts: Commited=671120 Target=671120 Hashed=467309<br />
InternalReservation=667 ExternalReservation=1299 Min Free=512<br />
2002-04-09 15:09:19.04 spid68 Procedure Cache: TotalProcs=36 TotalPages=161 InUsePages=79<br />
2002-04-09 15:09:19.04 spid68 Dynamic Memory Manager: Stolen=203310 OS Reserved=1664 <br />
OS Committed=1635<br />
OS In Use=1599<br />
Query Plan=204 Optimizer=201546<br />
General=2887<br />
Utilities=49 Connection=223<br />
2002-04-09 15:09:19.04 spid68 Global Memory Objects: Resource=1984 Locks=289 <br />
SQLCache=101 Replication=2<br />
LockBytes=2 ServerGlobal=43<br />
Xact=37<br />
</pre><br />
'''NOTE''': In this SQL Server error log text, the word &quot;Commited&quot; is a misspelling for the word &quot;Committed.&quot;<br /><br />
<br /><br />
In the failure case, the number reported as &quot;Latched&quot; is typically several thousand.<br /><br />
<br /><br />
<br />
<br />
</div><br />
<div class="cause_section"><br />
<br />
== CAUSE ==<br />
<br />
The lazywriter process has an incorrect calculation for determining whether it needs to run and free up infrequently used buffers so that they are available for mapping in AWE buffers.<br />
<br />
</div><br />
<div class="resolution_section"><br />
<br />
== RESOLUTION ==<br />
<br />
=== Service pack information ===<br />
<br />
To resolve this problem, obtain the latest service pack for Microsoft SQL Server 2000. For additional information, click the following article number to view the article in the Microsoft Knowledge Base:<br />
<div class="indent"><br />
<br />
[[../290211|290211]] How to obtain the latest SQL Server 2000 service pack<br />
<br />
<br />
</div><br />
=== Hotfix information ===<br />
<br />
==== SQL Server 2000 Service Pack 2 ====<br />
<br />
The English version of this fix should have the following file attributes or later:<br />
<pre class="fixed_text"> Version File name<br />
----------------------------<br />
<br />
8.00.0594 Sqlservr.exe<br />
</pre><br />
==== SQL Server 2000 Service Pack 3 ====<br />
<br />
The English version of this fix should have the following file attributes or later:<br />
<pre class="fixed_text"> Version File name<br />
----------------------------<br />
<br />
8.00.0840 Sqlservr.exe<br />
</pre><br />
<br /><br />
'''NOTE''': Because of file dependencies, the most recent hotfix or feature that contains the files may also contain additional files.<br /><br />
<br /><br />
<br /><br />
<br />
<br />
</div><br />
<div class="status_section"><br />
<br />
== STATUS ==<br />
<br />
Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the &quot;Applies to&quot; section.This problem was first corrected in Microsoft SQL Server 2000 Service Pack 4.<br />
<br />
</div><br />
Keywords: kbbug kbfix kbqfe kbsqlserv2000presp4fix kbhotfixserver KB319477<br />
<br />
<div class="footer"><br />
<br />
<br /><br />
<br />
<br />
-----<br />
<br />
[mailto:TECHNET@MICROSOFT.COM Send feedback to Microsoft]<br />
<br />
<span>© Microsoft Corporation. All rights reserved.</span><br />
<br />
<br />
</div><br />
<br />
</div></div>
3155ffGd