Microsoft KB Archive/909003

= Error message when you run a DBCC check command in SQL Server 2005: &quot;8909 16 1 Table error: Object ID 0, index ID -1, partition ID 0, alloc unit ID 0 (type unknown)&quot; =

Article ID: 909003

Article Last Modified on 6/8/2006

-

APPLIES TO


 * Microsoft SQL Server 2005 Standard Edition
 * Microsoft SQL Server 2005 Enterprise Edition
 * Microsoft SQL Server 2005 Developer Edition
 * Microsoft SQL Server 2005 Workgroup Edition

-



BUG #: 20010946 (SQLBUDT)



SYMPTOMS
When you run a DBCC check command in Microsoft SQL Server 2005, you may receive an error message that resembles the following:

8909 16 1

Table error: Object ID 0, index ID -1, partition ID 0, alloc unit ID 0

(type Unknown), page ID (6:8040) contains an incorrect page ID in its page header. The PageId in the

page header = (0:0).

When the DBCC check command is running for a database that is stored on an NTFS file system partition, and the NTFS partition is in MULTI-USER mode, the SQL Server database engine creates an internal, read-only database snapshot. This behavior prevents blocking problems and concurrency problems when the DBCC check command is run. A database snapshot uses one or more sparse files to store data.

The problem occurs when the following conditions are true:
 * SQL Server pages have been written to sparse files.
 * These sparse files are used for DBCC replicas and for the database snapshot.
 * These sparse files are lost.

Because the sparse files are lost, SQL Server reads zeroed data on those pages when you run the DBCC check command.

Note This behavior may cause a false failure to occur when you run the DBCC check command. Because the DBCC check command operates on an internal, read-only database snapshot, the command does not indicate that the database itself is damaged. The command only indicates that there is a problem with the internal, read-only database snapshot.



CAUSE
This problem may occur because of a race condition. The race condition occurs in an asynchronous non-cached write operation to an NTFS sparse file.



MORE INFORMATION
When the page ID is 0:0, you may also receive an error message that resembles the following:

Error: 824, Severity: 24, State: 2. SQL Server detected a logical consistency-based I/O error: incorrect pageid (expected 30:62; actual 0:0).

Keywords: kbtshoot kbfix kbprb KB909003

-

[mailto:TECHNET@MICROSOFT.COM Send feedback to Microsoft]

© Microsoft Corporation. All rights reserved.