Error 2575



Message text

Versions earlier than 15.0:

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.

Version 15.0 and later:

The last page of table '%.*s' is recorded in sysindexes as page number %d, partition ID %d. In its header, this page has page number %d as its 'next page'; however, the 'next page' value should be NULL. Check sysindexes.


The sysindexes table lists each table and index, and the segment where each table, clustered index, nonclustered index, and chain of text pages is stored. It also lists other information such as the first page and root for the object. For heap tables (those with no clustered index), the root entry points to the last page in the table's data page chain.

Adaptive Server expects to find a value of zero for the next page number on the last page for a table (meaning that there are no more pages in the page chain). Error 2575 is raised when dbcc checktable or dbcc checkdb is run, and the next page number in the table’s last page is not zero. This error is caused by an incorrect root page value for the table in sysindexes, or corruption in the table’s last page.


If this is the only error message you see when you run dbcc checktable or dbcc checkdb, it is likely that the table’s root entry in sysindexes is incorrect. Use one of these options to recover from the problem:

If you see other errors in addition to error 2575, the problem may be more extensive. Follow the instructions in this manual for handling those errors.

Additional information

Before calling Sybase Technical Support, have the information listed in “Reporting errors” available, including the output of dbcc checktable or dbcc checkdb.

Versions in which this error is raised

All versions