SQL Server Errors or Failures from Error: 8975 to Error: 8994

SQLServerF1

 

Error: 8975, Severity: 10, DBCC cross-rowset check failed for object ‘%.*ls’ (object ID %d) due to internal query error %d, severity %d, state %d. Refer to Books Online for more information on this error.
Error: 8976, Severity: 16, Table error: Object ID %d, index ID %d, partition ID %I64d, alloc unit ID %I64d (type %.*ls). Page %S_PGID was not seen in the scan although its parent %S_PGID and previous %S_PGID refer to it. Check any previous errors.
Error: 8977, Severity: 16, Table error: Object ID %d, index ID %d, partition ID %I64d, alloc unit ID %I64d (type %.*ls). Parent node for page %S_PGID was not encountered.

Error: 8978, Severity: 16, Table error: Object ID %d, index ID %d, partition ID %I64d, alloc unit ID %I64d (type %.*ls). Page %S_PGID is missing a reference from previous page %S_PGID. Possible chain linkage problem.
Error: 8979, Severity: 16, Table error: Object ID %d, index ID %d, partition ID %I64d, alloc unit ID %I64d (type %.*ls). Page %S_PGID is missing references from parent (unknown) and previous (page %S_PGID) nodes. Possible bad root entry in system catalog.
Error: 8980, Severity: 16, Table error: Object ID %d, index ID %d, partition ID %I64d, alloc unit ID %I64d (type %.*ls). Index node page %S_PGID, slot %d refers to child page %S_PGID and previous child %S_PGID, but they were not encountered.
Error: 8981, Severity: 16, Table error: Object ID %d, index ID %d, partition ID %I64d, alloc unit ID %I64d (type %.*ls). The next pointer of %S_PGID refers to page %S_PGID. Neither %S_PGID nor its parent were encountered. Possible bad chain linkage.

Error: 8982, Severity: 16, Table error: Cross object linkage. Page %S_PGID->next in object ID %d, index ID %d, partition ID %I64d, AU ID %I64d (type %.*ls) refers to page %S_PGID in object ID %d, index ID %d, partition ID %I64d, AU ID %I64d (type %.*ls) but is not in the same index
Error: 8983, Severity: 10, File %d. Extents %I64d, used pages %I64d, reserved pages %I64d, mixed extents %I64d, mixed pages %I64d.
Error: 8984, Severity: 16, Table error: object ID %d, index ID %d, partition ID %I64d. A row should be on partition number %d but was found in partition number %d. Possible extra or invalid keys for:
Error: 8985, Severity: 16, Could not locate file ‘%.*ls’ for database ‘%.*ls’ in sys.database_files. The file either does not exist, or was dropped.
Error: 8986, Severity: 16, Too many errors found (%d) for object ID %d. To see all error messages rerun the statement using “WITH ALL_ERRORMSGS”.
Error: 8987, Severity: 16, No help available for DBCC statement ‘%.*ls’.
Error: 8988, Severity: 16, Row (%d:%d:%d) identified by (%ls).
Error: 8989, Severity: 10, %.*ls found %d allocation errors and %d consistency errors in database ‘%ls’.
Error: 8990, Severity: 10, %.*ls found %d allocation errors and %d consistency errors in table ‘%ls’ (object ID %d).
Error: 8991, Severity: 16, 0x%p to 0x%p is not a valid address range.
Error: 8992, Severity: 16, Check Catalog Msg %d, State %d: %.*ls
Error: 8993, Severity: 16, Object ID %d, forwarding row page %S_PGID, slot %d points to page %S_PGID, slot %d. Did not encounter forwarded row. Possible allocation error.
Error: 8994, Severity: 16, Object ID %d, forwarded row page %S_PGID, slot %d should be pointed to by forwarding row page %S_PGID, slot %d. Did not encounter forwarding row. Possible allocation error.

This is applicable on below versions of SQL Server

SQL Server 2005
SQL Server 2008 R2
SQL Server 2012
SQL Server 2014

Hope this was helpful.

Thanks,
SQLServerF1 Team
In-Depth Blogs on SQL Server, Information about SQL Server Conferences and Events, SQL Server Frequently asked questions, SQL Server Trainings.

 

SQL Server Errors or Failures Error: 2524 to Error: 2544

SQLServerF1

 

Error: 2524, Severity: 16, Cannot process object ID %ld (object “%.*ls”) because it is a Service Broker queue. Try the operation again with the object ID of the corresponding internal table for the queue, found in sys.internal_tables.,
Error: 2525, Severity: 16, Database file %.*ls is offline.,
Error: 2526, Severity: 16, Incorrect DBCC statement. Check the documentation for the correct DBCC syntax and options.,
Error: 2527, Severity: 16, Unable to process index %.*ls of table %.*ls because filegroup %.*ls is offline.,

Error: 2528, Severity: 10, DBCC execution completed. If DBCC printed error messages, contact your system administrator.,
Error: 2529, Severity: 16, Filegroup %.*ls is offline.,
Error: 2530, Severity: 16, The index “%.*ls” on table “%.*ls” is disabled.,
Error: 2531, Severity: 16, Table error: object ID %d, index ID %d, partition ID %I64d, alloc unit ID %I64d (type %.*ls) B-tree level mismatch, page %S_PGID. Level %d does not match level %d from the previous %S_PGID.,
Error: 2532, Severity: 16, One or more WITH options specified are not valid for this command.,
Error: 2533, Severity: 16, Table error: page %S_PGID allocated to object ID %d, index ID %d, partition ID %I64d, alloc unit ID %I64d (type %.*ls) was not seen. The page may be invalid or may have an incorrect alloc unit ID in its header.,

Error: 2534, Severity: 16, Table error: page %S_PGID, whose header indicates that it is allocated to object ID %d, index ID %d, partition ID %I64d, alloc unit ID %I64d (type %.*ls), is allocated by another object.,
Error: 2536, Severity: 10, DBCC results for ‘%.*ls’.,
Error: 2537, Severity: 16, Table error: object ID %d, index ID %d, partition ID %I64d, alloc unit ID %I64d (type %.*ls), page %S_PGID, row %d. The record check (%.*ls) failed. The values are %I64d and %I64d.,
Error: 2538, Severity: 10, File %d. The number of extents = %I64d, used pages = %I64d, and reserved pages = %I64d.,
Error: 2539, Severity: 10, The total number of extents = %I64d, used pages = %I64d, and reserved pages = %I64d in this database.,
Error: 2540, Severity: 10, The system cannot self repair this error.,
Error: 2541, Severity: 10, DBCC UPDATEUSAGE: Usage counts updated for table ‘%.*ls’ (index ‘%.*ls’, partition %ld):,
Error: 2542, Severity: 10, DATA pages %.*ls: changed from (%I64d) to (%I64d) pages.,
Error: 2543, Severity: 10, USED pages %.*ls: changed from (%I64d) to (%I64d) pages.,
Error: 2544, Severity: 10, RSVD pages %.*ls: changed from (%I64d) to (%I64d) pages.,

This is applicable on below versions of SQL Server

SQL Server 2005
SQL Server 2008 R2
SQL Server 2012
SQL Server 2014

Hope this was helpful.

Thanks,
SQLServerF1 Team
In-Depth Blogs on SQL Server, Information about SQL Server Conferences and Events, SQL Server Frequently asked questions, SQL Server Trainings.