FIX: "bufferLen >= colLen" assertion when you run a parallel query in SQL Server 2008, in SQL Server 2008 R2 or in SQL Server 2012

Article ID: 2665649
Microsoft distributes Microsoft SQL Server 2008, Microsoft SQL Server 2008 R2 or Microsoft SQL Server 2012 fixes as one downloadable file. Because the fixes are cumulative, each new release contains all the hotfixes and all the security fixes that were included with the previous SQL Server 2008, SQL Server 2008 R2 or SQL Server 2012 fix release.
Expand all | Collapse all

On This Page

Symptoms

Assume that you run a parallel query in SQL Server 2008, in SQL Server 2008 R2 or in SQL Server 2012. When a query plan that is created by Query Optimizer uses a hash join for the parallel query execution, a "bufferLen >= colLen" assertion might occur. Additionally, a mini-dump file is generated in the SQL Server log folder, and the following error message is logged in the SQL Server error log file:
<Date><Time> <spid> Error: 17066, Severity: 16, State: 1.
<Date><Time> <spid> SQL Server Assertion: File: <e:\sql10_katmai_t\sql\ntdbms\storeng\dfs\access\sebind.h>, line=1139 Failed Assertion = 'bufferLen >= colLen'. This error may be timing-related. If the error persists after rerunning the statement, use DBCC CHECKDB to check the database for structural integrity, or restart the server to ensure in-memory data structures are not corrupted.

<Date><Time> <spid> * BEGIN STACK DUMP:
<Date><Time> <spid> * <Date><Time> <spid>
<Date><Time> <spid> *
<Date><Time> <spid> * Location: e:\sql10_katmai_t\sql\ntdbms\storeng\dfs\access\sebind.h:1139
<Date><Time> <spid> * Expression: bufferLen >= colLen
Back to the top | Give Feedback

Resolution

Cumulative update information

SQL Server 2008 R2 Service Pack 2

The fix for this issue was first released in Cumulative Update 1 for SQL Server 2008 R2 Service Pack 2. For more information about how to obtain this cumulative update package, click the following article number to view the article in the Microsoft Knowledge Base:
2720425
(http://support.microsoft.com/kb/2720425/ )
Cumulative Update package 1 for SQL Server 2008 R2 Service Pack 2
Note Because the builds are cumulative, each new fix release contains all the hotfixes and all the security fixes that were included with the previous SQL Server 2008 R2 fix release. We recommend that you consider applying the most recent fix release that contains this hotfix. For more information, click the following article number to view the article in the Microsoft Knowledge Base:
2730301
(http://support.microsoft.com/kb/2730301/ )
The SQL Server 2008 R2 builds that were released after SQL Server 2008 R2 Service Pack 2 was released

SQL Server 2012

The fix for this issue was first released in Cumulative Update 2 for SQL Server 2012. For more information about this cumulative update package, click the following article number to view the article in the Microsoft Knowledge Base:
2703275
(http://support.microsoft.com/kb/2703275/LN/ )
Cumulative update package 2 for SQL Server 2012
Note Because the builds are cumulative, each new fix release contains all the hotfixes and all the security fixes that were included with the previous SQL Server 2012 fix release. Microsoft recommends that you consider applying the most recent fix release that contains this hotfix. For more information, click the following article number to view the article in the Microsoft Knowledge Base:
2692828
(http://support.microsoft.com/kb/2692828/LN/ )
The SQL Server 2012 builds that were released after SQL Server 2012 was released
You must apply a SQL Server 2012 hotfix to an installation of SQL Server 2012.

SQL Server 2008 R2 Service Pack 1

The fix for this issue was first released in Cumulative Update 6 for SQL Server 2008 R2 Service Pack 1. For more information about how to obtain this cumulative update package, click the following article number to view the article in the Microsoft Knowledge Base:
2679367
(http://support.microsoft.com/kb/2679367/ )
Cumulative Update package 6 for SQL Server 2008 R2 Service Pack 1
Note Because the builds are cumulative, each new fix release contains all the hotfixes and all the security fixes that were included with the previous SQL Server 2008 R2 fix release. We recommend that you consider applying the most recent fix release that contains this hotfix. For more information, click the following article number to view the article in the Microsoft Knowledge Base:
2567616
(http://support.microsoft.com/kb/2567616/ )
The SQL Server 2008 R2 builds that were released after SQL Server 2008 R2 Service Pack 1 was released

SQL Server 2008 R2

The fix for this issue was first released in Cumulative Update 13. For more information about how to obtain this cumulative update package for SQL Server 2008 R2, click the following article number to view the article in the Microsoft Knowledge Base:
2679366
(http://support.microsoft.com/kb/2679366/ )
Cumulative Update package 13 for SQL Server 2008 R2
Note Because the builds are cumulative, each new fix release contains all the hotfixes and all the security fixes that were included with the previous SQL Server 2008 R2 fix release. We recommend that you consider applying the most recent fix release that contains this hotfix. For more information, click the following article number to view the article in the Microsoft Knowledge Base:
981356
(http://support.microsoft.com/kb/981356/ )
The SQL Server 2008 R2 builds that were released after SQL Server 2008 R2 was released

SQL Server 2008 Service Pack 3

The fix for this issue was first released in Cumulative Update 4 for SQL Server 2008 Service Pack 3. For more information about how to obtain this cumulative update package, click the following article number to view the article in the Microsoft Knowledge Base:
2673383
(http://support.microsoft.com/kb/2673383/ )
Cumulative update package 4 for SQL Server 2008 Service Pack 3
Note Because the builds are cumulative, each new fix release contains all the hotfixes and all the security fixes that were included with the previous SQL Server fix release. We recommend that you consider applying the most recent fix release that contains this hotfix. For more information, click the following article number to view the article in the Microsoft Knowledge Base:
2629969
(http://support.microsoft.com/kb/2629969/ )
The SQL Server 2008 builds that were released after SQL Server 2008 Service Pack 3 was released
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.
Back to the top | Give Feedback

Workaround

To work around this issue, use one of the following methods:
  • Set the MAXDOP query hint option to 1.
  • Set the Max Degree of Parallelism option to 1.
Back to the top | Give Feedback

References

For more information about the Incremental Servicing Model for SQL Server, click the following article number to view the article in the Microsoft Knowledge Base:
935897
(http://support.microsoft.com/kb/935897/ )
An Incremental Servicing Model is available from the SQL Server team to deliver hotfixes for reported problems
For more information about the naming schema for SQL Server updates, click the following article number to view the article in the Microsoft Knowledge Base:
822499
(http://support.microsoft.com/kb/822499/ )
Naming schema for Microsoft SQL Server software update packages
For more information about software update terminology, click the following article number to view the article in the Microsoft Knowledge Base:
824684
(http://support.microsoft.com/kb/824684/ )
Description of the standard terminology that is used to describe Microsoft software updates
Back to the top | Give Feedback

Properties

Article ID: 2665649 - Last Review: November 21, 2012 - Revision: 5.1
Keywords: 
kbtshoot kbqfe kbfix kbexpertiseadvanced kbsurveynew KB2665649
Back to the top | Give Feedback

Give Feedback

 
Back to the topBack to the top