SYSTEM_NO_ROLL - Dump

[Former Member]

Hi,

I am getting error like this when i am executing my conversion program in back ground.

*********************************************************************

DUMP report

ABAP runtime errors SYSTEM_NO_ROLL

>> Short dump has not been completely stored. It is too big.

What happened?

Each transaction requires some main memory space to process

application data. If the operating system cannot provide any more

space, the transaction is terminated.

What can you do?

Try to find out (e.g. by targetted data selection) whether the

transaction will run with less main memory.

If there is a temporary bottleneck, execute the transaction again.

-

If the error persists, ask your system administrator to check the

following profile parameters:

o ztta/roll_area (1.000.000 - 15.000.000)

Classic roll area per user and internal mode

usual amount of roll area per user and internal mode

o ztta/roll_extension (10.000.000 - 500.000.000)

Amount of memory per user in extended memory (EM)

o abap/heap_area_total (100.000.000 - 1.500.000.000)

Amount of memory (malloc) for all users of an application

server. If several background processes are running on

one server, temporary bottlenecks may occur.

Of course, the amount of memory (in bytes) must also be

available on the machine (main memory or file system swap).

Caution:

Error analysis

More main memory area was requested.

However, all the available space has been used up.

Possible reasons:

- Many (large) internal tables.

- Many (large) programs active.

- Deep nesting of subroutines with a lot of local data.

009700 *&

009710 *

009720 *& Form FETCH_FEBEP

009730 *&

009740 * Form to fetch cheque number and Refr

009750 *

009760 FORM fetch_febep.

009770

009780 IF NOT tbl_invoice[] IS INITIAL.

009790 SELECT nbbln chect avsid valut kw

009800 FROM febep INTO TABLE tbl_febep

009810 FOR ALL ENTRIES IN tbl_invoice

> WHERE nbbln EQ tbl_invoice-augbl.

***********************************************************************

Pls let me know - what is to be done to solve this. It was working fine in Development...but hitting DUMP at Quality.

Thanks

Senthil

[Former Member]

Hi,

I am getting error like this when i am executing my conversion program in back ground.

*********************************************************************

DUMP report

ABAP runtime errors SYSTEM_NO_ROLL

>> Short dump has not been completely stored. It is too big.

What happened?

Each transaction requires some main memory space to process

application data. If the operating system cannot provide any more

space, the transaction is terminated.

What can you do?

Try to find out (e.g. by targetted data selection) whether the

transaction will run with less main memory.

If there is a temporary bottleneck, execute the transaction again.

-

If the error persists, ask your system administrator to check the

following profile parameters:

o ztta/roll_area (1.000.000 - 15.000.000)

Classic roll area per user and internal mode

usual amount of roll area per user and internal mode

o ztta/roll_extension (10.000.000 - 500.000.000)

Amount of memory per user in extended memory (EM)

o abap/heap_area_total (100.000.000 - 1.500.000.000)

Amount of memory (malloc) for all users of an application

server. If several background processes are running on

one server, temporary bottlenecks may occur.

Of course, the amount of memory (in bytes) must also be

available on the machine (main memory or file system swap).

Caution:

Error analysis

More main memory area was requested.

However, all the available space has been used up.

Possible reasons:

- Many (large) internal tables.

- Many (large) programs active.

- Deep nesting of subroutines with a lot of local data.

009700 *&

009710 *

009720 *& Form FETCH_FEBEP

009730 *&

009740 * Form to fetch cheque number and Refr

009750 *

009760 FORM fetch_febep.

009770

009780 IF NOT tbl_invoice[] IS INITIAL.

009790 SELECT nbbln chect avsid valut kw

009800 FROM febep INTO TABLE tbl_febep

009810 FOR ALL ENTRIES IN tbl_invoice

> WHERE nbbln EQ tbl_invoice-augbl.

***********************************************************************

Pls let me know - what is to be done to solve this. It was working fine in Development...but hitting DUMP at Quality.

Thanks

Senthil

[former_member137336]

Hello Senthil,

I see that your selection is returning more number of records for which the system is not able to service the memory requirement. This cause the dump.

There can be two reasons why this is not happening in development

1. The data in development system is less

2. The memory allocated for a process in development is more.

Please try to reduce the number of records in the selection adding more where condition restriction. You can also try reducing the number of fields being selected.

Hope this will solve.

Thanks

Farzan