Select the product you need help with

FIX: You receive error 5180 when you run a parallel query and the combined maximum size of all of the search arguments exceeds 8 KB

Article ID: 815183 - View products that this article applies to.

BUG #: 364146 (SQL Server 8.0)

SYMPTOMS

You have a SQL query that contains many different search arguments. When you execute this SQL query with a parallel query plan in Microsoft SQL Server 2000 Service Pack 3 (SP3), the query may write beyond the bounds of an allocated buffer. This memory overwrite can lead to various exceptions, in-memory data corruption, or runtime errors. These problems may occur either while the specific query is running or after the query finishes, when another thread tries to access the overwritten memory.

Under the circumstances in which this problem was originally reported, the offending query reports the following error message:

2003-02-14 14:42:25.79 spid51 Error: 5180, Severity: 22, State: 1
2003-02-14 14:42:25.79 spid51 Could not open FCB for invalid file ID %d in database '%.*ls'.

This problem can occur when the combined maximum size of all the search arguments exceeds 8 KB. This behavior occurs when one of the following conditions is true:

You use a small number of predicates. For example, you may use two varchar(5000) columns.
You use a larger number of small values. For example, you may use hundreds of values in a large IN list or many OR predicates.

Back to the top | Give Feedback

RESOLUTION

Service pack information

To resolve this problem, obtain the latest service pack for Microsoft SQL Server 2000. For more information, click the following article number to view the article in the Microsoft Knowledge Base:

290211

(http://support.microsoft.com/kb/290211/ )

How to obtain the latest SQL Server 2000 service pack

Hotfix information

The English version of this hotfix has the file attributes (or later file attributes) 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
   -------------------------------------------------------------------
   26-Feb-2003  03:41  2000.80.777.0      29,244  Dbmslpcn.dll     
   08-Feb-2003  05:43                    786,432  Distmdl.ldf
   08-Feb-2003  05:43                  2,359,296  Distmdl.mdf
   30-Jan-2003  01:55                        180  Drop_repl_hotfix.sql
   01-Feb-2003  00:32  2000.80.763.0   1,557,052  Dtsui.dll        
   30-Jan-2003  05:18                    746,470  Instdist.sql
   30-Jan-2003  01:55                      1,402  Inst_repl_hotfix.sql
   08-Feb-2003  06:40  2000.80.765.0      90,692  Msgprox.dll      
   08-Feb-2003  03:53                  1,065,895  Replmerg.sql
   08-Feb-2003  06:40  2000.80.765.0     221,768  Replprov.dll     
   08-Feb-2003  06:40  2000.80.765.0     307,784  Replrec.dll      
   30-Jan-2003  05:18                  1,084,318  Replsys.sql
   28-Feb-2003  01:34  2000.80.778.0     176,696  Sqlmap70.dll     
   08-Feb-2003  06:40  2000.80.765.0      57,920  Sqlrepss.dll     
   03-Mar-2003  19:15  2000.80.780.0   7,516,241  Sqlservr.exe     
   08-Feb-2003  06:40  2000.80.765.0      45,644  Sqlvdi.dll       
   26-Feb-2003  03:41  2000.80.777.0      29,244  Ssmslpcn.dll     
   26-Feb-2003  03:41  2000.80.777.0      82,492  Ssnetlib.dll     
   28-Feb-2003  01:34  2000.80.778.0      98,872  Xpweb70.dll

Note Because of file dependencies, the most recent hotfix or feature that contains these files may also contain additional files.

Back to the top | Give Feedback

WORKAROUND

To work around this problem, you can disable parallelism by using one of the following methods:

To disable parallelism at the DML statement level, specify an OPTION (MAXDOP 1) statement level hint for the DML statement where the problem occurs.
To disable parallelism for the server, run the following Transact-SQL statement in SQL Query Analyzer:
use master go sp_configure 'max degree of parallelism', '1' go
For more information about the max degree of parallelism option, visit the following Microsoft Web site:
http://msdn2.microsoft.com/en-us/library/aa196725(SQL.80).aspx
(http://msdn2.microsoft.com/en-us/library/aa196725(SQL.80).aspx)

Back to the top | Give Feedback

STATUS

Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.This problem was first corrected in Microsoft SQL Server 2000 Service Pack 4.

Back to the top | Give Feedback