TDMS step - Export data to files - runtime error

[Former Member]

We are in process of doing TDMS data transfer for Material BOM data related to a specific plant using Data Import Through Files for SAP ERP template and we are using Business process modeler BC- Material BOM for this.

At the step Export data to files we are getting runtime error CALL_FUNCTION_REMOTE_ERROR with Short text
as "No more storage space available for extending an internal table." in control/central system.
Further details are -
Termination occurred in the ABAP program "SAPLCNV_MBT_DEX" - in
  "CNV_MBT_DEX_TABSTRUC_FILL".
The main program was "CNV_MBT_DEX_EXP_DATA_EXT_SUB ".

In the source code you have the termination point in line 80
of the (Include) program "LCNV_MBT_DEXU31".
The program "SAPLCNV_MBT_DEX" was started as a background job.
Job Name....... "DEX_EXP_TDM9000K_C_000001"
Job Initiator.. "SROLLA"
Job Number..... 16090400

In the sender system the corresponding runtime error is -

TSV_TNEW_PAGE_ALLOC_FAILED with short text as "No more storage space available for extending an internal table."
Error analysis
    The internal table "\FUNCTION-POOL=CNV_MBT_ANALYSIS\FORM=CNV_MBT_DD_GET\DATA=%_
    %_ET_DD03L" could not be further extended. To enable
    error handling, the table had to be delete before this log was written.
    As a result, the table is displayed further down or, if you branch to
    the ABAP Debugger, with 0 rows.

    At the time of the termination, the following data was determined for
    the relevant internal table:

    Memory location: "Session memory"
    Row width: 594
    Number of rows: 6555552
    Allocated rows: 6555552
    Newly requested rows: 16 (in 1 blocks)

How to correct the error
    The amount of storage space (in bytes) filled at termination time was:

    Roll area...................... 5220352
    Extended memory (EM)........... 2002743520
    Assigned memory (HEAP)......... 2000763072
    Short area..................... " "
    Paging area.................... 0
    Maximum address space.......... " "

    If the error occures in a non-modified SAP program, you may be able to
    find an interim solution in an SAP Note.
    If you have access to SAP Notes, carry out a search with the following
    keywords:

    "TSV_TNEW_PAGE_ALLOC_FAILED" " "
    "SAPLCNV_MBT_ANALYSIS" or "LCNV_MBT_ANALYSISU01"
    "CNV_MBT_DD_GET"

However there is no SAP Note that helped to resolve this error, moreover we have increased all memory profile parameter values in sender and central /control system.

Thank you!

[amit_sharma36]

Hello Sai,

you can reduce block size and file size using view V_CNVMBTDEXDEFAU and restart activity.

Best Regards,

Amit Sharma

[Former Member]

Hello Sai,

Has the error been fixed which you encountered?

You can raise an OSS message if you are still facing the issue.

Also what is the DMIS 2011 SP level of your system ?

Best Regards,

Farheen.

[rajesh_kumar2]

Hello Sai,

Have you checked the note composite note 1741455 ?

There are some corrections related to TDMS file transfer scenario mentioned in this note.

Make sure you have implemented the relevant notes as per the patch level of your DMIS/DMIS_CNT.

BR

Rajesh

[former_member206552]

Hi Sai

Rajesh has a very important point, was all the required notes implemented on the systems as this will resolve a lot of problems for you.

Best Regards

Marius

[Former Member]

I have applied all the notes as per 1741455 much earlier. Has anyone actually encountered such error or know a fix for such issue?

[amit_sharma36]

What is DMIS 2011 SP level?

[Former Member]

Has anyone had a similar issue or any expert suggestions?

[former_member206552]

Hi Sai,

you need to look at the memory management of the system this is not sole related to TDMS, i know tdms is causing this now because of the overheads but you need to have the system correctly setup

please also have a look at this tread,

http://scn.sap.com/thread/1522872

Please let me know if this does not solve the problem

Best Regards

Marius

[former_member206552]

Hi Sai,

Please try and extend parameter rdisp/PG_MAXFS on the system giving the error.

you can also have a look at the following 2 notes

Note 133909 - Maximum value for PG_MAXFS, PG_SHM, ROLL_MAXFS, ROLL_SHM

Note 146289 - Parameter Recommendations for 64-Bit SAP Kernel

Hops this helps

Best Regards

Marius

[Former Member]

I have done that already. I guess I have to change something on the table level.

Has someone got into similar issue, suggest a fix.