FIX: sysindexes.statblob Column May Be Corrupted After You Run a DBCC DBREINDEX Statement

View products that this article applies to.

Bug #: 364183 (SHILOH_BUGS)

SYMPTOMS

After you run a DBCC DBREINDEX statement, the sysindexes.statblob column may be corrupted if all the following conditions are true:

The table includes a computed column.
Some columns in the table are referenced by two or more statistics or indexes.
An indexed view references the table.
The table is reindexed by using DBCC DBREINDEX.
The auto create statistics database option is enabled for the database.

When you run a DBCC CHECKDB statement, you receive the following corruption errors on the sysindexes.statblob column:

Server: Msg 8964, Level 16, State 1, Line 2 Table error: Object ID 2. The text, ntext, or image node at page (1:64), slot 29, text ID 6815744 is not referenced.

-and-

Server: Msg 2576, Level 16, State 1, Line 2 IAM page (0:0) is pointed to by the previous pointer of IAM page (1:88) object ID 1977058079 index ID 2 but was not detected in the scan.

Back to the top

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 (http://support.microsoft.com/kb/290211/ ) How to obtain the latest SQL Server 2000 service pack

Back to the top

Hotfix information

The hotfix below can be applied to SQL Server 2000 Service Pack 3.

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

WORKAROUND

To work around this problem, disable the auto create statistics database option for the affected database.

Note If you disable the auto create statistics database option, the query optimizer may sometimes not be able to select the best query plans.

Back to the top

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