16
Versions earlier than 15.0:
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
Version 15.0 and later:
Table Corrupt: Row length is inconsistent between the computed row length (%d) and the row length (%d) recorded on the page. Check row number %d and page number %d, partition ID %d.
This error may be caused by a hardware problem.
Adaptive Server computes the length of each row by using the values stored in the offset and adjust tables of each row. Errors 2524 occurs when dbcc checkdb or dbcc checktable detects that the actual length of a row does not match the computed length of that row.
This error can occur on a data page as well as on an index page.
If you have clean backups of your database, recover from backups. If not, refer to “Identifying and fixing a corrupted table” in the chapter “Other Useful Tasks” in the most recent version of Troubleshooting and Disaster Recovery to correct the error.
WARNING! Some data on this page might be lost if you recover your table using bcp or select into (that is, the corrupted row and rows following it might be truncated and contain the wrong keys). Compare the two tables (old and new) row by row (by joining them on a primary key, for example) to determine which rows are different (corrupted).
Before dumping your database, make sure it is working correctly by running the following commands prior to each dump:
dbcc checkdb.
dbcc checkalloc or dbcc checkalloc with the fix option. (Refer to “Fixing and preventing allocation errors” in the chapter “Other Useful Tasks” in the most recent version of Troubleshooting and Disaster Recovery for information about running these commands in multiuser mode and how to prevent spurious allocation errors from dbcc commands.)
Error 2524 is probably caused by a problem within Adaptive Server but may also be caused by hardware errors on your database devices. To help rule out this possibility, do the following:
Check the Adaptive Server error log to determine whether there are other indications of hardware problems, such as kernel messages reporting I/O errors.
Check the operating system error log or diagnostics utilities for I/O errors. Refer to “Checking the operating system error log” in the chapter “Other Useful Tasks” in the most recent version of Troubleshooting and Disaster Recovery.
If problems persist, refer to the error documentation in this manual or contact Sybase Technical Support.
Refer to bcp in the Adaptive Server Utility Guide.
Refer to “select” in the Reference Manual: Commands for information about the select into command.
Have the information listed in “Reporting errors” available before you call Sybase Technical Support, including the output of dbcc checkdb and dbcc checkalloc.
All versions
