Skip to Content
0
Former Member
Aug 29, 2006 at 04:43 AM

Dum error: SYSTEM_NO_ROLL

2872 Views

Hello all,

i am getting the following dump error due to data load failure. When we try to load data around 4 million records the run is going through sucessfully, but when we try the same load with say 6 million records the process chain fails with the following dump.

Please let me know if you have any oSS note which can be directly applied for this issue:

Following is the system configuration:

Application SAP NW04

O/S Windows 2003 server

Database Oracle 9i.

From the Database side we checked that any of the table is has issues but there was no issues from the DB side as per our DBA confirmation.

Please let me know if you have any resolution for this you can mail me in the following addres: veeraraghavan.srinivasan@vitalspring.com. Kindly help me in this asap.

Runtime Error SYSTEM_NO_ROLL

Date and Time 2006.08.28 11:59:37

-


-


ShrtText

Unable to fulfil request for 67108864 bytes of memory space.

-


-


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:

The operating system must be set up so that there is also

enough memory for each process. Usually, the maximum address

space is too small.

Ask your hardware manufacturer or your competence center

about this.

In this case, consult your hardware vendor

abap/heap_area_dia: (10.000.000 - 1.000.000.000)

Restriction of memory allocated to the heap with malloc

for each dialog process.

Parameters for background processes:

abap/heap_area_nondia: (10.000.000 - 1.000.000.000)

Restriction of memory allocated to the heap with malloc

for each background process.

Other memory-relevant parameters are:

em/initial_size_MB: (35-1200)

Extended memory area from which all users of an

application server can satisfy their memory requirement.

Make a note of the actions and input which caused the error.

To resolve the problem, contact your SAP system administrator.

You can use transaction ST22 (ABAP Dump Analysis) to view and administer

termination messages, especially those beyond their normal deletion

date.

-


-


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.