16
Table Corrupt: A page is linked in more than one chain; check this page:page number=%ld allocation status=%d
This error can be caused by a hardware problem.
This error occurs when Adaptive Server detects an inconsistency in the page chains associated with an object. For example, a page may be connected in more than one chain. If this error is detected by a dbcc command, error 605 can also occur.
WARNING! If error 605 occurs with this error, use the instructions under “Error 605” to remedy that error or call Sybase Technical Support.
This is a serious error that must be corrected immediately.
Note the page number that appears in the error message. Use the procedure “Finding an object name from a page number” in the chapter “Other Useful Tasks” in the most recent version of the Troubleshooting and Disaster Recovery guide to determine the table associated with the corrupt page chain.
WARNING! The procedure referenced in step 1 uses the dbcc page command. Use the dbcc page command only as directed. This command is undocumented, nonstandard, and is provided “as is” without any warranty. Sybase Technical Support does not support this command for general use. Although the command syntax is provided for reference, use this command only in the specific diagnostic situations described, and with the specific syntax shown. Failure to do so could cause performance problems and database corruption.
Depending on the type of object, select the most appropriate procedure:
If the object with the error is not a system table (a system table’s object ID is less than 100), go to step 3.
If the object with the error is a system table and the index ID is not 0 (zero), see “Fixing a system table corrupted index” in the chapter “Other Useful Tasks” in the most recent version of the guide Troubleshooting and Disaster Recovery for instructions on how to repair the system table index.
If the index ID is 0 (zero) , contact Sybase Technical Support. They may be able to help you repair the corruption, but it may be necessary to restore from clean backups.
If the object with the error is not a system table, use one of the following procedures below to correct the problem, depending on the kind of object is involved:
If the page belongs to an index, drop and re-create the index.
If the page does not belong to an index, recover your database from a known clean backup or recover the tables not affected by this error using the bcp utility. See “Rescuing data from a corrupted table” in the chapter “Other Useful Tasks” in the most recent version of the guide Troubleshooting and Disaster Recovery for instructions.
Examine your operating system error log and the Adaptive Server error log to determine if hardware errors caused the corruption.
Before calling Sybase Technical Support, have information available that is listed in “Reporting errors”, including the output of the dbcc page command.
All versions
