2518887 - CALL_FUNCTION_REMOTE_ERROR ST22 Dump During Custom Code Management Migration | SAP Knowledge Base Article

SAP Knowledge Base Article - Preview

2518887 - CALL_FUNCTION_REMOTE_ERROR ST22 Dump During Custom Code Management Migration

Symptom

When executing Custom Code Migration the job SM:CCLM_MIGRATION fails with the following error log:
CCLM Data Migration was completed...
Update collectors and extractors
Start the scheduling of the collectors monitoring job
Scheduling of the collectors monitoring job finished successfully
Finalize SCMON data migration to new BW architecture
UPL Migration - Step: Move open periods...
Internal session terminated with a runtime error CALL_FUNCTION_REMOTE_ERROR (see ST22)
Job cancelled 

When you click into the dump encountered in the job SM:CCLM_MIGRATION it is as follows:

Category               External Error
Runtime Errors         CALL_FUNCTION_REMOTE_ERROR

 Short Text
     "No more memory available to add rows to an internal table."

What happened?
    Error in the ABAP Application Program

    The current ABAP program "CL_AGS_CC_UPL_MULTI_CUBE_MIG==CP" had to be
     terminated because it has
    come across a statement that unfortunately cannot be executed.

Information on where terminated
    The termination occurred in ABAP program "CL_AGS_CC_UPL_MULTI_CUBE_MIG==CP",
     in "STEP5_MOVE_OPEN_PERIODS_2_DSO". The main program
    was "RAGS_CC_MIGRATION".

    In the source code, the termination point is in line 1047 of (Include)
    program "CL_AGS_CC_UPL_MULTI_CUBE_MIG==CM005".
    Program "CL_AGS_CC_UPL_MULTI_CUBE_MIG==CP" was started as a background job.

    Job name....... SM:CCLM_MIGRATION
    Job initiator.. 00461926
    Job number...... 09043300

In ST22 you will also see another dump occuring at the same time as the above dump. The dump is as follows:

Category               Resource Shortage
Runtime Errors         TSV_TNEW_PAGE_ALLOC_FAILED


 Short Text
     No more memory available to add rows to an internal table.

 Error analysis
    No more rows could be added to internal table
     "\FUNCTION=AGS_SCMON_READ_DATA_INFOPROV_Y\DATA=ET_YEARLY_DATA". To make
    troubleshooting possible, the table had to be deleted before this log
    could be compiled. This means that the table will either be displayed
    further down or, if you call the ABAP Debugger from here, with 0 rows.

    When the program was terminated, the internal table had the following
    characteristics:

    Memory location:             Session memory
    Row width:            1768
    No. of rows:            24467000
    Allocated rows:       24467000
    Newly requested rows: 1000 (in 125 blocks)

 How to correct the error
    The amount of memory (in bytes) used at termination time was:

    Roll area...................... 0
    Extended memory (EM) 38529357297
    Assigned memory (HEAP) 5002688064
    Short area.....................
    Paging area.................... 16384
    Maximum address space.......... 18446744073709551615
    If the error occurs in a non-modfied SAP program, you might be able to
    find a solution in the SAP Notes system. If you have access to the SAP
    Notes system, check there first using the following keywords:

    "TSV_TNEW_PAGE_ALLOC_FAILED"
    "SAPLAGS_CC_BI_AGGREGATE_SCMON" bzw. LAGS_CC_BI_AGGREGATE_SCMONU12
    "AGS_SCMON_READ_DATA_INFOPROV_Y"

Information on where terminated
    The termination occurred in ABAP program "SAPLAGS_CC_BI_AGGREGATE_SCMON", in
     "AGS_SCMON_READ_DATA_INFOPROV_Y". The main program
    was "SAPMSSY1".

    In the source code, the termination point is in line 334 of (Include)
    program "LAGS_CC_BI_AGGREGATE_SCMONU12".


Read more...

Environment

Solution Manager 7.2 SP05

Product

SAP Solution Manager 7.2

Keywords

CCM, Custom Code Management, Migration, CCM Migration, SM:CCLM_MIGRATION, UPL MIgration, UPL, CALL_FUNCTION_REMOTE_ERROR, CL_AGS_CC_UPL_MULTI_CUBE_MIG==CP, TSV_TNEW_PAGE_ALLOC_FAILED, AGS_SCMON_READ_DATA_INFOPROV_Y, SAPLAGS_CC_BI_AGGREGATE_SCMON, LAGS_CC_BI_AGGREGATE_SCMONU12 , KBA , SV-SMG-CCM , Custom Code Management , Problem

About this page

This is a preview of a SAP Knowledge Base Article. Click more to access the full version on SAP ONE Support launchpad (Login required).

Search for additional results

Visit SAP Support Portal's SAP Notes and KBA Search.