8978, 8909, 8928 errors on INDEXES | SQL Server Performance Forums

SQL Server Performance Forum – Threads Archive

8978, 8909, 8928 errors on INDEXES

Hello. Periodically on a database where replication is enabled we are getting the above 3 errors on both a PK constraint index and a Non Clustered index on the same table. Why would this happen and what can be done to fix this. We do not have parallelism enabled nor auto shrink. see below for error. Msg 8909, Sev 16: Table error: Object ID 1977058079, index ID 2, page ID (1:1828241). The PageId in the page header = (1:870563). [SQLSTATE 42000]
Msg 8978, Sev 16: Table error: Object ID 1977058079, index ID 4. Page (1:1828240) is missing a reference from previous page (1:1828241). Possible chain linkage problem. [SQLSTATE 42000]
Msg 8928, Sev 16: Object ID 1977058079, index ID 4: Page (1:1828241) could not be processed. See other errors for details. [SQLSTATE 42000]

Did you run checkdb and checkalloc?
Luis Martin
Moderator
SQL-Server-Performance.com The views expressed here are those of the author and no one else. There are no warranties as to the reliability or accuracy of anything presented here.
What is the level of service pack on the SQL Server. When non-clustered indexes are created with the CREATE INDEX, ALTER TABLE, or DBCC DBREINDEX statements by using a parallel plan, pages may be used in the index that were not allocated. Use of the unallocated pages may lead to one or more of the following error messages as reported by DBCC CHECKDB or CHECKTABLE Change the configuration value for the "max degree of parallelism" option to 1 to avoid the use of a parallel plan to build an index. Refer to this KBA http://support.microsoft.com/default.aspx?scid=kb;en-us;308795] for information. Satya SKJ
Moderator
http://www.SQL-Server-Performance.Com/forum
This posting is provided “AS IS” with no rights for the sake of knowledge sharing.
]]>