TSV_TNEW_PAGE_ALLOC_FAILED

[Bharath84]

Hi All,

Below is the dump analysis in Quality system.
>> Short dump has not been completely stored. It is too big.

No memory space available for extending table "T_CUST_FIN

What happened?

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

Error analysis

The internal table "T_CUST_FIN" could not be enlarged further.
To extend the internal table "T_CUST_FIN", 14848 bytes of memory space
was
needed, but none was available.
-
At this point, the table "T_CUST_FIN" had 351 eintries.

Please note:
To facilitate error handling, the internal table "T_CUST_FIN" was

deleted.

System environment

SAP Release.............. "40B"

I am facing the below dump in my zreport at the below code.

data   begin of t_cust_fin occurs 0.

        include structure bsad.

SELECT * FROM BSAD

APPENDING TABLE T_CUST_FIN

FOR ALL ENTRIES IN T_KUNNR

WHERE BUKRS = P_BUKRS-LOW

AND       BUDAT < S_BUDAT-LOW

AND       UMSKZ NE 'R'

AND       BLART NE 'RB'

AND       BLART NE 'RV'

AND       BSCHL NE '13'.

When executed table BSAD, it showed 14,00,055 records are available for the above selection criterion.

How to overcome this issue. Please advice.

Thanks,

Haritha

[Bharath84]

Haritha,

This is common thing that happens when large tables are involved. To overcome this issue:

1. Restrict the select with more conditions on the "where" so that you only select what is required.

2. If 1 is not possible, restrict the select to a certain # of entries process those and redo the select.

SELECT....

PACKAGE SIZE

ENDSELECT.

Thanks,

Vikram.M

[Former Member]

Haritha,

This is common thing that happens when large tables are involved. To overcome this issue:

1. Restrict the select with more conditions on the "where" so that you only select what is required.

2. If 1 is not possible, restrict the select to a certain # of entries process those and redo the select.

SELECT....

PACKAGE SIZE

ENDSELECT.

Thanks,

Vikram.M

[Bharath84]

Hi Vikram,

As per my knowledge, we should not write multiple select queries on one database table.

If there are multiple hits on the same database table it will be performance issue right?

Thanks,

HT

[Former Member]

Yes, normally you should not and try to avoid that as much as possible. That would be step 1 which is to add more conditions on the where clause.

You can always talk to your basis team and see if they would be able to allocate more storage space for programs/internal tables.

If none of these options work, only then you should think of working with package size option on the select.

Thanks,

Vikram.M

[Former Member]

Hi,

You could use OPEN/FETCH/CLOSE CURSOR also. Check the ABAP documentation for that.

FETCH NEXT CURSOR dbcur2

    INTO/APPENDING TABLE spfli_tab PACKAGE SIZE <Put some reasonable size may be 10000>

Use that internal table and refresh it so that the memory problem do not occur.

R