BUG: Error Message "Table Corrupt Object ID 0, index ID 0, page ID.." Occurs When You Run DBCC DBREINDEX in SQL Server (277848)



The information in this article applies to:

  • Microsoft SQL Server 7.0
  • Microsoft SQL Server 2000 (all editions)

This article was previously published under Q277848
BUG #: 58052 (SQLBUG_70)
BUG #: 236149 (SHILOH_BUG)

SYMPTOMS

When you run DBCC DBREINDEX concurrently with AutoShrink or DBCC SHRINKDATABASE, the following error message may occur:
Error: 8909
Table Corrupt: Object ID 0, index ID 0, page ID (1:623). PageId in the page header = (0:0).
The error message is not indicative of any actual data corruption in the database. This issue may cause the shrink operation to fail but no persistent data integrity problems occur in the database.

DBCC SHRINKFILE does not seem to produce the error when run concurrently with a reindexing operation.

CAUSE

The problem may occur when you run the shrink database and reindexing operations at the same time. This behavior may be seen primarily in multiprocessor environments.

WORKAROUND

To work around this behavior:
  • If you have a scheduled job to run these two operations at the same time, reschedule the operations to run at different times.

    -or-

  • If the AutoShrink database option is turned on, turn AutoShrink off and schedule a database shrink either through a custom DBCC SHRINKDATABASE job, or by using the sqlmaint utility, through the Database Maintenance Wizard.

STATUS

Microsoft has confirmed this to be a problem in SQL Server 7.0.
Microsoft has confirmed this to be a problem in SQL Server 2000.

MORE INFORMATION

The Database Maintenance Wizard option to shrink the database is Remove Unused space from database files. The corresponding option in the sqlmaint utility is [-RmUnusedSpace].

REFERENCES

For more information about how to shrink a database, see the following topics in SQL Server Books Online:

"DBCC SHRINKDATABASE (T-SQL)"
"DBCC SHRINKFILE (T-SQL)"
"Setting Database Options"

Modification Type:MajorLast Reviewed:10/17/2003
Keywords:kbBug kbCodeSnippet kbpending KB277848