Our SAP ECC system is down and we are unable to update as records and in SM13 update got deactivated.
As per our observation, BALDAT table crossed 2billions of record and update got deactivated.
Upon clean with 1.2 billion records, system still in deactivate status.(after activation it is going into deactivation again)
Earlier record count : 2,147,451,854
current record count : 1.210.096.070
To expedite the issue resolving, we have checked the traces on your P01 system.
in SM14, we could see the update is deactived:
Status Update deactivated by system
Server gvecsl9113sps_P01_01
Based on the system log, we could see the update was deactivated and active repeatedly due to DB error 2055:
05.09.2021 02:02:25 gvecsl9c00sps_P01_01 UP1 240 100 BTC_EHS @5CQvery high priority@ BYL Database error 2055 requires database administrator to intervene
05.09.2021 02:02:25 gvecsl9c00sps_P01_01 UP1 240 100 BTC_EHS @5CQvery high priority@ R0R The update was deactivated following a system error
05.09.2021 02:02:25 gvecsl9c00sps_P01_01 UP1 240 100 BTC_EHS @5CQvery high priority@ R1O Update request restarted after internal error
05.09.2021 02:03:45 gvecsl9c00sps_P01_01 UP1 240 100 BTC_EHS @5CQvery high priority@ R1O Update request restarted after internal error
05.09.2021 02:03:45 gvecsl9c00sps_P01_01 UP1 240 100 BTC_EHS @5CQvery high priority@ R0R The update was deactivated following a system error
05.09.2021 02:03:45 gvecsl9c00sps_P01_01 UP1 240 100 BTC_EHS @5CQvery high priority@ BYL Database error 2055 requires database administrator to intervene
------------------------------------
I think the issue matches KBA 2212518 - HANA error maximum number of rows per partition reached, because, the following SQL shows "RAW_RECORD_COUNT_IN_MAIN + RAW_RECORD_COUNT_IN_DELTA as TOTAL_RECORD" reached 2 billion limit.
----------------------------------------------
select HOST, PORT, SCHEMA_NAME, TABLE_NAME, PART_ID, RAW_RECORD_COUNT_IN_MAIN, RAW_RECORD_COUNT_IN_DELTA, RAW_RECORD_COUNT_IN_MAIN + RAW_RECORD_COUNT_IN_DELTA as TOTAL_RECORD
from M_CS_TABLES
where SCHEMA_NAME = 'SAPABAP1' and TABLE_NAME like 'BALDAT';
----------------------------------------------
>>>gvecsl5103sps 30140 SAPABAP1 BALDAT 0 2,128,158,698 19,324,947 2,147,483,645
So, could you please follow instructions below to perform delta merge and force the compress of a table manually.
----------------------------
The 2 billion record limit include also MVCC versions and Fulltext Index Structures. Ensure you have performed an optimized compression and a delta merge of this table before attempting to add more data.
-To Compress a Column Table Manually, run the statement:
UPDATE "" WITH PARAMETERS ('OPTIMIZE_COMPRESSION'='FORCE')
-To perform a manual delta merge, check the Perform a Manual Delta Merge Operation.
