Application Development and Automation Discussions
Join the discussions or start your own on all things application development, including tools and APIs, programming models, and keeping your skills sharp.
cancel
Showing results for 
Search instead for 
Did you mean: 
Read only

MEMORY LOW

Former Member
0 Likes
758

Hi

I already use this function :

CALL FUNCTION 'PROGRESS_INDICATOR'

EXPORTING

i_text = 'Transferring data........ '.

This causes the system not to timeout after 1200secs.

But after about 40 minutes it gives another error: "Memory low. Leave the transaction before taking a break!"

When I check in debug, the internal table i'm filling contains +- 1.5 million records of type char length 1500.

Any ideas how to avoid having this error?

Greets

1 ACCEPTED SOLUTION
Read only

Former Member
0 Likes
716

Internal table can hold upto 2 GB of data ..

It can be increased to 4 GB , but not recommended ...

6 REPLIES 6
Read only

Former Member
0 Likes
716

hi,

Take an assistance from your basis consultant in increasing the memory ...

Regards,

Santosh

Read only

Former Member
0 Likes
717

Internal table can hold upto 2 GB of data ..

It can be increased to 4 GB , but not recommended ...

Read only

0 Likes
716

Actually it still gives the error: TIME_OUT.(time limit exceeded)

My mistake sorry.

But it gives a notification on bottom of the screen saying "Memory Low..." and I don't think the data is anyway near 2GB.. its just plain text so..

Please every little help is welcome..

Edited by: Bert Neels on Apr 24, 2008 2:49 PM

Read only

0 Likes
716

You can be surprised at how big that internal table can get when you have a lot of data.

Maybe you just have to much data, and need to split it up in smalled blocks?

Read only

0 Likes
716

I've just transferred about 500,000 records to a plain text file.

The size was 137MB so it doesn't come near 2GB..

Read only

0 Likes
716

Then i have no idea what the problem could possibly be.