Error Message in SAP .No more memory available
to add rows to an internal table.
Error message coming scenario.
An attempt was made to add rows to an internal table. There
was no memory available for this, however.
What you can do?
Note proper actions and entries details caused the error to
occur.
Go to SAP
administrator.
T-code: ST22 Using transaction for analysis ABAP dump, you
can identify, view, manage, and retain termination messages for longer periods.
Try to find whether the transaction will run with less main memory. If the
problem is due to a temporary bottleneck, run the transaction again. If the
error persists, ask your system administrator to check the following profile
parameters:
Ø
ztta/roll_area (1.000.000 - 15.000.000) classic
roll area per user and internal session.
Ø
ztta/roll_extension (10.000.000 - 500.000.000) available
memory/user in extended memory EM.
Ø
ztta/max_memreq_MB maximum size of an
individual memory request. (in MB).
Ø
abap/heap_area_total (100.000.000 - 1.500.000.000).available
memory (malloc) for all users of an application server. If several background
processes are running on one server, temporary bottlenecks can 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 centre about this.
§
abap/heap_area_dia: (10.000.000 - 1.000.000.000)
restriction of the memory that can be allocated to the heap with malloc per
dialog process.Parameter for background processes:
§
abap/heap_area_nondia: (10.000.000 - 1.000.000.000) restriction
of the memory that can be allocated to the heap with malloc per 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 meet their memory needs.
§
abap/shared_objects_size_MB: Size of the shared memory area that can be
used to save shared objects area instances. This memory area is global for all
users of the application server.
Error analysis:
No more rows could be added to internal table
"???". 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: 4904
No. of rows: 0
Allocated rows: 419750
Newly requested
rows: 2 (in 209874 blocks)