SQL Server Errors or Failures from Error: 8955 to Error: 8974

SQLServerF1

 

Error: 8955, Severity: 16, Data row (%d:%d:%d) identified by (%ls) with index values ‘%ls’.
Error: 8956, Severity: 16, Index row (%d:%d:%d) with values (%ls) pointing to the data row identified by (%ls).
Error: 8957, Severity: 10, %lsDBCC %ls (%ls%ls%ls)%ls executed by %ls found %d errors and repaired %d errors. Elapsed time: %d hours %d minutes %d seconds. %.*ls
Error: 8958, Severity: 10, %ls is the minimum repair level for the errors found by DBCC %ls (%ls%ls%ls).
Error: 8959, Severity: 16, Table error: IAM page %S_PGID for object ID %d, index ID %d, partition ID %I64d, alloc unit ID %I64d (type %.*ls) is linked in the IAM chain for object ID %d, index ID %d, partition ID %I64d, alloc unit ID %I64d (type %.*ls) by page %S_PGID.

Error: 8960, Severity: 16, Table error: Object ID %d, index ID %d, partition ID %I64d, alloc unit ID %I64d (type %.*ls). Page %S_PGID, slot %d, column %d is not a valid complex column.
Error: 8961, Severity: 16, Table error: Object ID %d, index ID %d, partition ID %I64d, alloc unit ID %I64d (type %.*ls). The off-row data node at page %S_PGID, slot %d, text ID %I64d does not match its reference from page %S_PGID, slot %d.
Error: 8962, Severity: 16, Table error: Object ID %d, index ID %d, partition ID %I64d, alloc unit ID %I64d (type %.*ls). The off-row data node at page %S_PGID, slot %d, text ID %I64d has incorrect node type %d.
Error: 8963, Severity: 16, Table error: Object ID %d, index ID %d, partition ID %I64d, alloc unit ID %I64d (type %.*ls). The off-row data node at page %S_PGID, slot %d, text ID %I64d has type %d. It cannot be placed on a page of type %d.

Error: 8964, Severity: 16, Table error: Object ID %d, index ID %d, partition ID %I64d, alloc unit ID %I64d (type %.*ls). The off-row data node at page %S_PGID, slot %d, text ID %I64d is not referenced.
Error: 8965, Severity: 16, Table error: Object ID %d, index ID %d, partition ID %I64d, alloc unit ID %I64d (type %.*ls). The off-row data node at page %S_PGID, slot %d, text ID %I64d is referenced by page %S_PGID, slot %d, but was not seen in the scan.
Error: 8966, Severity: 22, Unable to read and latch page %S_PGID with latch type %ls. %ls failed.
Error: 8967, Severity: 16, An internal error occurred in DBCC that prevented further processing. Contact Customer Support Services.
Error: 8968, Severity: 16, Table error: %ls page %S_PGID (object ID %d, index ID %d, partition ID %I64d, alloc unit ID %I64d (type %.*ls)) is out of the range of this database.
Error: 8969, Severity: 16, Table error: IAM chain linkage error: Object ID %d, index ID %d, partition ID %I64d, alloc unit ID %I64d (type %.*ls). The next page for IAM page %S_PGID is %S_PGID, but the previous link for page %S_PGID is %S_PGID.
Error: 8970, Severity: 16, Row error: Object ID %d, index ID %d, partition ID %I64d, alloc unit ID %I64d (type %.*ls), page ID %S_PGID, row ID %d. Column ‘%.*ls’ was created NOT NULL, but is NULL in the row.
Error: 8971, Severity: 16, Forwarded row mismatch: Object ID %d, partition ID %I64d, alloc unit ID %I64d (type %.*ls) page %S_PGID, slot %d points to forwarded row page %S_PGID, slot %d; the forwarded row points back to page %S_PGID, slot %d
Error: 8972, Severity: 16, Forwarded row referenced by more than one row. Object ID %d, partition ID %I64d, alloc unit ID %I64d (type %.*ls), page %S_PGID, slot %d incorrectly points to the forwarded row page %S_PGID, slot %d, which correctly refers back to page %S_PGID, slot %d.
Error: 8973, Severity: 16, CHECKTABLE object ID %d, index ID %d, partition ID %I64d, alloc unit ID %I64d (type %.*ls) processing encountered page %S_PGID, slot %d twice.
Error: 8974, Severity: 16, Table error: Object ID %d, index ID %d, partition ID %I64d, alloc unit ID %I64d (type %.*ls). The off-row data node at page %S_PGID, slot %d, text ID %I64d is pointed to by page %S_PGID, slot %d and by page %S_PGID, slot %d.

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 from Error: 8935 to Error: 8954

SQLServerF1

 

Error: 8935, Severity: 16, Table error: Object ID %d, index ID %d, partition ID %I64d, alloc unit ID %I64d (type %.*ls). The previous link %S_PGID on page %S_PGID does not match the previous page %S_PGID that the parent %S_PGID, slot %d expects for this page.
Error: 8936, Severity: 16, Table error: Object ID %d, index ID %d, partition ID %I64d, alloc unit ID %I64d (type %.*ls). B-tree chain linkage mismatch. %S_PGID->next = %S_PGID, but %S_PGID->Prev = %S_PGID.
Error: 8937, Severity: 16, Table error: Object ID %d, index ID %d, partition ID %I64d, alloc unit ID %I64d (type %.*ls). B-tree page %S_PGID has two parent nodes %S_PGID, slot %d and %S_PGID, slot %d.

Error: 8938, Severity: 16, Table error: Page %S_PGID, Object ID %d, index ID %d, partition ID %I64d, alloc unit ID %I64d (type %.*ls). Unexpected page type %d.
Error: 8939, Severity: 16, Table error: Object ID %d, index ID %d, partition ID %I64d, alloc unit ID %I64d (type %.*ls), page %S_PGID. Test (%.*ls) failed. Values are %ld and %ld.
Error: 8940, Severity: 16, Table error: Object ID %d, index ID %d, partition ID %I64d, alloc unit ID %I64d (type %.*ls), page %S_PGID. Test (%.*ls) failed. Address 0x%x is not aligned.
Error: 8941, Severity: 16, Table error: Object ID %d, index ID %d, partition ID %I64d, alloc unit ID %I64d (type %.*ls), page %S_PGID. Test (%.*ls) failed. Slot %d, offset 0x%x is invalid.
Error: 8942, Severity: 16, Table error: Object ID %d, index ID %d, partition ID %I64d, alloc unit ID %I64d (type %.*ls), page %S_PGID. Test (%.*ls) failed. Slot %d, offset 0x%x overlaps with the prior row.

Error: 8943, Severity: 16, Table error: Object ID %d, index ID %d, partition ID %I64d, alloc unit ID %I64d (type %.*ls), page %S_PGID. Test (%.*ls) failed. Slot %d, row extends into free space at 0x%x.
Error: 8944, Severity: 16, Table error: Object ID %d, index ID %d, partition ID %I64d, alloc unit ID %I64d (type %.*ls), page (%d:%d), row %d. Test (%.*ls) failed. Values are %ld and %ld.
Error: 8945, Severity: 16, Table error: Object ID %d, index ID %d will be rebuilt.
Error: 8946, Severity: 16, Table error: Allocation page %S_PGID has invalid %ls page header values. Type is %d. Check type, alloc unit ID and page ID on the page.
Error: 8947, Severity: 16, Table error: Multiple IAM pages for object ID %d, index ID %d, partition ID %I64d, alloc unit ID %I64d (type %.*ls) contain allocations for the same interval. IAM pages %S_PGID and %S_PGID.
Error: 8948, Severity: 16, Database error: Page %S_PGID is marked with the wrong type in PFS page %S_PGID. PFS status 0x%x expected 0x%x.
Error: 8949, Severity: 10, %.*ls fixed %d allocation errors and %d consistency errors in table ‘%ls’ (object ID %d).
Error: 8950, Severity: 16, %.*ls fixed %d allocation errors and %d consistency errors not associated with any single object.
Error: 8951, Severity: 16, Table error: table ‘%ls’ (ID %d). Data row does not have a matching index row in the index ‘%ls’ (ID %d). Possible missing or invalid keys for the index row matching:
Error: 8952, Severity: 16, Table error: table ‘%ls’ (ID %d). Index row in index ‘%ls’ (ID %d) does not match any data row. Possible extra or invalid keys for:
Error: 8953, Severity: 10, Repair: Deleted off-row data column with ID %I64d, for object ID %d, index ID %d, partition ID %I64d, alloc unit ID %I64d (type %.*ls) on page %S_PGID, slot %d.
Error: 8954, Severity: 10, %.*ls found %d allocation errors and %d consistency errors not associated with any single object.
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 from Error: 7948 to Error: 7969

SQLServerF1

 

Error: 7948, Severity: 10, – Avg. Pages per Extent……………………: %3.1f
Error: 7949, Severity: 10, – Scan Density [Best Count:Actual Count]…….: %4.2f%ls [%I64d:%I64d]
Error: 7950, Severity: 10, – Logical Scan Fragmentation ………………: %4.2f%ls
Error: 7951, Severity: 10, Warning: Could not complete filestream consistency checks due to an operating system error. Any consistency errors found in the filestream subsystem will be silenced. Please refer to other errors for more information. This condition is likely transien
Error: 7952, Severity: 10, – Extent Scan Fragmentation ……………….: %4.2f%ls

Error: 7953, Severity: 10, – Avg. Bytes Free per Page…………………: %3.1f
Error: 7954, Severity: 10, – Avg. Page Density (full)…………………: %4.2f%ls
Error: 7955, Severity: 16, Invalid SPID %d specified.
Error: 7956, Severity: 16, Table error: The FILESTREAM file “%.*ls” for column ID %d was found in column directory ID %.*ls of container ID %d but should be in container ID %d in object ID %d, index ID %d, partition ID %I64d, page ID %S_PGID, slot ID %d.
Error: 7957, Severity: 10, Cannot display the specified SPID’s buffer; in transition.
Error: 7958, Severity: 16, The specified SPID does not process input/output data streams.
Error: 7960, Severity: 16, An invalid server process identifier (SPID) %d or batch ID %d was specified.

Error: 7961, Severity: 16, Object ID %d, index ID %d, partition ID %I64d, alloc unit ID %I64d (type %.*ls) , page ID %S_PGID, row ID %d. Column ‘%.*ls’ is a var column with a NULL value and non-zero data length
Error: 7962, Severity: 16, Invalid BATCHID %d specified.
Error: 7963, Severity: 16, Database error: The file “%.*ls” is not a valid FILESTREAM LOG file in container ID %d.
Error: 7964, Severity: 10, Repair: Deleted FILESTREAM file “%.*ls” for column ID %d, for object ID %d, index ID %d, partition ID %I64d, alloc unit ID %I64d (type %.*ls) on page %S_PGID, slot %d.
Error: 7965, Severity: 16, Table error: Could not check object ID %d, index ID %d, partition ID %I64d, alloc unit ID %I64d (type %.*ls) due to invalid allocation (IAM) page(s).
Error: 7966, Severity: 10, Warning: NO_INDEX option of %ls being used. Checks on non-system indexes will be skipped.
Error: 7968, Severity: 10, Transaction information for database ‘%.*ls’.
Error: 7969, Severity: 16, No active open transactions.

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 from Error: 7907 to Error: 7926

SQLServerF1

 

Error: 7907, Severity: 16, Table error: The directory “%.*ls” under the rowset directory ID %.*ls is not a valid FILESTREAM directory in container ID %d.
Error: 7908, Severity: 16, Table error: The file “%.*ls” in the rowset directory ID %.*ls is not a valid FILESTREAM file in container ID %d.
Error: 7909, Severity: 20, The emergency-mode repair failed.You must restore from backup.
Error: 7910, Severity: 10, Repair: The page %S_PGID has been allocated to object ID %d, index ID %d, partition ID %I64d, alloc unit ID %I64d (type %.*ls).
Error: 7911, Severity: 10, Repair: The page %S_PGID has been deallocated from object ID %d, index ID %d, partition ID %I64d, alloc unit ID %I64d (type %.*ls).
Error: 7912, Severity: 10, Repair: The extent %S_PGID has been allocated to object ID %d, index ID %d, partition ID %I64d, alloc unit ID %I64d (type %.*ls).

Error: 7913, Severity: 10, Repair: The extent %S_PGID has been deallocated from object ID %d, index ID %d, partition ID %I64d, alloc unit ID %I64d (type %.*ls).
Error: 7914, Severity: 10, Repair: %ls page at %S_PGID has been rebuilt.
Error: 7915, Severity: 10, Repair: IAM chain for object ID %d, index ID %d, partition ID %I64d, alloc unit ID %I64d (type %.*ls), has been truncated before page %S_PGID and will be rebuilt.
Error: 7916, Severity: 10, Repair: Deleted record for object ID %d, index ID %d, partition ID %I64d, alloc unit ID %I64d (type %.*ls), on page %S_PGID, slot %d. Indexes will be rebuilt.
Error: 7917, Severity: 10, Repair: Converted forwarded record for object ID %d, index ID %d, partition ID %I64d, alloc unit ID %I64d (type %.*ls), at page %S_PGID, slot %d to a data row.

Error: 7918, Severity: 10, Repair: Page %S_PGID next and %S_PGID previous pointers have been set to match each other in object ID %d, index ID %d, partition ID %I64d, alloc unit ID %I64d (type %.*ls).
Error: 7919, Severity: 16, Repair statement not processed. Database needs to be in single user mode.
Error: 7920, Severity: 10, Processed %ld entries in system catalog for database ID %d.
Error: 7921, Severity: 16, Repair statement not processed. Database cannot be a snapshot.
Error: 7922, Severity: 16, ***************************************************************
Error: 7923, Severity: 10, Table %.*ls Object ID %ld.
Error: 7924, Severity: 10, Index ID %d, partition ID %I64d, alloc unit ID %I64d (type %.*ls). FirstIAM %S_PGID. Root %S_PGID. Dpages %I64d.
Error: 7925, Severity: 10, Index ID %d, partition ID %I64d, alloc unit ID %I64d (type %.*ls). %I64d pages used in %I64d dedicated extents.
Error: 7926, Severity: 16, Check statement aborted. The database could not be checked as a database snapshot could not be created and the database or table could not be locked. See Books Online for details of when this behavior is expected and what workarounds exist. Also see previ

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 from Error: 5275 to Error: 5309

SQLServerF1

 

Error: 5275, Severity: 10, Exhaustive search of ‘%.*ls’ (database ID %d) for inconsistencies completed. Processed %d of %d total searches. Elapsed time: %I64d milliseconds. This is an informational message only. No user action is required.
Error: 5276, Severity: 10, Exhaustive search of ‘%.*ls’ (database ID %d) for inconsistencies failed due to exception %d, state %d. This is an informational message only. No user action is required.
Error: 5277, Severity: 10, Internal %lsdatabase snapshot has split point LSN = %08x:%08x:%04x and first LSN = %08x:%08x:%04x.
Error: 5278, Severity: 10, DBCC encountered a page with an LSN greater than the current end of log LSN %S_LSN for its internal database snapshot. Could not read page %S_PGID, database ‘%.*ls’ (database ID %d), LSN = %S_LSN, type = %ld, isInSparseFile = %d. Please re-run this DBC

Error: 5280, Severity: 16, An unexpected protocol element was recevied during the execution of a consistency check command. Retry the operation.
Error: 5281, Severity: 10, Estimated TEMPDB space (in KB) needed for %s on database %.*ls = %I64d.
Error: 5282, Severity: 16, Table error: Object ID %d, index ID %d, partition ID %I64d, alloc unit ID %I64d (type %.*ls), page %S_PGID. The header of the page is invalid: the IS_IN_SYSXACT flag bit is set.
Error: 5283, Severity: 10, The Cross Rowset check on columnstore index object ID %d, index ID %d, partition ID %I64d. Drop and recreate the columnstore index.
Error: 5284, Severity: 16, The replicated index ‘%.*ls’ (object ID %d) and one or more of its clones do not contain the same rows.

Error: 5286, Severity: 10, %.*ls: Page %d:%d could not be moved because it belongs to an active online index build with LOBs.
Error: 5287, Severity: 10, DBCC THROWERROR bypass exception. This is an informational message only. No user action is required.
Error: 5301, Severity: 16, Bulk load failed. User does not have ALTR TABLE permission on table ‘%.*ls’. ALTR TABLE permission is required on the target table of a bulk load if the target table contains triggers or check constraints, but the ‘FIRE_TRIGGERS’ or ‘CHECK_CONSTRAINTS’
Error: 5302, Severity: 16, Mutator ‘%.*ls’ on ‘%.*ls’ cannot be called on a null value.
Error: 5303, Severity: 16, The result of applying mutator ‘%.*ls’ on CLR type ‘%.*ls’ cannot be a null value.
Error: 5304, Severity: 16, Bulk copy failed. User does not have ALTR TABLE permission on table ‘%.*ls’. ALTR TABLE permission is required on the target table of a bulk copy operation if the table has triggers or check constraints, but ‘FIRE_TRIGGERS’ or ‘CHECK_CONSTRAINTS’ bulk h
Error: 5305, Severity: 16, The rowdump and lockres columns are only valid on tables and indexed views on which the NOEXPAND hint is specified.
Error: 5306, Severity: 16, Cursor parameters are not allowed for functions. Variable ‘%.*ls’ is of type cursor.
Error: 5307, Severity: 16, Invalid parameter specified for sp_cursoropen.
Error: 5308, Severity: 16, Windowed functions and NEXT VALUE FOR functions do not support integer indices as ORDER BY clause expressions.
Error: 5309, Severity: 16, Windowed functions and NEXT VALUE FOR functions do not support constants as ORDER BY clause expressions.

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 from Error: 5255 to Error: 5274

SQLServerF1

 

Error: 5255, Severity: 10, %.*ls: Page %d:%d could not be moved because it is a sort page.
Error: 5256, Severity: 16, Table error: alloc unit ID %I64d, page %S_PGID contains an incorrect page ID in its page header. The PageId in the page header = %S_PGID.
Error: 5257, Severity: 10, %.*ls: File ID %d of database ID %d was skipped because the file size was changed in the middle of shrink operation.
Error: 5258, Severity: 10, %.*ls: Heap page %d:%d could not be moved because building computed column expression failed.
Error: 5259, Severity: 10, %.*ls: Heap page %d:%d could not be moved because populating computed column expression failed.

Error: 5260, Severity: 16, Object ID %d, index ID %d, partition ID %I64d, alloc unit ID %I64d (type %.*ls): At least one record on page %S_PGID contains versioning information, but the VERSION_INFO bit in the page header is not set.
Error: 5261, Severity: 10, %.*ls: Page %d:%d could not be moved because it has not been formatted.
Error: 5262, Severity: 16, Object ID %d, index ID %d, partition ID %I64d, alloc unit ID %I64d (type %.*ls), page %S_PGID, row %d: Row contains a NULL versioning timestamp, but its version chain pointer is not NULL. Version chain points to page %S_PGID, slot %d.
Error: 5263, Severity: 10, Found incorrect count(s) for table ‘%.*ls’, index ‘%.*ls’, partition %ld:
Error: 5264, Severity: 10, DATA pages %.*ls: From system table – %I64d pages; Actual – %I64d pages.

Error: 5265, Severity: 10, USED pages %.*ls: From system table – %I64d pages; Actual – %I64d pages.
Error: 5266, Severity: 10, RSVD pages %.*ls: From system table – %I64d pages; Actual – %I64d pages.
Error: 5267, Severity: 10, ROWS count: From system table – %I64d rows; Actual – %I64d rows.
Error: 5268, Severity: 10, DBCC %.*ls is performing an exhaustive search of %d indexes for possible inconsistencies. This is an informational message only. No user action is required.
Error: 5269, Severity: 16, Check terminated. The transient database snapshot for database ‘%.*ls’ (database ID %d) has been marked suspect due to an IO operation failure. Refer to the SQL Server error log for details.
Error: 5270, Severity: 10, %.*ls: Page %d:%d could not be moved because it is an unmovable page in a critical system table.
Error: 5271, Severity: 10, DBCC %ls could not output results for this command due to an internal failure. Review other errors for details.
Error: 5272, Severity: 10, %.*ls: Index Allocation Map (IAM) page %d:%d could not be moved because the underlying object could not be accessed exclusively.
Error: 5273, Severity: 10, %.*ls: Page %d:%d could not be moved because it belonged to an index/heap that was/is in build online.
Error: 5274, Severity: 16, Table error: Object ID %d, index ID %d, partition ID %I64d, alloc unit ID %I64d (type %.*ls), page %S_PGID. %S_MSG is invalid for compressed page; the following internal test failed: %.*ls. Values are %ld and %ld.

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 from Error: 5215 to Error: 5234

SQLServerF1

 

Error: 5215, Severity: 10, %.*ls: Page %d:%d could not be moved because the partition to which it belonged was dropped.
Error: 5216, Severity: 10, %.*ls: Heap page %d:%d could not be moved because the table to which it belonged was dropped.
Error: 5217, Severity: 10, %.*ls: Page %d:%d could not be moved because it is an empty non-leaf level index page.
Error: 5218, Severity: 10, %.*ls: Heap page %d:%d could not be moved because the table name could not be found.
Error: 5219, Severity: 10, %.*ls: Heap page %d:%d could not be moved.

Error: 5220, Severity: 10, %.*ls: Index Allocation Map (IAM) page %d:%d could not be moved.
Error: 5221, Severity: 10, %.*ls: Index Allocation Map (IAM) page %d:%d from a dropped allocation unit could not be moved.
Error: 5222, Severity: 10, %.*ls: Page %d:%d from a dropped allocation unit could not be deallocated.
Error: 5223, Severity: 10, %.*ls: Empty page %d:%d could not be deallocated.
Error: 5224, Severity: 10, %.*ls: Empty large object page %d:%d could not be deallocated.
Error: 5225, Severity: 10, %.*ls: Not all ghost records on the large object page %d:%d could be removed. If there are active queries on readable secondary replicas check the current ghost cleanup boundary.
Error: 5226, Severity: 10, %.*ls: Page %d:%d (type UNLINKED_REORG_PAGE) could not be deallocated.

Error: 5227, Severity: 10, %.*ls: Page %d:%d (type BULK_OPERATION_PAGE) could not be deallocated.
Error: 5228, Severity: 16, Table error: object ID %d, index ID %d, partition ID %I64d, alloc unit ID %I64d (type %.*ls), page %S_PGID, row %d. DBCC detected incomplete cleanup from an online index build operation. (The anti-matter column value is %d.)
Error: 5229, Severity: 16, Table error: Object ID %d, index ID %d, partition ID %I64d, alloc unit ID %I64d (type %.*ls) contains an anti-matter column, but is not a nonclustered index.
Error: 5230, Severity: 10, The check statement was aborted. DBCC CHECKCATALOG cannot be run on TEMPDB.
Error: 5231, Severity: 10, Object ID %ld (object ‘%.*ls’): A deadlock occurred while trying to lock this object for checking. This object has been skipped and will not be processed.
Error: 5232, Severity: 10, DBCC CHECKDB will not check SQL Server catalog or Service Broker consistency because a database snapshot could not be created or because WITH TABLOCK was specified.
Error: 5233, Severity: 16, Table error: alloc unit ID %I64d, page %S_PGID. The test (%.*ls) failed. The values are %ld and %ld.
Error: 5234, Severity: 10, DBCC SHRINKDATABASE: File ID %d of database ID %d was skipped because trying to adjust the space allocation for the file was failed.

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: 2567 to Error: 2590

SQLServerF1

 

Error: 2567, Severity: 14, DBCC INDEXDEFRAG cannot be used on system table indexes,
Error: 2568, Severity: 16, Page %S_PGID is out of range for this database or is in a log file.,
Error: 2570, Severity: 16, Page %S_PGID, slot %d in object ID %d, index ID %d, partition ID %I64d, alloc unit ID %I64d (type “%.*ls”). Column “%.*ls” value is out of range for data type “%.*ls”. Update column to a legal value.,
Error: 2571, Severity: 14, User ‘%.*ls’ does not have permission to run DBCC %.*ls.,

Error: 2572, Severity: 16, DBCC cannot free DLL ‘%.*ls’. The DLL is in use.,
Error: 2573, Severity: 16, Could not find table or object ID %.*ls. Check system catalog.,
Error: 2574, Severity: 16, Table error: Page %S_PGID is empty in object ID %d, index ID %d, partition ID %I64d, alloc unit ID %I64d (type %.*ls). This is not permitted at level %d of the B-tree.,
Error: 2575, Severity: 16, The Index Allocation Map (IAM) page %S_PGID is pointed to by the next pointer of IAM page %S_PGID in object ID %d, index ID %d, partition ID %I64d, alloc unit ID %I64d (type %.*ls), but it was not detected in the scan.,
Error: 2576, Severity: 16, The Index Allocation Map (IAM) page %S_PGID is pointed to by the previous pointer of IAM page %S_PGID in object ID %d, index ID %d, partition ID %I64d, alloc unit ID %I64d (type %.*ls), but it was not detected in the scan.,

Error: 2577, Severity: 16, Chain sequence numbers are out of order in the Index Allocation Map (IAM) chain for object ID %d, index ID %d, partition ID %I64d, alloc unit ID %I64d (type %.*ls). Page %S_PGID with sequence number %d points to page %S_PGID with sequence number %d.,
Error: 2579, Severity: 16, Table error: Extent %S_PGID in object ID %d, index ID %d, partition ID %I64d, alloc unit ID %I64d (type %.*ls) is beyond the range of this database.,
Error: 2580, Severity: 16, Table ‘%.*ls’ is either a system or temporary table. DBCC CLEANTABLE cannot be applied to a system or temporary table.,
Error: 2581, Severity: 10, DBCC cannot free the DLL “%.*ls”. The DLL is not loaded.,
Error: 2583, Severity: 16, An incorrect number of parameters was given to the DBCC statement.,
Error: 2585, Severity: 16, Cannot find partition number %ld for table “%.*ls”.,
Error: 2586, Severity: 16, Cannot find partition number %ld for index “%.*ls”, table “%.*ls”.,
Error: 2587, Severity: 16, The invalid partition number %ld was specified.,
Error: 2588, Severity: 16, Cannot find partition number %ld for index ID %d, object ID %d.,
Error: 2589, Severity: 16, Repair could not fix all errors on the first attempt.,
Error: 2590, Severity: 10, User “%.*ls” is modifying bytes %d to %d of page %S_PGID in database “%.*ls”.,

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.

 
1 2