FIX: Optimizer May Consume Too Much Memory if Address Windowing Extensions (AWE) is Enabled (323212)



The information in this article applies to:

  • Microsoft SQL Server 2000 (all editions)

This article was previously published under Q323212
BUG #: 358007 (SHILOH_BUGS)

SYMPTOMS

The optimizer may consume too much SQL Server memory when Microsoft Windows 2000 Address Windowing Extensions (AWE) support is enabled. In rare circumstances, this may cause the server to stop responding. Additionally, the following errors may show up repeatedly in the error log until the server is restarted, or the queries that are consuming the optimizer memory either complete or are canceled:
BPool::Map: no remappable address found
Error: 17803, Severity 20, State 14 Insufficient memory available
The SQL Server error log may also show output similar to this:
2002-05-28 15:14:39.28 spid4     Dynamic Memory Manager:  Stolen=335656 OS 
Reserved=1864 
		OS Committed=4294860732
		OS In Use=1775
		Query Plan=108 Optimizer=334000
		General=3051
		Utilities=178 Connection=94
					
If this problem occurs, the output will show a large number of buffers in use by the optimizer (greater than 200,000, or greater than 300,000 if the /3GB switch is enabled in the Boot.ini file).

RESOLUTION

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:

290211 INF: How To Obtain the Latest SQL Server 2000 Service Pack

NOTE: The following hotfix was created before the release of Microsoft SQL Server 2000 Service Pack 3.

The English version of this fix has the file attributes (or later) that are listed in the following table. The dates and times for these files are listed in coordinated universal time (UTC). When you view the file information, it is converted to local time. To find the difference between UTC and local time, use the Time Zone tab in the Date and Time tool in Control Panel.
   Date          Time    Version         Size              File name
   ---------------------------------------------------------------------

   17-May-2002   16:44   2000.80.629.0   7,454,804 bytes   Sqlservr.exe     
				
NOTE: Because of file dependencies, the most recent hotfix or feature that contains the files may also contain additional files.


STATUS

Microsoft has confirmed that this is a problem in the Microsoft products that are listed at the beginning of this article.
This problem was first corrected in Microsoft SQL Server 2000 Service Pack 3.

Modification Type:MinorLast Reviewed:9/27/2005
Keywords:kbHotfixServer kbQFE kbbug kbfix kbSQLServ2000preSP3fix kbSQLServ2000sp3fix KB323212 kbAudDeveloper