Production dump STORAGE_PARAMETERS_WRONG_SET

[Former Member]

Hi All,

We are getting below dump suddenly from last 2 days in our PRD system for one of critical FI report.No changes made to system and workload is also fine.

what could be the reason ?

Runtime Errors STORAGE_PARAMETERS_WRONG_SET

Date and Time 08.10.2007 10:30:38

ShrtText

&INCLUDE INCL_INSTALLATION_ERROR

What happened?

The current program had to be terminated because of an

error when installing the R/3 System.

The program had already requested 185589040 bytes from the operating

system with 'malloc' when the operating system reported after a

further memory request that there was no more memory space

available.

Error analysis

When the program was running, it was established that more

memory was needed than the operating system is able to provide savely.

To avoid a system crash, you must prevent this

situation.

-

---

Last error logged in SAP kernel

-

---

Component............ "EM"

Place................ "SAP-Server lfyd043a_PRD_00 on host lfyd043a (wp 0)"

Version.............. 37

Error code........... 7

Error text........... "Warning: EM-Memory exhausted: Workprocess gets PRIV "

Description.......... " "

System call.......... " "

Module............... "emxx.c"

Best Regards,

AjitR

[Former Member · Accepted solution]

What can you do?

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.

Set the system profile parameters

- abap/heap_area_dia

- abap/heap_area_nondia

to a maximum of 185589040. Then reduce the value by 10.000.000 to be on the

safe side.

Then restart the SAP System.

abap/heap_area_nondia and abap/heap_area_dia:

Set smaller than the memory achieved for each process

with 'malloc' and smaller than abap/heap_area_total

You should also check whether the available memory (file system

swap and main memory) is sufficient for the started program

and its data.

We have changed mentioned parameters and

Below are current settings for parameters

abap/heap_area_dia 2000000000 Byte Max. heap memory for dialog workprocesses

abap/heap_area_nondia 2000001024 Byte Max. heap memory for non-dialog workprocesses

[markus_doehr2 · Accepted solution]

What platform are you running? Windows 32 bit?

--

Markus

[Former Member · Accepted solution]

32 bit Windows Oracle 9.2.0.5

[Former Member · Accepted solution]

Markus,

I have already increased parameter but no gain for that Job,

[markus_doehr2 · Accepted solution]

Classical error on 32bit platform.

What you can try is:

- configure boot.ini using "/3GB /USERVA=2600" (see note 990538).

The problem is, you reach the 32bit limit of the maximum allocated memory. The process has already 1.8 GB memory and depending on the size of your buffers you will reach 2.6 GB quickly.

There's no quick solution for this, you should consider switching to 64bit hardware.

--

Markus

[Former Member · Accepted solution]

Markus,

Using 3GB option according to note 990538 , can i fix this problem.

As it is PRD system very less chance of moving this system to 64-bit as of now.

But is this note gives solution can i ask my OS guys to have look at it.

Best Regards,

AjitR

[markus_doehr2 · Accepted solution]

I don't know if that "fixes" the problem since I don't know how much data your program will need. It may help and this is the only way you can avoid that.

--

Markus

[former_member204746 · Accepted solution]

also check value for PHYS_MEMSIZE in your SAP profiles.

ask your user to use a more restrictive parameters.

long term: plan a conversion to 64-bit

[Former Member · Accepted solution]

or add an 64 Bit Dialog Instance into this system and run the memory consuming jobs there

peter

[Former Member · Accepted solution]

Guys ,

current value for PHYS_MEMSIZE is as below

Dflt value 7679

ProfileVal 7200

Current value 7200

Any changes you suggess ?

About 64-bit opion i have already initiated with OS guys but will take time ,

meanwhile i need to fix this critical issue.

Best Regards,

AjitR

[markus_doehr2 · Accepted solution]

And how much physical memory do you have installed?

Keep in mind, that one process can´t use more than 2.6 GB of that memory including the buffers.

2600 MB - = max. Memory your program can use

--

Markus

[Former Member · Accepted solution]

Phisical memory is 7GB total

do we need to increase phy_memsize

[markus_doehr2 · Accepted solution]

No, the parameter is correct.

Even if the system had 64 GB memory you would get the same erro because of the limitation of the 32bit platform.

--

Markus

[Former Member · Accepted solution]

Ok Markus then i must go for 3GB option activation now.

[Former Member · Accepted solution]

Markus,

i have activated 3 GB option and report is runnign fine , but

After a reboot with the /3GB option, we now only have 3.5 GB RAM available to the system as apposed to the 7.5 GB RAM we had before.

is it normal ?

[markus_doehr2 · Accepted solution]

How do you see that?

--

Markus

[Former Member · Accepted solution]

My computer right click - properties

RAM

Also i can see in ST06 transaction only 3.5 GB

[Former Member · Accepted solution]

Markus ,

Appreciate if you could give some comment on the issue.

[markus_doehr2 · Accepted solution]

Did you use just /3GB or /3GB /USERVA=2600? you need the second one (as I advised and as is written in the mentioned note).

--

Markus

[Former Member · Accepted solution]

This is the boot.ini forwarded by my OS guys

[boot loader]

timeout=30

default=multi(0)disk(0)rdisk(0)partition(2)\WINNT

[operating systems]

multi(0)disk(0)rdisk(0)partition(2)\WINNT="Windows Server 2003, Enterprise" /noexecute=optout /fastdetect /3GB

is there anything else to be added ?

[Former Member · Accepted solution]

[boot loader]

timeout=30

default=multi(0)disk(0)rdisk(0)partition(2)\WINNT

[operating systems]

multi(0)disk(0)rdisk(0)partition(2)\WINNT="Windows Server 2003, Enterprise" /noexecute=optout /fastdetect<b> /3GB /USERVA=2600</b>

is this the only difference i need to make.

[Former Member · Accepted solution]

Markus ,

Could you please confirm the same about userva

[markus_doehr2 · Accepted solution]

Yes.

Again - READ THE NOTE - everything you will need to know about those parameters (and maybe about other parameters you need to modify) is explained there.

--

Markus

[Former Member · Accepted solution]

Markus,

System has been restarted with the /USERVA 2600 option in the boot.ini. During the boot process, I did verify that the BIOS can see all 8GB of RAM, but the operating system only sees 3.5GB of RAM.

what i did just add /PAE option and it worked and now system showing 8 GB RAM

[boot loader]

timeout=30

default=multi(0)disk(0)rdisk(0)partition(2)\WINNT

[operating systems]

multi(0)disk(0)rdisk(0)partition(2)\WINNT="Windows Server 2003, Enterprise" /noexecute=optout /fastdetect <b>/3GB /USERVA=2600 /PAE</b>

Thanks for help.

Best Regards,

AjitR

[Former Member · Accepted solution]

Hi ,

When you get this kind of error, do not increase the size of the parameter.try runnning the job in background.Most of the times it will work.If not create a message with SAP.

Thanks,

Varada Reddy.

[Former Member · Accepted solution]

this makes no sense.

there is no big difference running reports in dialog or batch concerning memory consumption.

a very detailed documentation on this can be found [here|http://service.sap.com/~sapidb/011000358700006425762006E]

Peter