FIX: Error 1105 on Default Segment When Running DBCC DBREINDEX (164578)



The information in this article applies to:

  • Microsoft SQL Server 6.5

This article was previously published under Q164578
BUG #: 16286

SYMPTOMS

When you run DBCC DBREINDEX with a fillfactor of 0, you may experience error 1105 (Can't allocate space) or errors on the "default" segment, even though there is plenty of space available for this segment within the database.

CAUSE

Running DBCC DBREINDEX(<tablename>,'',0) exposes this intermittent bug. Specifying a non-zero fillfactor avoids the problem. In some cases, once you have experienced this error, you may not be able to build any new indexes on any table, even in other databases on the same SQL Server.

The fillfactor used when originally creating the index makes no difference to this behavior. Also, using the "SORTED_DATA" option has no effect on the problem.

Shutting down and restarting the server may temporarily clear the symptoms of this bug. However, a shut down is unnecessary when using the workaround described below.

WORKAROUND

To work around this problem, specify a fillfactor other than 0; that is, explicitly code the appropriate fillfactor for the index in question.

STATUS

Microsoft has confirmed this to be a problem in Microsoft SQL Server version 6.5. This problem has been corrected in U.S. Service Pack 3 for Microsoft SQL Server version 6.5. For more information, contact your primary support provider.

Modification Type:MajorLast Reviewed:10/3/2003
Keywords:kbfix kbusage KB164578