No storage space available for extending the internal table

[Former Member]

Hi,

Here is the error occured in the production system

Error analysis:

The internal table (with the internal identifier "IT_1044") could not be

enlarged any further. To enable error handling, the internal table had

to be deleted before this error log was formatted.

Error Search Criteria : TSV_TNEW_PAGE_ALLOC_FAILED

Question : How to delete this system internal table or how to solve this error

Thanks in advance.

BR,

Raj

[Former Member]

Hi Raja,

I don't have the solution.

But I think it's worth taking a look in the OSS notes.

[former_member215251]

Hi

This error occurs if the disp+work process in which the given programm is running is requesting more memory as it is allowed by several SAP Profile parameters and/or the Limits of the Operating system.

If you take a close look at the dump in ta. sm21 you can see the number of the Work Process - in the ta. sm50 you can look into the trace file of the WP - there you can see how much storage was allready allocated.

There is also a program in the kernel dir of the SAP System called <u>memlimits</u> with this programm you can check how much memory a WP can allocate.

Out from my experiance errors like this are caused by bugs in the program or bugs in the customizing

if you can post the sequense of the short dump and also the corresponding lines of the WP trace file - I can take a closer look.

Regards

Guenther

[Former Member]

Hey raj,

Did u get any solution for the problem?I'm also facing the same dump. If u could suggest something, that would be great..

Regards

Sriram

[Former Member]

Hi,

Check your program for the following cases: (there may be so many reasons but a couple of which that can more often cause such problem is only given here)

1. Such problems may occur because of fact that your data intensive tables are not fully qualified with key values. Check your key fields.

2.There might be some places in your program where database selection is done using FOR ALL ENTRIES in <itab> and that <itab> is empty and because of which the entire records in a database table is being fetched. Check for Initial condition of such tables before doing your database fetch.

if not <itab> is initial.

select <fields> FOR ALL ENTRIES IN <itab>...

endif.

3.When dealing with large volumes of data, refresh the internal tables after its last use and FREE the memory wherever possible. Keeping so many unused data in the runtime memory can cause the problem.

4. Also check with the administrator whether they have allocated enough memory in application server for background processing or not.

Regards,

Vijay