03:00000:00044:2009/06/15 09:37:23.73 server Error: 2628, Severity: 21, State: 2
03:00000:00044:2009/06/15 09:37:23.73 server In database 'WDZX', page 15953689 is linked forward to page 15969149, but that page is linked backward to page 15969147. Please report this internal error to Sybase Technical Support.
03:00000:00044:2009/06/15 09:37:23.73 kernel ************************************
03:00000:00044:2009/06/15 09:37:23.73 kernel SQL causing error : update statistics WDZX.G_UFILES using 100 values
[ 本帖最后由 donniejeck 于 2009-6-15 16:38 编辑 ]作者: donniejeck 时间: 2009-06-15 10:24 标题: 重建索引脚本日志输出部分内容 Server 'cq', Line 1:
In database 'WDZX', page 15953689 is linked forward to page 15969149, but that
page is linked backward to page 15969147. Please report this internal error to
Sybase Technical Support.
The SQL Server is terminating this process.
CT-LIBRARY error:
ct_send(): network packet layer: internal Client Library error: State error: trying to write when connection is expecting a read.
CT-LIBRARY error:
ct_cancel(): network packet layer: internal net library error: Net-Library operation terminated due to disconnect作者: donniejeck 时间: 2009-06-15 10:29 标题: 摘自SYBASE官方解释 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:
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.
If the page is a data page (index ID = 0), drop and recreate th作者: donniejeck 时间: 2009-06-15 10:30 标题: 摘自SYBASE官方解释 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:
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.
If the page is a data page (index ID = 0), drop and recreate the clustered index on the table.
If this is an index page (index ID is greater than 0), drop and recreate the index.
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作者: donniejeck 时间: 2009-06-15 10:31
硬件故障?难道是作者: chuxu 时间: 2009-06-15 14:13
删了索引，再重新建立不行吗？作者: donniejeck 时间: 2009-06-15 14:20
03:00000:00044:2009/06/15 09:37:23.73 server In database 'WDZX', page 15953689 is linked forward to page 15969149, but that page is linked backward to page 15969147. Please report this internal error to Sybase Technical Support.
数据页链错误如何修复呢?作者: chuxu 时间: 2009-06-15 15:02
dbcc checktable作者: donniejeck 时间: 2009-06-15 15:35
1> dbcc tablealloc(1628532835)
2> go
The default report option of OPTIMIZED is used for this run.
The default fix option of FIX is used for this run.
***************************************************************
TABLE: LONGTEXT OBJID = 1628532835
INDID=0 FIRST=4561 ROOT=4561 SORT=0
The oam counts for objid 1628532835 indid 0 are corrected.
Data level: 0. 43069 Data pages allocated and 5716 Extents allocated.
INDID=2 FIRST=3853705 ROOT=3853704 SORT=1
Msg 2503, Level 16, State 2:
Server 'cq', Line 1:
Table Corrupt: Page linkage is not consistent; check the following pages: (current page#=11928067; page# pointing to th
is page=11928066; previous page# indicated in this page=1192806
INDID=3 FIRST=9995961 ROOT=9995960 SORT=1
Indid : 3. 10193 Index pages allocated and 1276 Extents allocated.
TOTAL # of extents = 6992
1> dbcc tablealloc(876530156)
2> go
The default report option of OPTIMIZED is used for this run.
The default fix option of FIX is used for this run.
***************************************************************
TABLE: G_UFILES OBJID = 876530156
INDID=0 FIRST=3673 ROOT=3673 SORT=0
The oam counts for objid 876530156 indid 0 are corrected.
Data level: 0. 25215 Data pages allocated and 3222 Extents allocated.
INDID=2 FIRST=1886417 ROOT=1886416 SORT=1
Msg 2503, Level 16, State 2:
Server 'cq', Line 1:
Table Corrupt: Page linkage is not consistent; check the following pages: (current page#=15969149; page# pointing to th
is page=15953689; previous page# indicated in this page=15969147)
INDID=3 FIRST=9970361 ROOT=9970360 SORT=1
Indid : 3. 8267 Index pages allocated and 1035 Extents allocated.
INDID=4 FIRST=9987121 ROOT=9987120 SORT=1
Indid : 4. 6286 Index pages allocated and 806 Extents allocated.
TOTAL # of extents = 5063
1>作者: donniejeck 时间: 2009-06-15 16:01
重建OBJID(1628532835,876530156)索引后,tablealloc正常.作者: WFCJZ 时间: 2009-06-15 18:50
kernel end of stack trace, spid 44, kpid 6029404, suid 1
早应该从这上面入手的,呵呵!
