Dump Memory_no_more_paging

[Former Member]

I have this problem when I want to export 3 tables

internal (itab1 is great, itab2 is average, is itab3

small). That's what I do handle the dump

so as not to drop the program, I did it the

follows:

Using exceptions to the command catchebles

export found this: so export_buffer_no_memory

use.

FREE MEMORY ID 'ITAB1'.

FREE MEMORY ID 'ITAB2'.

FREE MEMORY ID 'ITAB3'.

CATCH SYSTEM-EXCEPTIONS export_buffer_no_memory = 4.

T_itab1 EXPORT TO MEMORY ID 'ITAB1'.

ENDCATCH.

CATCH SYSTEM-EXCEPTIONS export_buffer_no_memory = 4.

T_itab2 EXPORT TO MEMORY ID 'ITAB2'.

ENDCATCH.

CATCH SYSTEM-EXCEPTIONS export_buffer_no_memory = 4.

T_itab3 EXPORT TO MEMORY ID 'ITAB3'.

ENDCATCH.

When you pass the first itab1 if it controls the dump,

it passes the second itab2 also controls the dump,

but when it comes to the third itab3 is where

falls, apparently memory is full, or I do not

using the right catch??.

I wonder if they know the problem and how could

fix, thanks.

[pole_li]

Hi,

Maybe you'd better split itab1 into two internal tables by restricting the query condition, or ask your basis guys to adjust the limitation of paging setting.

regards

Pole

[former_member195402]

Hi,

which exception do you want to catch excatly?

There are at least to possible exceptions

CX_SY_EXPORT_BUFFER_NO_MEMORY

CX_SY_EXPORT_NO_SHARED_MEMORY

I think, you'll have the first kind, but what's the type of the runtime error?

You should ever catch CX_ROOT in addition!

Regards,

Klaus.