3390691 - Migrating from ECC to S/4HANA is getting cancelled

Symptom

1. When migrating from ECC to S/4HANA one package is getting cancelled in ENR step and an ST22 dump like the one below can be observed:

Category ABAP programming error
Runtime Errors AMDP_EXECUTION_FAILED
Except. CX_AMDP_EXECUTION_FAILED
ABAP Program CL_FINS_CO_MIG_UTIL===========CP
Application Component FIN-MIG-CO
Date and Time 23.08.2023 19:40:40
----------------------------------------------------------------------------------------------------

----------------------------------------------------------------------------------------------------
|Short Text |
| Error while executing a database procedure |
----------------------------------------------------------------------------------------------------

----------------------------------------------------------------------------------------------------
|What happened? |
| During execution of database procedure |
| |
| CL_FINS_CO_MIG_UTIL=>MIGRATE_COBK_COEP |
| |
| an error occurred. |
| |
| SQL code of the database: 4 |
----------------------------------------------------------------------------------------------------

----------------------------------------------------------------------------------------------------
|What can you do? |
| Note which actions and entries caused the error to occur. |
| |
| Consult your SAP administrator. |
| |
| Using transaction ST22 for ABAP dump analysis, you can view, manage, |
| and retain termination messages for longer periods. |
| Note which actions and entries caused the error to occur. |
| |
| Consult your SAP administrator. |
| |
| Using transaction ST22 for ABAP dump analysis, you can view, manage, |
| and retain termination messages for longer periods. |
----------------------------------------------------------------------------------------------------

----------------------------------------------------------------------------------------------------
|Error analysis |
| An exception has occurred in class "CX_AMDP_EXECUTION_FAILED". This exception |
| was not caught |
| in procedure "MIGRATE_COBK_COEP" "(METHOD)" or propagated by a RAISING clause. |
| Since the caller of the procedure could not have anticipated this |
| exception, the current program was terminated. |
| The reason for the exception occurring was: |
| The reason for the exception is: |
| When calling database procedure |
| |
| CL_FINS_CO_MIG_UTIL=>MIGRATE_COBK_COEP |
| |
| an error occurred. The error message begins with (full message under |
| "Information about database procedures (AMDP)": |
| |
| "cannot allocate enough memory: |
| "SAPHANADB"."CL_FINS_CO_MIG_UTIL=>MIGRATE_COBK_COEP#stb2#20220401214717": |
| line 17 col 3 (at pos 509): |
| "SAPHANADB"."CL_FINS_CO_MIG_UTIL=>MIGRATE_COBK_COEP": line 442 col 3 (at pos |
| 19154): search table error: [9] Memory alloc" |
----------------------------------------------------------------------------------------------------

2. When checking Database diagnosis files you see indexserver_vhrsushddb01.30640.rtedump.<timestamp>.compositelimit_oom.trc trace files being generated and contains entries similar to this:

[MEMORY_LIMIT_VIOLATION] Information about current memory composite-limit violation: (2023-08-23 19:02:20 090 Local)
Composite limit violation (OUT OF MEMORY) occurred.
Composite limit=25gb (26843545600b)
Root allocator name=Connection/207279/Statement/890260483361979
Host: <host_name>
Executable: hdbindexserver
PID: <pid_number>
Failed to allocate 251.21mb (263415040b).

3. When using the using the statement number 890260483361979 collected from Root allocator name(Connection/207279/Statement/890260483361979) to find the SQL statement caused the memory violation we find the below

597704[thr=10506]: SqlExecutor, TID: 75, UTID: 103132904, CID: 207279, LCID: 207279, SEID: 844433711558668, parent: ---, SQLUserName: "SAPHANADB", AppUserName: "JSOL02", AppName: "ABAP:SRD", ConnCtx: 207279 {LDBID: 3, LCID: 207279}, StmtCtx: (1) 890260393113050 {Parent: 207279, P: 5, THRL: 13, MEMLGB: 25, TIMESec: 0, ObjHdl: 139536600442112, User: "SAPHANADB", Schema: "SAPHANADB", SesCtx: {ObjHdl: 139695782338560, CID: 207279, LCID: 207279, User: "SAPHANADB", Schema: "SAPHANADB", Ver: 3319, CtxID: 793547}}, (2) 890260483361979 {Parent: 207279, P: 5, THRL: 13, MEMLGB: 25, TIMESec: 0, SesCtx: {ObjHdl: 139695782338560, CID: 207279, LCID: 207279, User: "SAPHANADB", Schema: "SAPHANADB", Ver: 3319, CtxID: 793547}}, WorkloadCtx: 844442163147342{INDI, P=5, THRL=13, MEMLGB=25, TIMESec=0, WTXMin=0, ICURMin=720, NAME=_SYS_DEFAULT}, type: "SqlExecutor", method: "NoAction", detail: "", command: "
Dump at QueryExecution:
{
Project::do_open
Buffer id: 48
Operator id: -1
}

{
SQL:
/* procedure: "SAPHANADB"."CL_FINS_CO_MIG_UTIL=>MIGRATE_COBK_COEP" variable: LT_COEP2 line: 442 col: 3 (at pos 19154) */

<CODE>

Environment

HANA 1.0
HANA 2.0
SAP S/4HANA 2022

Product

SAP HANA 1.0, platform edition ; SAP HANA, platform edition 2.0 ; SAP S/4HANA 2022

Keywords

CL_FINS_CO_MIG_UTIL, MIGRATE_COBK_COEP, CX_AMDP_EXECUTION_FAILED, CL_FINS_CO_MIG_UTIL===========CP, memory, Memory alloc, compositelimit, , KBA , HAN-DB , SAP HANA Database , FIN-MIG , SAP Simple Finance data migration , HAN-DB-ENG , SAP HANA DB Engines , 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.