You are currently offline, waiting for your internet to reconnect

FIX: Parallel Plan for Index Creation of Non-Clustered Index May Result in Use of Pages That are not Allocated

This article was previously published under Q291566
This article has been archived. It is offered "as is" and will no longer be updated.
BUG #: 352345 (SHILOH_bugs)
When non-clustered indexes are created with the CREATE INDEX, ALTER TABLE, or DBCC DBREINDEX statements by using a parallel plan, pages may be used in the index that were not allocated. Use of the unallocated pages may lead to one or more of the following error messages as reported by DBCC CHECKDB or CHECKTABLE:
Msg 8976, Level 16, State 1
Table error: Object ID 1993058136, index ID 2. Page (1:385) was not seen in the scan although its parent (1:445) and previous (1:384) refer to it. Check any previous errors.
Msg 8978, Level 16, State 1
Table error: Object ID 1993058136, index ID 2. Page (1:125) is missing a reference from previous page (1:387). Possible chain linkage problem.
Msg 8980, Level 16, State 1Table error: Object ID 1993058136, index ID 2. Index node page (1:445), slot 4 refers to child page (1:386) and previous child (1:385), but they were not encountered.
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 theMicrosoft Knowledge Base:
290211 INF: How to Obtain the Latest SQL Server 2000 Service Pack


NOTE: The following hotfix was created prior to Microsoft SQL Server 2000 Service Pack 1.

The English version of this fix should have the following file attributes or later:
   Version      File name   Platform   ---------------------------------   8.00.262     s80262i.exe Intel				
NOTE: Due to file dependencies, the most recent hotfix or feature that contains the preceding files may also contain additional files.
Change the configuration value for the "max degree of parallelism" option to 1 to avoid the use of a parallel plan to build an index.
Microsoft has confirmed that this is a problem in Microsoft SQL Server 2000. This problem was first corrected in SQL Server 2000 Service Pack 1.
This problem only occurs on the Microsoft SQL Server 2000 Enterprise Edition because that package is required to allow parallel creation of an index.

Article ID: 291566 - Last Review: 01/16/2015 21:54:58 - Revision: 2.1

Microsoft SQL Server 2000 Enterprise Edition

  • kbnosurvey kbarchive kbbug kbfix kbqfe kbsqlserv2000sp1fix KB291566