UCMON Short dump - SYSTEM_NO_ROLL

[Former Member]

We are getting an error every single time we execute the task in the monitor for Load from Data Stream tasks. The data is coming from 0PCA_C01 cube and loaded into a consolidation area that is built off of 0BCS_C10. We have configured all of the necessary mappings and have successfully tested the load once.

This same memory error has came up every time since. Our Basis people and employees from SAP are saying that it is not a memory problem.

Has anyone ran into this problem?

[former_member588240 · Accepted solution]

Can you please provide the error message?

If it is a short dump, can you pls give the error analysis?

I will be able to help you once you give the output of error message details.

[Former Member]

There was a parameter setting that was missing for abap/shared_objects_size_MB. Needed to be set in RZ11 as 200 - 300 MB

[Former Member]

That is what the OSS note says.

[Former Member]

As I wrote several times, there are some notes related to issue. It's simply the harder requirements from FINBASIS. The solution is written in the system as a part of the system configuration:

SPRO: SEM/Business Analytics -> Fin. Basis -> Master Data Framework -> System Settings -> Profile Parameter Setting. Click on the book icon and see the directions.

[Former Member]

It's looks to me as really related to memory problem. But not simply the physical memory on the disk.

It's either:

- tables space issue (as Mani pointed out), or

- PXA no free space, or

- ABAP shared memory issue.

Check it out with your basis team.

Edited by: Eugene Khusainov on Dec 19, 2007 11:18 PM

[Former Member]

Can you check OSS note 741864 ?

[Former Member]

Runtime Errors SYSTEM_NO_ROLL

Date and Time 12/18/2007 05:02:31

Short text

Unable to fulfil request for 1048576 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.

Note which actions and input led to the error.

For further help in handling the problem, contact your SAP administrator

.

You can use the ABAP dump analysis transaction ST22 to view and manage

termination messages, in particular for long term reference.

If you have access to SAP Notes, carry out a search with the following

keywords:

"SYSTEM_NO_ROLL" " "

"GP484FLR7YDDTQ0KO1C6L0EN0PM===CP" or "GP484FLR7YDDTQ0KO1C6L0EN0PM===CM001"

"CONSTRUCTOR"

Hopefully that is enough. I do not know how to attach anything in this forum

[former_member588240]

Can you please advise me SEM-BCS version? Please also advise the support package level.

I can see as many as 10 SAP notes for patches/ applying with the error messages mentioned by you.

[Former Member]

I faced similar table space issue in implementation and suspected it to be table space issue and when I searchd the OSS notes many were giving different reason.

Submitted message to SAP and SAP asked to modify the configuration in fiscal year variant related parameters. It is not the normal FYV parameters settings in UCWB, but additional one.

I suggest you to submit message to SAP and have SAP look at your issue.. Also you can paralelly evaluate the OSS notes incase your support pack level is lower ones.

[Former Member]

The version that we are on is SAP NetWeaver 2004s. The support pack level is SAPKW70014 for SAP_BW, SAPKGS6010 for SEM-BW, and SAPKIBIIP6 for BI_CONT.

Let me know what else you need and thank you.

[Former Member]

Do you recall where the setting was in SEM/ BW? In getting your information, I started looking around the master data IMG for BCS and found a transaction RZ11 (Profile Parameter Setting), which does appear like it could give us some added benefit.

Could you look at that transaction in your system to see if you have anything maintained that could assist?

Thanks