SAP Knowledge Base Article - Preview

3276680 - HANA Error "maximum number of rows per table or partition reached" occurs even though the record count is not near the 2 billion threshold limit


  • The following ABAP dump appears as users try to perform DML modifications like INSERTs to a table :
Category               Installation error                                                           
Runtime Errors         DBSQL_SQL_ERROR                                                              
Except.                CX_SY_OPEN_SQL_DB                                                            
Date and Time          25.11.2022 12:43:36                                                          
Short Text                                                                                        
    SQL error "SQL code: 2055" occurred while accessing table "EDID4".                            
What happened?                                                                                    
    Database error text: "SQL message: maximum number of rows per table or                        
     partition reached: 'SAPABAP1:EDID4' 
  • EDID4 has only around ~1.8billion records under it's record count in SE16 / M_CS_TABLES. The number of records in a table (partition) can't exceed 2^31 (i.e. 2147483648, 2 billion). So why is the dump triggered even if the 2 billion limit is not even near reached yet ??





SAP HANA, platform edition 2.0

SAP HANA, platform edition 1.0


SAP HANA 1.0, platform edition ; SAP HANA, platform edition 2.0


KBA , HAN-DB , SAP HANA Database , 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.