SAP Knowledge Base Article - Preview

2443399 - How to run dbcc tablealloc on a table to fix corruptions - SAP ASE


  • When running applications on SAP ASE database, database corruptions may occur due to various problems. 
  • Typically raised errors are:
    • 605 - An attempt was made to fetch logical page '%ld' from cache '%.*s'. Page belongs to %S_PTNINFO and not to %S_PTNINFO.
    • 691 - Encountered invalid logical page '%ld' while accessing object '%ld' in database '%d'. This is an internal system error. Please contact SAP Product Support.
    • 1142 - Invalid OAM Page %ld. Found pstat=0x%x, object=%ld, database=%d, indid=%d.
    • 2510 - Key mismatch between index page %d, partition ID %d; at offset %d; and data page %d (row ID %d), partition ID %d. Drop and re-create index ID %d of table '%.*s' in database '%.*s'.
    • 2558 - Extent not within segment: Object %ld, indid %d, partition %ld includes extents on allocation page %ld which is not in segment %d
    • 2620 - The offset of the row number at offset 1228 does not match the entry in the offset table of the following page: ...
    • 2630 - In database '%.*s', page %u is linked backward to page %u, but that page is linked forward to page %u. Please report this internal error to SAP Technical Support.
  • Other errors my also be raised in the ASE log.



  • SAP Adaptive Server Enterprise (ASE) 15.7
  • SAP Adaptive Server Enterprise (ASE) 16.0
  • SAP Adaptive Server Enterprise (ASE) 15.7 for Business Suite
  • SAP Adaptive Server Enterprise (ASE) 16.0 for Business Suite


SAP Adaptive Server Enterprise 15.7 ; SAP Adaptive Server Enterprise 16.0


KBA , BC-SYB-ASE , Sybase ASE Database Platform (non Business Suite) , BC-DB-SYB , Business Suite on Adaptive Server Enterprise , How To

About this page

This is a preview of a SAP Knowledge Base Article. Click more to access the full version on SAP for Me (Login required).

Search for additional results

Visit SAP Support Portal's SAP Notes and KBA Search.