Dump -- No more storage space available for extending an internal table

[Former Member]

In Our system we are getting this dump

No more storage space available for extending an internal table

and because of it no user is able to login into the system.

We have Some classes in the system and we have defined shared memories to all classes according to regions.

So for a particular class means users of a region are not able to logon to systems and we are getting these dumps in the system.

So please suggest first how to clear the shared memory & how to conclude what activity in system made the shared memory full.

Regards,

Shivam Mittal

[Former Member]

Which OS you are running on ?

by the way the command is:

cleanipc <SAPSYSTEM> remove

Regards;

[Former Member]

My OS is HP-UNIX..

And we do not access on OS level,So please suggest the way to clear it from SAP level.

In dump it is also mentioned:

The internal table "\AREA=<Name>\INSTANCE=$DEFAULT_INSTANCE$\VER

SID=2\OBJ={O:1.2*\CLASS=<CLASS>\DATA=GT_BUFFER[1]-DATA" 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: "\AREA=<Name>\INST=$DEFAULT_INSTANCE$\CLNT=100"

Row width: 156

Number of rows: 0

Allocated rows: 63

Newly requested rows: 1216 (in 19 blocks)

Please also suggest what is the internel table name that is causing the issue.

Regards,

Shivam Mittal

[Former Member]

Hey Shivam,

First of all you shud know Internal tables provide a means of taking data from a fixed structure and storing it in working memory in ABAP (temporary and on fly). The data is stored line by line in memory, and each line has the same structure. In ABAP, internal tables fulfill the function of arrays. Since they are dynamic data objects, they save the programmer the task of dynamic memory management in his or her programs.

The minimum size of an internal table is 256 bytes and it may grows to 2GB. You if its full system throws an error like TSV_NEW or something realted to memory. Unlike all other ABAP data objects, you do not have to specify the memory required for an internal table. Table rows are added to and deleted from the table dynamically at runtime by the various statements for adding and deleting records.

May be the below link usefull for you...

http://help.sap.com/saphelp_45b/helpdata/en/34/8e73a36df74873e10000009b38f9b8/content.htm

[Former Member]

Shivam, there are several memory related parameters that can be looked and tuned. You can see them in RZ10 or by running ABAP RSPARAM.

But to start with, how much total physical memory you have in the system? You can see it in ST06. Also specify the available (free) physical memory and swap (paging) information from ST06.

Are there other SAP instances or non-SAP applications running on this system?

Regards.

[Former Member]

Hi,

Check this link.

If you are facing the issue while executing standard programs/tcode, try to tune the memory related parameters.

Regards,

Varadhu