FIX: Error 1105 on Default Segment When Running DBCC DBREINDEX

 Last reviewed: June 27, 1997
Article ID: Q164578
The information in this article applies to:
  • Microsoft SQL Server, version 6.5
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.

Keywords : kbusage SSrvAdmin SSrvGen kbbug6.5 kbbuglist
Version : 6.5
Platform : WinNT

THE INFORMATION PROVIDED IN THE MICROSOFT KNOWLEDGE BASE IS PROVIDED "AS IS" WITHOUT WARRANTY OF ANY KIND. MICROSOFT DISCLAIMS ALL WARRANTIES, EITHER EXPRESS OR IMPLIED, INCLUDING THE WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE. IN NO EVENT SHALL MICROSOFT CORPORATION OR ITS SUPPLIERS BE LIABLE FOR ANY DAMAGES WHATSOEVER INCLUDING DIRECT, INDIRECT, INCIDENTAL, CONSEQUENTIAL, LOSS OF BUSINESS PROFITS OR SPECIAL DAMAGES, EVEN IF MICROSOFT CORPORATION OR ITS SUPPLIERS HAVE BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES. SOME STATES DO NOT ALLOW THE EXCLUSION OR LIMITATION OF LIABILITY FOR CONSEQUENTIAL OR INCIDENTAL DAMAGES SO THE FOREGOING LIMITATION MAY NOT APPLY.

Last reviewed: June 27, 1997
© 1998 Microsoft Corporation. All rights reserved. Terms of Use.