cancel
Showing results for 
Search instead for 
Did you mean: 

TSV_TNEW_PAGE_ALLOC_FAILED - No more memory available to add rows to an internal table.

lpodile
Participant

While accessing the TM Rate table by following the below path, facing the short dump.

NWBC -> Master Data -> Rate Tables -> Maintain Rate Table -> Provide the Rate Table name -> Click on 'Continue' -> Getting the short dump now without displaying the table

Analysis from short dump:

What happened?
An attempt was made to add rows to an internal table. There was no
memory available for this however.

Information on where terminated
The termination occurred in ABAP program "/SCMTMS/CL_UI_RATE2_ASSISTANCECP",
in "_FILL_TABLE_M_DIM_PARTIAL". The main program
was "SAPMHTTP". In the source code, the termination point is in line 126 of (Include)
program "/SCMTMS/CL_UI_RATE2_ASSISTANCECM03F".

Technical Analysis:

We have implemented the OSS Note 2716170 but still facing the same issue. We have sent a issue to SAP and still waiting for response.

BASIS Analysis:

This is no technical issue- again an attempt to add too many data to internal table.

Internal tables have limits which cause the mentioned dump when reached, this is to protect systems.

Please respond with resolution if anyone have faced the same issue in TM. This is critical because no one is able to access the Rate table in production.


Accepted Solutions (1)

Accepted Solutions (1)

lpodile
Participant
0 Kudos

Hi..SAP responded with the solution as below

This is related to BASIS

1.Could you please check the profile parameters as mentioned in the dump infosheet?
These are the following:

o ztta/roll_area (1.000.000 - 15.000.000)
Classic roll area per user * internal mode usual amount of roll area per user internal mode
o ztta/roll_extension (10.000.000 - 500.000.000)
Amount of memory per user * extended memory (EM)
o abap/heap_area_total (100.000.000 - 1.500.000.000)
Amount of memory (malloc) for all users of an application server. If several background processes are running on one server, temporary bottlenecks may occur. Of course, the amount of memory (in bytes) must also be available on the machine (main memory or file system swap).
Caution: The operating system must be set up so that there is also enough memory for each process. Usually, the maximum address
space is too small.
Ask your hardware manufacturer or your competence center about this.
In this case, consult your hardware vendor abap/heap_area_dia: (10.000.000 - 1.000.000.000)
Restriction of memory allocated to the heap with malloc for each dialog process.

Parameters for background processes:
abap/heap_area_nondia: (10.000.000 - 1.000.000.000)
Restriction of memory allocated to the heap with malloc for each background process.

Other memory-relevant parameters are:
em/initial_size_MB: (35-1200)
Extended memory area from which all users of an application server can satisfy their memory requirement.

This is relevant to configuration:

Please maintain a value for filtering in the customizing (SPRO transaction) in the following path:
Transportation Management -> Basic Functions -> General Settings -> Define General Settings for SAP TM -> Max. Rate Table Entries Before Filtering

Currently the value is 0. Once you maintain a value in this field, a pop-up appears that states the potential value for rate combination is high. Kindly click 'Cancel' and you will be able to apply filters and the resultant rate table will be displayed.

Matt_Fraser
Active Contributor

Hi Lakshmi,

So which of the various suggestions from SAP Support did you apply? What was the final solution? Did you increase any of the memory parameters, and if so, which ones, and from what to what value? Did you apply the Max Rate Table Entries filter? If so, what did you set it to?

Cheers,
Matt

Answers (3)

Answers (3)

lpodile
Participant

Hi Isais,

Thank you for your response.

Also BASIS responded as below

The memory area is called heap memory which is static, session memory is not affected or involved.

The records are copied from Z table to internal table. Once entire heap is used by that table then dump occurs.

Temp files are not involved here.

Configured heap area could be increased from 4 to 6 Gb, however that puts risk on system and would allow up to approx 27000 records instead 19000.

Increase of heap memory parameters require system restart and approval from <XXXX>

Increasing heap area would just solve symptom but not underlying reason of bad application. Copying entire database tables to internal table is not good.

Can you use smaller selection criteria, so less data is handled?

From NWBC, We are trying to access the table by just entering the table name. and its giving the short dump. No where we have option to have selection criteria.

Attached the snapshot of this. Please share your thoughts.

isaias_freitas
Advisor
Advisor

Hello lakshmi,

From the basis perspective, what could be done is to increase the memory limits, if possible (depending on the server's capacity), nothing more.

Can you use smaller selection criteria, so less data is handled?

Regards,

Isaías

dasistdochscheisse
Active Participant
0 Kudos

> Increase of heap memory parameters require system restart

this can also be done with the report RSMEMORY. The change is not persistent. You can change the heap limit, EM limit and total heap size for dia and btc.