Dum error: SYSTEM_NO_ROLL

[#1]

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: [email protected]. 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.

[Former Member]

Hello Veer,

If this is standard SAP then ST05 won't be of much help. ST05 is used for performance analysis (SQL/RFC etc.) You can go to ST05 activate trace and choose the type of trace you want (in this case SQl trace).

I reckon either you need to reduce the data or you need to change profile paramter values.

Before making changes to any of the profile paramters mentioned in my previous replycheck the value of this paramter: ztta/max_memreq_MB. This is nothing but OSS note 353579 as suggested by Juan . First increase its value (make it double of exisitng value)and do a check by trying the data load once again. I can't say for sure that changing the value of the paramter ztta/max_memreq_MB alone will fix this issue.

However if this does not work out then make changes to the other three parameters mentioned in my previous mail.

To check the exisiting values go to RZ11 and display the value for each paramter. here you can also read the documentation for each parameter. The documentation will guide you. Also each of these parameters will have maximum value so you will know what maximum value is allowed. I would recommend you to double the existing values for these paramters.Atleast try to increase the values by 50%.

Then you can make the changes in RZ10. For knowing how to make changes in RZ10 check this link:

http://help.sap.com/saphelp_nw04s/helpdata/en/c4/3a6247505211d189550000e829fbbd/content.htm

Regards.

Ruchit.

[Former Member]

Hi Ruchit,

I changed the parameters but still i am getting the same error but now the job runs for more time with any delay in time.

Please let me know the excat configuration if possible from your side.

Thanks,

Veera

[Former Member]

Hello Veer,

This is coming becasue roll areamemory is not sufficient to handle this kind of load. Is it custom report or standard report that you are using? If it is a custom report then first try to fine tune the code (check for select/update statements). ST05 will help you in identifying the bottlenecks.However if the error is coming with standard SAP or is not going away with fine tuning of custom code then you need to increase the values of profile parameters like:

ztta/roll_area, ztta/roll_extension and abap/heap_area_total (it all should be done with proper consideration).

Though I must add that the values given as default values by SAP are sufficient enough.

Another option is to reduce the number of entries you are trying to load.

Please award points if the answer was helpful.

Regards.

Ruchit.

[Former Member]

Hi Ruchit,

Could you pelase let me know how to use ST05, also we have not used any custom report. Can you please let em know SAP standard report to check this issue.

More over if you can let me know how to do the extention or the ztta/roll_area, ztta/roll_extension and abap/heap_area_total, what are the proper consideration to be taken in calculating this.

Please reply asap

[JPReyes]

Hi Veeraraghavan

This dump happen when the program ends because insufficient memory check the parameters suggested in the shortdump and increase if necesary.

There's lots of sap notes try note 353579

Hope this help!

Juan

Please reward with points if helpful