3527838 - POSTING_ILLEGAL_STATEMENT Dumps on an ABAP Client - HANA Database

• The following dump occurs in ST22 Tcode for an ABAP program or function module, indicating a failure on the HANA Database layer : 
  
  

  Category               ABAP programming error
  Runtime Errors         POSTING_ILLEGAL_STATEMENT
  ABAP Program           ------
  Application Component  XX-XX-XX-XX
  Date and Time          09/18/2024 08:11:24
  ----------------------------------------------------------------------------------------------------
  ----------------------------------------------------------------------------------------------------
  |Short Text                                                                                        |
  |    Statement "DB Operation with implicit Rollback" is not allowed in this form.                  |
  ----------------------------------------------------------------------------------------------------
  ----------------------------------------------------------------------------------------------------
  |What happened?                                                                                    |
  |    Error in the ABAP application program.                                                        |
  |                                                                                                  |
  |    The current ABAP program "<>" had to be terminated because it found a                   |
  |    statement that could not be executed.                                                         
  
  
  
  ----------------------------------------------------------------------------------------------------
  |Database Interface Information                                                                    |
  ----------------------------------------------------------------------------------------------------
  
  .......
  
  |C|E|EXECUTE C_0128 on connection 0, rc=129 [/bas/754_REL/src/dbs/hdb/dbslsdb.cpp#8614]            |
  |C|1|SQLCODE    : 129 [/bas/754_REL/src/dbs/hdb/dbsdbtrc.cpp#610]                                  |
  |C|1|SQLERRTEXT : transaction rolled back by an internal error: Allocation failed ; $size$=58047088|
  |C|1|             ssed; $type$=pool; $inuse_count$=31630; $allocated_size$=753581150328; $failure_t|
  |C|1|             EM_LIMIT; $failure_flag$= [/bas/754_REL/src/dbs/hdb/dbsdbtrc.cpp#617]            |
  |C|1|sc_p=7f3585b8e900,no=128,idc_p=7f3585b9ce90,con=0,act=1,slen=182,smax=768,#vars=39,stmt=7f3585|
  |C|1|prepared=0,lastPrepareTime=20240918052603,nativeSQL=0,ignoreStmtId=0 [/bas/754_REL/src/dbs/hdb|
  |C|1|stmtid = <13/BSET                                    /33282/20170926115658> [/bas/754_REL/src/|
  |C|1|INSERT INTO "BSET" VALUES( ? , ? , ? , ? , ? , ? , ? , ? , ? , ? , ? , ? , ? , ? , ? , ? , ? ,|
  |C|1| , ? , ? , ? , ? , ? , ? , ? , ? , ? , ? , ? , ? , ? , ? , ? , ? , ? , ? , ? , ? ); [/bas/754_|
  |B|E|***LOG B64=> internal DB error aborts transaction [dbsh#1233]                                 |
  |B|1|SQL code: 129, SQL text: transaction rolled back by an internal error: Allocation failed ; $si|
  ----------------------------------------------------------------------------------------------------

• The indexserver trace reveals the out of memory event during statement execution :
  

  [73906]\{204396\}[562/29523190643] 2024-09-18 08:11:54.156752 e OOM_Notification Statement.cc(04606) : oom exception occurred at 'host:port': conn_id=204396, stmt_id=877876337077440, stmt_hash=73d64f65d357547b239df9eefa22dd3f, sql=INSERT INTO "BSET" VALUES( ? , ? , ? , ? , ? , ? , ? , ? , ? , ? , ? , ? , ? , ? , ? , ? , ? , ? , ? , ? , ? , ? , ? , ? , ? , ? , ? , ? , ? , ? , ? , ? , ? , ? , ? , ? , ? , ? , ? )
  [334397]{-1}[-1/-1] 2024-09-18 08:12:03.675832 i Savepoint        SavepointImpl.cpp(03044) : Savepoint current savepoint version: 1041856, restart redo log position: 0xb85e70d2146, next savepoint version: 1041857, last snapshot SP version: 1041854
  [74096]\{264202\}[883/29523443212] 2024-09-18 08:12:05.168965 i TraceContext     TraceContext.cpp(01269) : UserName=SAPABAP1, ApplicationUserName=<>, ApplicationName=ABAP:<>, ApplicationSource=SAPLF005:22325, Client=100, StatementHash=73d64f65d357547b239df9eefa22dd3f, EppRootContextId=36364539453032353636453945303235, EppTransactionId=C6614B7DD4F80C10E0066E9A386C77DE, EppConnectionId=66E93265A47E1809E10000000A5A20B5, EppConnectionCounter=1, EppComponentName=SID/host, EppAction=<>, StatementExecutionID=844435856891303
  [74096]\{264202\}[883/29523443212] 2024-09-18 08:12:05.168956 e Memory           mmPrecharge.cpp(01324) : Free precharge after error in 'addMemory'.
  [74096]\{264202\}[883/29523443212] 2024-09-18 08:12:07.163495 e Memory           mmPrecharge.cpp(01324) : Free precharge after error in 'addMemory'.
  [74096]\{264202\}[883/29523443212] 2024-09-18 08:12:07.164732 w Memory           mmPoolAllocator.cpp(01231) : Out of memory for Pool/ColumnStore/Main/Uncompressed, size 5804708864B, alignment=1B, flags 0x0, reason OPERATING_SYSTEM_LIMIT

SAP HANA Platform Edition 2.0

KBA , HAN-DB , SAP HANA Database , Problem