Symptom
- During the downtime phase of a conversion from ECC to S/4 HANA, an error is encountered.
- The error message in the log 'MIGRATE_DT_00141_CDCLS_IMP.LOG' indicates a failure in creating an index for 'CDPOS~0'.
- During the downtime phase (MAIN_SWITCH/SUBMOD_MIG_SWITCH_ORG/SUBMOD_MIG_DOWNTIME_RUN/EU_CLONE_MIG_DT_RUN ) we run into below error:
# Find the detailed information in log 'MIGRATE_DT_00141_CDCLS_IMP.LOG':
A1 EGEN 011 CMDLINE: "/sapupgrade/CSI/SUM/abap/bin_754/R3load -i /sapupgrade/CSI/SUM/abap/load/migrate_dt/MIGRATE_DT_00141_CDCLS_IMP.CMD -table_suffix ~ -k 1W9geUM504800eqtdaYx1Qq3 -l /sapupgrade/CSI/SUM/abap/load/migrate_dt/MIGRATE_DT_00141_CDCLS_IMP.LOG"
A1 EIMP 001 Task for 'PCDPOS' executed #20250218132509
A2 ETSK 005 Finished create for object "CDCLS" of type "merge" in 4792.402 sec #20250218132509
A2 ETSK 008 ------------------------------------------------------------------
A2 ETSK 000 Starting create for object "CDCLS~0" of type "primary index" #20250218132509
A2 EIMP 004 CDPOS~0 dropped #20250218132509
A2EEIMP 047 Index creation failed before - listing duplicate records for 'CDPOS~0' with key fields: MANDANT OBJECTCLAS OBJECTID CHANGENR TABNAME TABKEY FNAME CHNGIND
A1 EGEN 002 ====================================================
A1 EDAT 006 Resource usage: GENERAL times: 570.205/ 0.639/ 0.003 2.6%/99.8%/75.2% real/usr/sys
A1 EDAT 006 Resource usage: DATABASE times: 21344.923/ 0.001/ 0.001 97.4%/ 0.2%/24.6% real/usr/sys
A1 EDAT 006 Resource usage: NULL times: 0.000/ 0.000/ 0.000 0.0%/ 0.0%/ 0.1% real/usr/sys
A1 EDAT 005 Memory usage: 12/0/0 MB buffer/objectcache/disk (0 reused buffers)
A1EEGEN 000 dbrc = 99: 'all DB errors, except for ...'
A1EEGEN 000 DB code 4
A1EEGEN 000 cannot allocate enough memory: Allocation failed; Reason: global allocation limit configured in [memorymanager] global_allocation_limit
Read more...
Environment
- Upgrade tools for ABAP
- Hana database
Product
SAP ERP all versions
Keywords
- SAP S/4 HANA, Conversion, ECC, Index Creation, CDPOS~0, Memory Allocation Limit, SAP Note 3191206
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.