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

[Former Member]

Dear All,

when i execute a report of bank balances, it will show an error  (No more storage space available for extending an internal table).

short dump - TSV_TNEW_PAGE_ALLOC_FAILED.

how i can extend the size of an internal table.

Thanks

Moderator message: very frequently discussed, please search for information using the technical short dump name.

Message was edited by: Thomas Zloch

[nishant_jain3]

(No more storage space available for extending an internal table).

This error means that your internal table has large size compare to memory.

Try to reduce your selection criteria or contact BASIS team.

There are already many posts related to this error on forum.

[Sijin_Chandran]

Hi Robbin,

Please try with Note 166551.

You can also try with the Related notes as well.

[Venkat_Sesha]

Hi,

An Internal Table size is of size 0 is 8KB.

Check the below links for Internal Table size details.

http://www.google.co.in/#hl=en&tbo=d&output=search&sclient=psy-ab&q=internal+table+size+sap&oq=inter...

http://scn.sap.com/message/3514789#3514789

Also I want to suggest use of Selects with OPEN CURSOR and FETCH CURSOR will avoid such kind of problems. Especially when you want to fetch data from Accounting/Finance/Banking tables. Then you should use CURSOR concept because of lot of data will be there in those tables.

Check the below example for Using CURSOR in the Select statements.

   *can't join table with bseg because bseg is a cluster table
  OPEN CURSOR WITH HOLD c_cursor FOR
  SELECT bukrs belnr gjahr
      FROM bkpf
     WHERE cpudt = p_cpudt
       AND blart = 'ZC'.

  DO.
    FETCH NEXT CURSOR c_cursor INTO TABLE t_cpudt
                                  PACKAGE SIZE p_size.
    IF sy-subrc <> 0.
* ----- exit if no items fetched
      EXIT.
    ENDIF.

You can write your own logic here to doing some operations.

ENDO.

Hope this helps

[hendrik_brandes]

Hello Robbin,

this shortdump occurs, when you internal table needs more space as your workprocess can allocate. The workprocess memory will be configured within the instance profile.

Usually, this error occurs when reading a lot of data within one step from a database or when you collect data from external systems.

Try to change your loading strategie:

1) Reduce the amount of line through filter / less attributes within your structure

2) Look at the length of the line-structure of your table: is it possible to reduce it?

3) Use SQL-Cursors and read package oriented from database

4) use collect, if you have same keys and you want to aggregate data

Kind regards,

Hendrik

[former_member193464]

if its a custom report you need to change the select query at which its dumping , the reason is as all above have told. when there is a lot of data at once, use PACKAGE SIZE in your select query  or fetch cursor to avoid this dump .