No storage space available for extending an internal table

[Former Member]

Hi,

While executing a select statement my program is giving dump.

<b>ShrtText</b>

No storage space available for extending an internal table.

<b>What happened?</b>

You attempted to extend an internal table, but the required space was

not available.

<b>Error analysis</b>

The internal table "IT_49" could not be enlarged further. To allow

error handling, the table had to be deleted before this log was

created. So, if you branch to the ABAP debugger from the display

of this log, the table will there be displayed with 0 rows.

At the moment of the termination, the following data was

determined for the respective internal table:

Storage location: "Session memory"

Row width: 7936

Number of rows: 1594

Allocated rows: 1594

Newly requested rows: 2 (in 1 blocks)

Please let me know how to solve this problem.

Thanks in advance

Suresh

[Former Member]

Kamlesh is right.

Kindly increase the memory size of your application server through the below mentioned transaction.

Pass this issue to the Basis guys, they would be able to sort this issue.

Regards

Senthil

[Former Member]

Unfortunately the interesting part of the short dump was stripped.

There are some rows telling you how many memory has been allocated in the WP, also information on the hardware platform (Windows/Unix) and architecture (32/64 bit ) would be helpfull.

regards

Peter

[Former Member]

Is this short dump occuring for single / many programs?

Alternatively, you could ask the enduser to split the inputed data into smaller chunks.

[Former Member]

Hi,

You can overcome this error by extending the table space.

conn /as sysdba

brtools

tablesapce maintanence

extend tablespace

try out,,let me know in case of issues

jag

[Former Member]

> Hi,

> You can overcome this error by extending the table

> space.

> conn /as sysdba

> brtools

> tablesapce maintanence

> extend tablespace

> try out,,let me know in case of issues

> jag

This is a NO/NO/NO.

As commented a couple of times here, the problem is not related whatsoever to the database.

The problem is in an internal SAP table, not in a PHYSICAL database table.

Pay attention to the error:

<quote>

ShrtText

No storage space available for extending an <b>internal</b> table.

<quote>

If it were a problem with the tablespace the error you get is an oracle error:

ORA-01650: unable to extend rollback segment <rbs> in tablespace <tsp>

ORA-01651: unable to extend save undo segment for tablespace <tsp>

ORA-01652: unable to extend temp segment in tablespace <tsp>

ORA-01653: unable to extend table <tab> in tablespace <tsp>

ORA-01654: unable to extend index <ind> in tablespace <tsp>

ORA-01655: unable to extend cluster <clus> in tablespace <tsp>

ORA-01658: unable to create INITIAL extent for segment in tablespace.

<tsp>

ORA-01659: unable to allocate MINEXTENTS beyond <ext> in tablespace

[Former Member]

Hello

is it related with short dump TSV_TNEW_PAGE_ALLOC_FAILED ?

if yes, you can check this profile parameter (from RZ10 / RZ11) abap/heap_area_total , abap/heap_area_dia , and/or abap/heap_area_nondia ...

Thanks

If usefull then dont forget to give reward points

[Former Member]

I guess increasing the memory profile paramater will just 'delay' the occurance of the dump.

We need to find out how much the data is being punch?

Is it a SAP standard program / User created program?

Are there any expensive SQL statements in the program query?

[muzaidi_marjuki]

yes, i have the same error. i have stop the sap service and up the service back. so what can i do with ur suggesttion can u give me the step . thanks

[Former Member]

is there any guide how to set these parameters?

[markus_doehr2]

Assuming you're on Windows check the following notes:

88416 - Zero administration memory management as of 4.0A/ Windows

This note will give you an understanding how memory is allocated.

110172 - Windows: Transactions with large memory requirements

129813 - Windows: Problems due to address space fragmentation

Also see

http://service.sap.com/msplatforms

--> Windows Server

and download the PDF "Windows 32-Bit: Optimizing Memory Settings for SAP Systems "

Markus

[Former Member]

Hi,

The error is not related to the database or lack of space on the tablespaces, but on a SAP

internal table. Perhaps you can check on the ABAP Forum if you do not get good replies here.

[Former Member]

AS Fidel mentions, this is a server memory issue, NOT a DB space issue. An internal table is a table that resides in server memory. You either need to look at reducing the amount of data you're attepting ot put in thei table, allocate more memory, or look at other techniques to live within the memory allocated. ABAP forum is the best place to pursue this. Talk to your Basis Aadmin and see if more memory is an option.

[Former Member]

Suresh

If issue with space have a look on output

SELECT BYTES FROM DBA_FREE_SPACE

WHERE TABLESPACE_NAME = '<tablespace>'

ORDER BY BYTES ASC;

if not u need to look at notes to apply correction.

Is space issue increase space concerned with table means tablespace size

Regards

vinod