Application Development and Automation Discussions
Join the discussions or start your own on all things application development, including tools and APIs, programming models, and keeping your skills sharp.
cancel
Showing results for 
Search instead for 
Did you mean: 
Read only

Short Dump

Former Member
0 Likes
639

Hi,

I have got this short dump in Production for one of my Interfaces '' No storage space available for extending table "IT_2211406".

As this is the first time the legacy system has given a big file (More number of records). Does anyone has a fast solution on this?

Thanks.

1 ACCEPTED SOLUTION
Read only

romanweise
Active Contributor
0 Likes
620

Hi,

looks like you run out of table space for extending the database table when you tried to insert a large amount of records.

You will need the basis administration to enlarge the table space, if there is not only a logical but a really physical restriction you will need a bigger storage array.

Rgds.

Roman

4 REPLIES 4
Read only

romanweise
Active Contributor
0 Likes
621

Hi,

looks like you run out of table space for extending the database table when you tried to insert a large amount of records.

You will need the basis administration to enlarge the table space, if there is not only a logical but a really physical restriction you will need a bigger storage array.

Rgds.

Roman

Read only

Former Member
0 Likes
620

hi,

You need more memory allocation for holding the records on to your table ... For this contact your basis consultant ...

Regards,

Santosh

Read only

Former Member
0 Likes
620

Hi,

definitley a memory problem within sap.

have a look at the extended memory parameters. difficult to give you answer how

to solve it as every os needs a different parameters.

Read only

matt
Active Contributor
0 Likes
620

In the dump you can, if I remember correctly, see how much memory was in use before the crash. Your basis chap will need to know this. It's possible that you need more hardware to handle the larger amount of data.

In the interim, look at ways of splitting the data into smaller datasets.

Also, look for memory leaks. I recall defining an internal table with an inner internal table, where I used OCCURS 0 on the inner. That mean every record at the outer level was taking 8K, instead of the expect 20 bytes. I rapidly ran out of memory!

matt