Home

	Expand Search

Troubleshooting and Error Messages Guide

Chapter 3 Error Message Writeups

Insert Errors

Error 2628

Error 2628

Severity

21

Error message text

In database '%.*s', page %ld is linked forward to page %ld, but that page is linked backward to page %ld. Please report this internal error to Sybase Technical Support.

This error may be caused by a hardware problem.

Explanation

When updating a table or index, Adaptive Server may determine that there is not enough room on a page to insert additional data. A new page is then allocated for the object. Existing rows may be moved to this page and new rows inserted. Error 2628 is raised when Adaptive Server fetches a page by following the forward pointers, examines the existing page linkage, and finds that the backward pointer does not point to the previous page as expected. Since the linkage problem could be worsened by continuing the page split, the operation is aborted.

When dbcc detects this problem, it raises Error 2503 (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)).

Action

Error 2628 is due to corruption of page pointers for the object. Use the following steps to resolve the error:

1. Identify the object using one of the pages identified in the message. Refer to "How to Find an Object Name from a Page Number" in the Encyclopedia of Tasks chapter for information.

2. If the page is a data page (index ID = 0), drop and recreate the clustered index on the table.

3. If this is an index page (index ID is greater than 0), drop and recreate the index.

4. Run dbcc pglinkage on the table to verify that the problem is corrected. Be sure to check both next page and previous page pointers.

Versions in which this error is raised

All versions