SAP Knowledge Base Article - Preview

3293801 - Invalid data row pointer error raised when accessing table with compressed rows - SAP ASE


  • ASE encounters error message which may be followed by a stacktrace
  • Several error patterns are reported for this issue
  1. Invalid DOL data row pointer: row xx with status 0xXXXXX must be normal row instead of compressed row

    with a stack trace including functions


  2. Error: 614, Severity: 21, State: 12
    Adaptive Server accessed a row that has an illegal length of -6547 while in database 'dbname'.
    Page pointer = 0x0x7f6c45720000, pageno = 7274, status = 0x801, ptnid = 2071011428, indexid = 0, level = 0, pnextrno = 48. The minimum row length is 14. The page size is 16384.

    with a stack trace including functions

    LeDataRow::_updateVarLenValue(LeColumn*, sdes*, int)
    LeDataRow::writeRowDOL_upd(unsigned char*, int, sdes*, sdes*)

  3. dbcc checktable reports following errors

    Table Corrupt: Row length is inconsistent between the computed row length (29) and the row length (13957) recorded on the page.
    Check row number 0 and page number 10137, partition ID 451529661.

    Msg 15041, Level 16, State 1:
    Table Corrupt: Row 0 in page 10137 is in the wrong partition (ID 451529661). The row should reside in the partition corresponding to ID 735338653.

    Msg 9991, Level 16, State 1:
    Page 10137, partition ID 451529661, of object 716526555, contains an orphan row at offset 14001 which must be marked committed delete and is not.

    Invalid column length 0 found for compressed column, column ID 0, row ID 74, page number 10138, partition ID 451529661. Fixed-length column cannot have a NULL value.



    Adaptive Server Enterprise (ASE) 16.0 SP03 & SP04


    SAP Adaptive Server Enterprise 16.0


    290026, Invalid DOL data row pointer, compression, collocate, 827810, CR827810, 827650, CR827650, Error 614 , KBA , BC-SYB-ASE , Sybase ASE Database Platform (non Business Suite) , BC-DB-SYB , Business Suite on Adaptive Server Enterprise , Problem

    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.