20
Keys did not match overflow page when inserting row at end of page (%S_PAGE) that has overflow page (%S_PAGE) that is not disconnected in dbid = %d.
With a clustered index, Adaptive Server maintains data so that the physical order of rows is the same as their logical, indexed order. The bottom or leaf level of a clustered index contains the table’s actual data pages. When an index key has a large number of duplicates, not all of these may fit on the same data page. Adaptive Server then allocates a new data page, marking it an “overflow page” to store the additional values. The original page and the overflow page now both contain at least one row with that key value.
If the data corresponding to the key value on the first page is now updated or deleted so that the key no longer appears on that page, Adaptive Server removes the association between the two pages. The overflow page is now a regular page just like any other data page.
Error 2619 is raised when Adaptive Server attempts to insert a key value at the end of a page, and the key currently in place has an associated overflow page, but the key does not match the key value in the overflow page. It is likely that the page served as an overflow page at some point, but when a row with that key value on the first page was updated or deleted, the overflow page was not marked as a regular (disconnected) page.
When error 2619 occurs, the connection to Adaptive Server is broken. This is a serious error that indicates a corrupt clustered index on the table.
Use the following steps to resolve the error:
Perform the procedure in “Finding an object name from a page number” in the most recent Troubleshooting and Disaster Recovery guide to identify the table.
Use sp_helpindex to list all indexes associated with the table and identify the clustered index on the table.
Drop and re-create the clustered index.
Run dbcc tablealloc on the table to ensure that the problem is resolved. If errors are raised, contact Sybase Technical Support for assistance.
When calling Sybase Technical Support, have the information available that is listed in “Reporting errors”.
All versions
