cancel
Showing results for 
Search instead for 
Did you mean: 

Solman - Memory Low

Former Member
0 Kudos

We're running solman with these following :

OS Windows NT

DB Oracle 10.2

RAM : 3,6 GB

SWAP : 16 GB

When we run transaction SOLAR_EVAL,

this message :

'Memory Low.Leave the transaction before taking a break'

Sometime it lead to Shortdump. It said :

Storage Parameters wrong

We already set parameters in the system profile :

-abap/heap_area_dia and

-abap/heap_area_nondia

according to the suggestion in the shortdump message.

But the problem still persistent.

Any Suggestion?

Accepted Solutions (0)

Answers (4)

Answers (4)

Former Member
0 Kudos

Hi mas

When the memory is low, there should be many swaps in PXA of ST02

markus_doehr2
Active Contributor
0 Kudos

This is a classical problem of a 32bit architecture.

Do you have /3GB option set in boot.ini?

--

Markus

Former Member
0 Kudos

Markus,

We dont set 3GB option in boot.ini

Regards,

Hary

Former Member
0 Kudos

I ran into a similar issue with a very similar setup. I fixed it by making adjustments to the various memory parameters that appear within transaction ST02.

First, make sure you are using all of the memory available on the system (parameter PHYS_MEMSIZE). A good place to start is by reading the material at http://help.sap.com/saphelp_nw70/helpdata/en/c4/3a74b2505211d189550000e829fbbd/frameset.htm (which I used to set the various parameters).

Hope that helps.

J. Haynes

Denver

Former Member
0 Kudos

J Haynes,

We already set all the parameters you mentioned,

but the problem still happen.

Regards,

Hary

Former Member
0 Kudos

Two quick questions. How large is the page file? How large is the data cache for Oracle?

One other thing to check is the memory used by each process in Task Manager. Add these up and see if you are maxing out both the main memory and the page file.

markus_doehr2
Active Contributor
0 Kudos

Your transactions are consuming too much memory, where "too much" is here compared to the available size.

The dump is caused because you reach the maximum available memory allocated by a single process on a 32bit platform. There's nothing you can do about that but reducing the amount of memory needed or switch to a 64bit platform.

--

Markus

Former Member
0 Kudos

Dear Markus,

Actually our server is using Microsoft Windows Server 2003 R2,

and the processor is Intel Xeon CPU 3.6Ghz.

Is that a 32 Bit system or 64 bit system ?

Regards,

Hary

markus_doehr2
Active Contributor
0 Kudos

That CPU is most likely capable of running a 64bit operating system and applications.

What do you see in "system - status" under "machine type"?

--

Markus

Former Member
0 Kudos

The Machine Type is : 4x Intel 8

-Hary-

raguraman_c
Active Contributor
0 Kudos

Hi,

I wonder none of the replies have looked at the total virutal memory. It has to be a minimum of 8GB. Please check if you have atleast 8GB virtual memory.

This will solve your problem.

Feel free to revert back.

--Ragu

Former Member
0 Kudos

HI,

have you rebooted the system after changing those parameters.

if you see more problems, consult with sap.

Thanks,