Increase internal table memory

[Former Member]

Dear Techis,

How to increase size of internal table. while executing it gettin in DUMP.

I checked wid basis consultanat the Heap memory is more than sufficient, but still my report is not gettin executed its showin dump .

Will anybody pls tell me is it possible to increase size of internal table as of now i am using "Occurs 0" if i use "occurs 100" is dis help in any way??

Pls Suggest

Regards

Santosh

[Former Member]

hi,

while declaring internal table

data: itab type table of xyz initial size n.

increase value of n from 0 step wise, and check when dump is not comming

by default if we do not specify initial size n, n is taken to be 0

if you are using occur 0, increasing it to higher value will definitely help

Edited by: Amit Gupta on Oct 4, 2008 1:21 PM

[former_member125931]

Occurs 0 is correct,there may b a another reason for Dump,can u send us Dump.

[Former Member]

Hi Shree,

The Dump is

Line width: 1700

Number of lines: 106904

Allocated lines: 106904

New no. of requested lines: 8 (in 1 blocks)

How to correct the error

The amount of storage space (in bytes) filled at termination time was:

The Dump is given Below

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

not available.

The internal table "\PROGRAM=ZFIGLN0002\DATA=IT_LINEITEM[]" 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: "Session memory"

Row width: 197

Number of rows: 43248

Allocated rows: 43248

Newly requested rows: 64 (in 1 blocks)

Last error logged in SAP kernel

Component............ "EM"

Place................ "SAP-Server TCPRDSAP_TCP_00 on host TCPRDSAP (wp 4)"

Version.............. 37

Error code........... 7

Error text........... "Warning: EM-Memory exhausted: Workprocess gets PRIV "

Description.......... " "

System call.......... " "

Module............... "emxx.c"

Line................. 1881

The error reported by the operating system is:

Error number..... " "

Error text....... " "

The amount of storage space (in bytes) filled at termination time was:

Roll area...................... 1508832

Extended memory (EM)........... 383623632

Assigned memory (HEAP)......... 369003312

Short area..................... " "

Paging area.................... 24576

Maximum address space.......... " "

If the error occures in a non-modified SAP program, you may be able to

find an interim solution in an SAP Note.

If you have access to SAP Notes, carry out a search with the following

keywords:

"TSV_TNEW_PAGE_ALLOC_FAILED" " "

"ZFIGLN0002" or "ZFIGLN0002"

"POPULATE_SUMMARY_INFO"

If you cannot solve the problem yourself and want to send an error

notification to SAP, include the following information:

1. The description of the current problem (short dump)

To save the description, choose "System->List->Save->Local File

(Unconverted)".

2. Corresponding system log

Display the system log by calling transaction SM21.

Restrict the time interval to 10 minutes before and five minutes

Above is the error in showing in Dump Analysisi

i Checked heap memory parameter thru basis consultant and its more as compared to dis

[former_member125931]

If you are using ECC6.0 do the setting like below in ur ABAP editor

UTILITIES --> SETTINGS ---> ABAP EDITOR -

---

>DOWNWARD-COMP.LINE.LENGTH here un check the check box

But I don't think it is your problem,your coding taking so much of time it need to be change just send ur code once

Edited by: Sree on Oct 4, 2008 2:06 PM

[piyush_mathur]

Hi Santosh,

No need to increase internal table memory. You first analyze cause of dump in ST22.

Piyush

[Former Member]

Hi,

If you declare with occurs 0 or 100 it doesn't matter, it takes care at run time. So the problem is in your Select query or some other code which is taking more time. Plz check in debugg..

Regards,

Sarvesh

[former_member585060]

Instaed of declaring the Internal Table with Occurs statement.

Declare the Internal table structure with TYPES statement,

Then Declare an internal table with DATA statement for above structure, Then the workarea.

Ex:-

TYPES : BEGIN OF ty_emp,

empno(2) TYPE c,

empid(10) TYPE c,

empname(3) TYPE c,

END OF ty_emp.

DATA : it_emp TYPE TABLE OF ty_emp,

wa_emp TYPE ty_emp.

Regards

Bala Krishna

[former_member212653]

I dont think your problem will be solved by increasing the initial size. Use field-symbols instead of internal tables. They can hold more data.

FIELD-SYMBOLS:<f1> TYPE STANDARD TABLE OF x_data.

[Former Member]

The trick is not to increase the amount of memory available, but to decrease the amount you are consuming.

Rob