Server Error Messages 2500–2599


 Table named %.*s not found; check sysobjects
 Table Corrupt: A page is linked in more than one chain; check this page:page number=%ld  allocation status=%d
 Table Corrupt: Page linkage is not consistent; check the following pages: (current page#=%ld;  page# pointing to this page=%ld; previous page# indicated in this page=%ld)
 Table Corrupt: The index id in alloc page does not match the index id in sysindexes (alloc page#=%ld;  extent id=%ld; index id in alloc=%d; index id in sysindexes=%d)
Table Corrupt: Free offset in page header is not reasonable; free offset should be >= %d and <= %d; check this page and offset (page#=%ld freeoffset on the page header=%ld)
 Table Corrupt: The values in adjust table should be in ascending order starting from the end of the table (page#=%ld  row#=%d); check adjust table in this row
 Table Corrupt: Offset table is incorrect (page#=%ld  row#=%d offset in offset table is=%d  correct offset is=%d)
 Table Corrupt: Row length is incorrect (page#=%d row#=%d minimum row length=%d row length=%d)
Table Corrupt: The row number and offset of each row in the page should have a matching entry in row number table; check this page (page#=%d row#=%d offset in row number table=%d)
Key mismatch between index page %ld, at offset %d and data page %ld (row ID %d) in database ’%.*s’. Drop and re-create index id %d of table ’%.*s’.
Keys of index id %d for table ’%.*s’ in %S_MSG not in correct order. Drop and re-create the index. (index page %d)
 Table Corrupt: The specified row number %d in index page %ld cannot be found on data page %ld
 Table Corrupt: Object id %ld (object name = %S_OBJID) does not match between %.*s and %.*s
 Table Corrupt: Type id %ld (type name = %.*s) does not match between %.*s and %.*s
 Table Corrupt: Segment number %d does not match between %.*s and %.*s
 Table Corrupt: Procedure id %ld (procedure name = %S_OBJID) does not match between %.*s and %.*s
 Database Corrupt: Incorrect last checkpoint in syslogs
 Database Corrupt: The last checkpoint in sysdatabases is incorrect.  Syslogs recorded a different checkpoint
 Database named %.*s not found; check sysdatabases
 Table Corrupt: Page is linked but not allocated. Run DBCC TABLEALLOC to correct the problem. (alloc page#=%ld, extent id=%ld, logical page#=%ld, object id in extent=%ld, index id in extent=%ld, object name=%S_OBJID)
 Table Corrupt: The object id %ld (object name = %.*s) in page# %ld is different from the object id %ld (object name = %.*s) in sysindexes
 Table Corrupt: Page number %ld is out of range for this database %S_DBID. The maximum page number in this database is %ld
 Table Corrupt: Row length is inconsistent between the computed row length and the recorded row length on page; check the following page and row: pageno=%ld row#=%d computed row length=%d row length on page=%ld
 Table Corrupt: Object id wrong; tables: alloc page %ld  extent id=%ld  l page#=%ld objid in ext=%ld (name = %S_OBJID) objid in page=%ld (name = %S_OBJID) objid in sysindexes=%ld (name = %S_OBJID)
 Incorrect DBCC command: Please see the SQL Server Reference Manual for DBCC commands and options.
 DBCC detected internal database inconsistancy; contact a user with System Administrator (SA) role.
 DBCC execution completed. If DBCC printed error messages, contact a user with System Administrator (SA) role.
 Table Corrupt: Attempted to get page %ld, object %ld;  got page %ld, object %ld.
 Table Corrupt: Index id on extent should be 0; check the following page and ids: alloc page=%ld  extent=%ld index id on extent=%d
 Table Corrupt: No syslogs entry in sysindexes.
 Table Corrupt: Incorrect index key length %d in internal (sarg) structure.
 Table Corrupt: No keys found on index page %ld. Offset for the free space: (freeoff=%ld)
 Table Corrupt: Page# %ld belongs to object id %ld (object name = %.*s) not object id %ld (object name = %.*s)
 Checking %.*s: Logical pagesize is %ld bytes
 Checking %ld.
 Alloc page %ld (# of extent=%ld used pages=%ld ref pages=%ld)
 Total (# of extent=%ld used pages=%ld ref pages=%ld) in this database
 Table Corrupt: Page is allocated but not linked; check the following pages and ids: allocation pg#=%ld extent id=%ld logical pg#=%ld  object id on extent=%ld (object name = %S_OBJID) indid on extent=%ld
 Table Corrupt: object id does not match between extent in allocation page and sysindexes; check the following extent: alloc pg#=%ld extent#=%ld  object id on extent=%ld (object name = %.*s) object id in sysindexes=%ld (object name = %.*s)
 Table Corrupt: Extent is linked in more than one chain.  Check the following allocation page and extent: alloc pg#=%ld extent#=%ld status=%d
 Table Corrupt: Extent structures are linked incorrectly; check the following extent: alloc pg#=%ld extent#=%ld previous extent# on this extent=%ld previous extent should be=%ld
 Table Corrupt: Extent id %ld on allocation pg# %ld had object id %ld (object name = %.*s) on but used bit off
 Table Corrupt: Extent#=%ld on allocation pg#=%ld was used but object id was 0,
 Table Corrupt: Extent id %ld on allocation pg# %ld has objid %ld and used bit on, but reference bit off.
 Table Corrupt: Segment number %d specified for use in the segment map in sysusages has no entry in syssegments. The entry in sysusages is for dbid %d (db name = %S_DBID), with a virtual starting address of %ld.
 There is no default segment specified in syssegments.
 There is more than one default segment specified in syssegments.
 Missing segment in sysusages segmap.
 The following segments have been defined for database %d (database name %S_DBID).
 Page #%ld of sysindexes in database %d not found in cache after read.
 Only the owner of object `%.*s' or a user with System Administrator (SA) role can run DBCC %s on it.
 Extent not within segment: Object %ld, indid %d includes extents on allocation page %ld which is not in segment %d.
 Data page number %ld is empty but is not the first page. Status = 0x%x.
 Incorrect parameter passed to DBCC command.
 Unable to open log for database %d.
 %s cannot access object `%.*s' because it is not a table.
 Only the DBO of database %S_DBID or a user with System Administrator (SA) role can run the DBCC CHECKCATALOG command.
 Only the DBO of database %S_DBID or a user with System Administrator (SA) role can run the DBCC CHECKDB command.
 Only the DBO of database %S_DBID or a user with System Administrator (SA) role can run the DBCC CHECKALLOC/CHECKGAM command.
 Only the DBO of database %S_DBID or a user with System Administrator (SA) role can run the DBCC DBREPAIR command.
 Page %ld is out of range for this database
 Warning - Page %ld has DEALLOC bit on - indid %d, status 0x%x
 Permission denied.  Only a user with System Administrator (SA) role can use the DBCC command `%.*s'.
 Database `%S_DBID' is not in single user mode - may find spurious allocation problems due to transactions in progress.
 Database `%.*s' is not marked suspect. You cannot drop it with DBCC.
 Index page number %ld is empty.  Status = 0x%x.
 The last page %ld in sysindexes for table `%.*s' has next page # %ld in its page header. The next page # should be NULL. Please check sysindexes.
 The %S_MSG page %ld specified in sysindexes for table `%.*s' can not be found.  Please check sysindexes.
 The root page %ld in sysindexes for table `%.*s' has next page # %ld and previous page # %ld in its page header. Both the next page # and the previous page # should be NULL.  Please check sysindexes.
 The first page %d in sysindexes for table ’%.*s’ has previous page # %d in its page header. The previous page # should be NULL. Please check sysindexes.
 The total number of data pages in this table is %d.
 The clustered index page (%S_PAGE) has an unexpected key pointer to an overflow data page (%S_PAGE).  Please check page status.
 Data page (%S_PAGE) indicates that an overflow page is linked to it; however, the next page (%S_PAGE) has not been marked as an overflow page.  Please check page status.
 Data page (%S_PAGE) has been marked as an overflow page; however, the previous page (%S_PAGE) does not indicate that there is an overflow page linked to it.
 Number of data pages counted by DBCC differs from count in the data OAM.
 The last key in the previous page (%S_PAGE) is equal to the first key in the current page (%S_PAGE); however, the status of current page does not indicate that it is an overflow page.
 The last key in the previouse page (%S_PAGE) is equal to the first key in the current page (%S_PAGE); however, the status of previous page indicates that there is a disconnected overflow page.
 The last key in the previous page (%S_PAGE) is equal to the first key in the current page (%S_PAGE); however, the status of previous page indicates that there is no overflow page.
 The last key in the previouse page (%S_PAGE) is not equal to the first key in the current page (%S_PAGE); the current page is an overflow page; however, the status of previous page indicates that there is no disconnected overflow page.
 Object `%.*s' must have its status updated in sysobjects, to reflect the intent of repairing the index on it.
 DBCC option available for system tables only.
 Could not find index row which has id %d for table `%.*s'.
 %s index successfully restored for object `%.*s' in `%.*s' database.
 There are %d rows in %ld pages for object `%.*s'.
 Invalid index id specified (index id = %d).
 Database `%.*s' must be set to single user mode before executing this command.
 %S_PAGE has an incorrect pgfreeoff value of %d. The offset should be %d.
 The database is not open. Please issue a `use %.*s' and re-run the DBCC command.
 Indexes on sysobjects and sysindexes cannot be recreated.
 Invalid monitor group specified: `%.*s'. Please re-enter.

Number	Severity	Text and Explanation
2501	16	Table named %.s not found; check sysobjects Explanation:* Refer to the writeup for this error.
2502	16	Table Corrupt: A page is linked in more than one chain; check this page:page number=%ld allocation status=%d Explanation: Refer to the writeup for this error.
2503	16	Table Corrupt: Page linkage is not consistent; check the following pages: (current page#=%ld; page# pointing to this page=%ld; previous page# indicated in this page=%ld) Explanation: Refer to the writeup for this error.
2504	16	Table Corrupt: The index id in alloc page does not match the index id in sysindexes (alloc page#=%ld; extent id=%ld; index id in alloc=%d; index id in sysindexes=%d) Explanation: There may be possible corruption in a database or a database object. Take any corrective action indicated by the message. Consult the Adaptive Server System Administration Guide and the Troubleshooting Guide.
2505	16	Table Corrupt: Free offset in page header is not reasonable; free offset should be >= %d and <= %d; check this page and offset (page#=%ld freeoffset on the page header=%ld) Explanation: There may be possible corruption in a database or a database object. Take any corrective action indicated by the message. Consult the Adaptive Server System Administration Guide and the Troubleshooting Guide.
2506	16	Table Corrupt: The values in adjust table should be in ascending order starting from the end of the table (page#=%ld row#=%d); check adjust table in this row Explanation: Refer to the writeup for this error.
2507	16	Table Corrupt: Offset table is incorrect (page#=%ld row#=%d offset in offset table is=%d correct offset is=%d) Explanation: Refer to the writeup for this error.
2508	16	Table Corrupt: Row length is incorrect (page#=%d row#=%d minimum row length=%d row length=%d) Explanation: A dbcc check detected table corruption. Refer to Encyclopedia of Tasks in this document, and Checking Database Consistency in the System Administration Guide, for help in identifying the affected object and determining appropriate corrective action.
2509	16	Table Corrupt: The row number and offset of each row in the page should have a matching entry in row number table; check this page (page#=%d row#=%d offset in row number table=%d) Explanation: Refer to the writeup for this error.
2510	16	Key mismatch between index page %ld, at offset %d and data page %ld (row ID %d) in database ’%.s’. Drop and re-create index id %d of table ’%.s’. Explanation: Refer to the writeup for this error.
2511	16	Keys of index id %d for table ’%.s’ in %S_MSG not in correct order. Drop and re-create the index. (index page %d) Explanation:* Refer to the writeup for this error.
2512	16	Table Corrupt: The specified row number %d in index page %ld cannot be found on data page %ld Explanation: There may be possible corruption in a database or a database object. Take any corrective action indicated by the message. Consult the Adaptive Server System Administration Guide and the Troubleshooting Guide.
2513	16	Table Corrupt: Object id %ld (object name = %S_OBJID) does not match between %.s and %.s Explanation: Refer to the writeup for this error.
2514	16	Table Corrupt: Type id %ld (type name = %.s) does not match between %.s and %.s Explanation:* Refer to the writeup for this error.
2516	16	Table Corrupt: Segment number %d does not match between %.s and %.s Explanation: There may be possible corruption in a database or a database object. Take any corrective action indicated by the message. Consult the Adaptive Server System Administration Guide and the Troubleshooting Guide.
2517	16	Table Corrupt: Procedure id %ld (procedure name = %S_OBJID) does not match between %.s and %.s Explanation: Refer to the writeup for this error.
2518	16	Database Corrupt: Incorrect last checkpoint in syslogs Explanation: This message is generated when dbcc checkcatalog detects corruption in the syslogs table of a database. Collect dbcc output and report the error to Sybase Technical Support.
2519	16	Database Corrupt: The last checkpoint in sysdatabases is incorrect. Syslogs recorded a different checkpoint Explanation: Refer to the writeup for this error.
2520	16	Database named %.s not found; check sysdatabases Explanation:* Refer to the writeup for this error.
2521	16	Table Corrupt: Page is linked but not allocated. Run DBCC TABLEALLOC to correct the problem. (alloc page#=%ld, extent id=%ld, logical page#=%ld, object id in extent=%ld, index id in extent=%ld, object name=%S_OBJID) Explanation: Refer to the writeup for this error.
2522	16	Table Corrupt: The object id %ld (object name = %.s) in page# %ld is different from the object id %ld (object name = %.s) in sysindexes Explanation: Command failed due to invalid or illegal request. Check syntax, semantics, and permissions. Take any corrective action indicated by message.
2523	16	Table Corrupt: Page number %ld is out of range for this database %S_DBID. The maximum page number in this database is %ld Explanation: There may be possible corruption in a database or a database object. Collect dbcc output and report the error to Sybase Technical Support.
2524	16	Table Corrupt: Row length is inconsistent between the computed row length and the recorded row length on page; check the following page and row: pageno=%ld row#=%d computed row length=%d row length on page=%ld Explanation: Refer to the writeup for this error.
2525	16	Table Corrupt: Object id wrong; tables: alloc page %ld extent id=%ld l page#=%ld objid in ext=%ld (name = %S_OBJID) objid in page=%ld (name = %S_OBJID) objid in sysindexes=%ld (name = %S_OBJID) Explanation: Refer to the writeup for this error.
2526	16	Incorrect DBCC command: Please see the SQL Server Reference Manual for DBCC commands and options. Explanation: An attempt was made to execute an invalid dbcc command, or an incorrect number of parameters has been passed to a dbcc command.
2527	10	DBCC detected internal database inconsistancy; contact a user with System Administrator (SA) role. Explanation: This is an informational message. Unless otherwise specified, no action is required. Contact your System Administrator about any warning issued in the message.
2528	10	DBCC execution completed. If DBCC printed error messages, contact a user with System Administrator (SA) role. Explanation: This is an informational message. Unless otherwise specified, no action is required. Contact your System Administrator about any warning issued in the message.
2529	16	Table Corrupt: Attempted to get page %ld, object %ld; got page %ld, object %ld. Explanation: Refer to the writeup for this error.
2531	16	Table Corrupt: Index id on extent should be 0; check the following page and ids: alloc page=%ld extent=%ld index id on extent=%d Explanation: There may be possible corruption in a database or a database object. Takeany corrective action indicated by the message. Consult the Adaptive Server System Administration Guide and the Troubleshooting Guide.
2532	16	Table Corrupt: No syslogs entry in sysindexes. Explanation: There may be possible corruption in a database or a database object. Takeany corrective action indicated by the message. Consult the Adaptive Server System Administration Guide and the Troubleshooting Guide.
2533	16	Table Corrupt: Incorrect index key length %d in internal (sarg) structure. Explanation: There may be possible corruption in a database or a database object. Take any corrective action indicated by the message. Consult the Adaptive Server System Administration Guide and the Troubleshooting Guide.
2534	16	Table Corrupt: No keys found on index page %ld. Offset for the free space: (freeoff=%ld) Explanation: There may be possible corruption in a database or a database object. Take any corrective action indicated by the message. Consult the Adaptive Server System Administration Guide and the Troubleshooting Guide.
2535	16	Table Corrupt: Page# %ld belongs to object id %ld (object name = %.s) not object id %ld (object name = %.s) Explanation: There may be possible corruption in a database or a database object. Take any corrective action indicated by the message. Consult the Adaptive Server System Administration Guide and the Troubleshooting Guide.
2536	10	Checking %.s: Logical pagesize is %ld bytes Explanation:* This is an informational message. Unless otherwise specified, no action is required. Contact your System Administrator about any warning issued in the message.
2537	10	Checking %ld. Explanation: This is an informational message. No action is required.
2538	10	Alloc page %ld (# of extent=%ld used pages=%ld ref pages=%ld) Explanation: This is an informational message. Unless otherwise specified, no action is required. Contact your System Administrator about any warning issued in the message.
2539	10	Total (# of extent=%ld used pages=%ld ref pages=%ld) in this database Explanation: This is an informational message. Unless otherwise specified, no action is required. Contact your System Administrator about any warning issued in the message.
2540	16	Table Corrupt: Page is allocated but not linked; check the following pages and ids: allocation pg#=%ld extent id=%ld logical pg#=%ld object id on extent=%ld (object name = %S_OBJID) indid on extent=%ld Explanation: Refer to the writeup for this error.
2541	16	Table Corrupt: object id does not match between extent in allocation page and sysindexes; check the following extent: alloc pg#=%ld extent#=%ld object id on extent=%ld (object name = %.s) object id in sysindexes=%ld (object name = %.s) Explanation: Refer to the writeup for this error.
2542	16	Table Corrupt: Extent is linked in more than one chain. Check the following allocation page and extent: alloc pg#=%ld extent#=%ld status=%d Explanation: There may be possible corruption in a database or a database object. Take any corrective action indicated by the message. Consult the Adaptive Server System Administration Guide and the Troubleshooting Guide.
2543	16	Table Corrupt: Extent structures are linked incorrectly; check the following extent: alloc pg#=%ld extent#=%ld previous extent# on this extent=%ld previous extent should be=%ld Explanation: Refer to the writeup for this error.
2544	16	Table Corrupt: Extent id %ld on allocation pg# %ld had object id %ld (object name = %.s) on but used bit off Explanation:* Refer to the writeup for this error.
2545	16	Table Corrupt: Extent#=%ld on allocation pg#=%ld was used but object id was 0, Explanation: There may be possible corruption in a database or a database object. Takeany corrective action indicated by the message. Consult the Adaptive Server System Administration Guide and the Troubleshooting Guide.
2546	16	Table Corrupt: Extent id %ld on allocation pg# %ld has objid %ld and used bit on, but reference bit off. Explanation: Refer to the writeup for this error.
2547	16	Table Corrupt: Segment number %d specified for use in the segment map in sysusages has no entry in syssegments. The entry in sysusages is for dbid %d (db name = %S_DBID), with a virtual starting address of %ld. Explanation: Run dbcc checkcatalog, collect dbcc output and report the error to Sybase Technical Support.
2548	16	There is no default segment specified in syssegments. Explanation: Information in syssgements may be corrupt. Run dbcc checkcatalog, collect dbcc output and report the error to Sybase Technical Support.
2549	16	There is more than one default segment specified in syssegments. Explanation: Information in syssgements may be corrupt. Run dbcc checkcatalog, collect dbcc output and report the error to Sybase Technical Support.
2550	16	Missing segment in sysusages segmap. Explanation: Refer to the writeup for this error.
2551	10	The following segments have been defined for database %d (database name %S_DBID). Explanation: This is an informational message. Unless otherwise specified, no action is required. Contact your System Administrator about any warning issued in the message.
2556	20	Page #%ld of sysindexes in database %d not found in cache after read. Explanation: Adaptive Server encountered an internal error affecting the current process. Reconnect to Adaptive Server. Report the error to your System Administrator so dbcc diagnostics can be run.
2557	14	Only the owner of object `%.s' or a user with System Administrator (SA) role can run DBCC %s on it. Explanation:* You do not have the permission to execute this command. Have the object owner or a user with the needed role run this command.
2558	16	Extent not within segment: Object %ld, indid %d includes extents on allocation page %ld which is not in segment %d. Explanation: Refer to the writeup for this error.
2559	16	Data page number %ld is empty but is not the first page. Status = 0x%x. Explanation: Refer to the writeup for this error.
2560	16	Incorrect parameter passed to DBCC command. Explanation: Command failed due to invalid or illegal request. Check syntax, semantics, and permissions. Take any corrective action indicated by message.
2561	16	Unable to open log for database %d. Explanation: Adaptive Server could not perform the requested action. Contact your System Administrator.
2562	16	%s cannot access object `%.s' because it is not a table. Explanation:* Command failed due to invalid or illegal request. Check syntax, semantics, and permissions. Take any corrective action indicated by message.
2563	14	Only the DBO of database %S_DBID or a user with System Administrator (SA) role can run the DBCC CHECKCATALOG command. Explanation: You do not have the permission to execute this command. Have the object owner or a user with the needed role run this command.
2564	14	Only the DBO of database %S_DBID or a user with System Administrator (SA) role can run the DBCC CHECKDB command. Explanation: You do not have the permission to execute this command. Have the object owner or a user with the needed role run this command.
2565	14	Only the DBO of database %S_DBID or a user with System Administrator (SA) role can run the DBCC CHECKALLOC/CHECKGAM command. Explanation: You do not have the permission to execute this command. Have the database owner or a user with SA role run this command.
2567	14	Only the DBO of database %S_DBID or a user with System Administrator (SA) role can run the DBCC DBREPAIR command. Explanation: You do not have the permission to execute this command. Have the object owner or a user with the needed role run this command.
2568	16	Page %ld is out of range for this database Explanation: There may be possible corruption in a database or a database object. Takeany corrective action indicated by the message. Consult the Adaptive Server System Administration Guide and the Troubleshooting Guide.
2570	10	Warning - Page %ld has DEALLOC bit on - indid %d, status 0x%x Explanation: This is an informational message. Unless otherwise specified, no action is required. Contact your System Administrator about any warning issued in the message.
2571	14	Permission denied. Only a user with System Administrator (SA) role can use the DBCC command `%.s'. Explanation:* Refer to the writeup for this error.
2572	10	Database `%S_DBID' is not in single user mode - may find spurious allocation problems due to transactions in progress. Explanation: Refer to the writeup for this error.
2573	16	Database `%.s' is not marked suspect. You cannot drop it with DBCC. Explanation:* Refer to the writeup for this error.
2574	16	Index page number %ld is empty. Status = 0x%x. Explanation: There may be possible corruption in a database or a database object. Take any corrective action indicated by the message. Consult the Adaptive Server System Administration Guide and the Troubleshooting Guide.
2575	16	The last page %ld in sysindexes for table `%.s' has next page # %ld in its page header. The next page # should be NULL. Please check sysindexes. Explanation:* There may be possible corruption in a database or a database object. Takeany corrective action indicated by the message. Consult the Adaptive Server System Administration Guide and the Troubleshooting Guide.
2576	16	The %S_MSG page %ld specified in sysindexes for table `%.s' can not be found. Please check sysindexes. Explanation:* There may be possible corruption in a database or a database object. Takeany corrective action indicated by the message. Consult the Adaptive Server System Administration Guide and the Troubleshooting Guide.
2577	16	The root page %ld in sysindexes for table `%.s' has next page # %ld and previous page # %ld in its page header. Both the next page # and the previous page # should be NULL. Please check sysindexes. Explanation:* There may be possible corruption in a database or a database object. Takeany corrective action indicated by the message. Consult the Adaptive Server System Administration Guide and the Troubleshooting Guide.
2578	16	The first page %d in sysindexes for table ’%.s’ has previous page # %d in its page header. The previous page # should be NULL. Please check sysindexes. Explanation:* There may be possible corruption in a database or a database object. Take any corrective action indicated by the message. Consult the Adaptive Server System Administration Guide and the Troubleshooting Guide.
2579	10	The total number of data pages in this table is %d. Explanation: This is an informational message. Unless otherwise specified, no action is required. Contact your System Administrator about any warning issued in the message.
2580	16	The clustered index page (%S_PAGE) has an unexpected key pointer to an overflow data page (%S_PAGE). Please check page status. Explanation: There may be possible corruption in a database or a database object. Take any corrective action indicated by the message. Consult the Adaptive Server System Administration Guide and the Troubleshooting Guide.
2581	16	Data page (%S_PAGE) indicates that an overflow page is linked to it; however, the next page (%S_PAGE) has not been marked as an overflow page. Please check page status. Explanation: There may be possible corruption in a database or a database object. Take any corrective action indicated by the message. Consult the Adaptive Server System Administration Guide and the Troubleshooting Guide.
2582	16	Data page (%S_PAGE) has been marked as an overflow page; however, the previous page (%S_PAGE) does not indicate that there is an overflow page linked to it. Explanation: See the writeup for Error 2582.
2583	10	Number of data pages counted by DBCC differs from count in the data OAM. Explanation: This is an informational message. Unless otherwise specified, no action is required. Contact your System Administrator about any warning issued in the message.
2584	16	The last key in the previous page (%S_PAGE) is equal to the first key in the current page (%S_PAGE); however, the status of current page does not indicate that it is an overflow page. Explanation: There may be possible corruption in a database or a database object. Take any corrective action indicated by the message. Consult the Adaptive Server System Administration Guide and the Troubleshooting Guide.
2585	16	The last key in the previouse page (%S_PAGE) is equal to the first key in the current page (%S_PAGE); however, the status of previous page indicates that there is a disconnected overflow page. Explanation: There may be possible corruption in a database or a database object. Take any corrective action indicated by the message. Consult the Adaptive Server System Administration Guide and the Troubleshooting Guide.
2586	16	The last key in the previous page (%S_PAGE) is equal to the first key in the current page (%S_PAGE); however, the status of previous page indicates that there is no overflow page. Explanation: There may be possible corruption in a database or a database object. Take any corrective action indicated by the message. Consult the Adaptive Server System Administration Guide and the Troubleshooting Guide.
2587	16	The last key in the previouse page (%S_PAGE) is not equal to the first key in the current page (%S_PAGE); the current page is an overflow page; however, the status of previous page indicates that there is no disconnected overflow page. Explanation: There may be possible corruption in a database or a database object. Take any corrective action indicated by the message. Consult the Adaptive Server System Administration Guide and the Troubleshooting Guide.
2589	16	Object `%.s' must have its status updated in sysobjects, to reflect the intent of repairing the index on it. Explanation:* Adaptive Server could not perform the requested action. Contact your System Administrator.
2590	16	DBCC option available for system tables only. Explanation: Command failed due to invalid or illegal request. Check syntax, semantics, and permissions. Take any corrective action indicated by message.
2591	16	Could not find index row which has id %d for table `%.s'. Explanation:* Command failed due to invalid or illegal request. Check syntax, semantics, and permissions. Take any corrective action indicated by message.
2592	10	%s index successfully restored for object `%.s' in `%.s' database. Explanation: This is an informational message. Unless otherwise specified, no action is required. Contact your System Administrator about any warning issued in the message.
2593	10	There are %d rows in %ld pages for object `%.s'. Explanation:* This is an informational message. Unless otherwise specified, no action is required. Contact your System Administrator about any warning issued in the message.
2594	16	Invalid index id specified (index id = %d). Explanation: Command failed due to invalid or illegal request. Check syntax, semantics, and permissions. Take any corrective action indicated by message.
2595	16	Database `%.s' must be set to single user mode before executing this command. Explanation:* Command failed due to invalid or illegal request. Check syntax, semantics, and permissions. Take any corrective action indicated by message.
2596	16	%S_PAGE has an incorrect pgfreeoff value of %d. The offset should be %d. Explanation: Refer to the writeup for this error.
2597	16	The database is not open. Please issue a `use %.s' and re-run the DBCC command. Explanation:* Command failed due to invalid or illegal request. Check syntax, semantics, and permissions. Take any corrective action indicated by message.
2598	16	Indexes on sysobjects and sysindexes cannot be recreated. Explanation: You cannot recreate the indexes on these system tables.
2599	16	Invalid monitor group specified: `%.s'. Please re-enter. Explanation:* Command failed due to invalid or illegal request. Check syntax, semantics, and permissions. Take any corrective action indicated by message.