Memory Low

[Former Member]

Hello All,

All our consultants are facing problem in login or while printing the sales order, billing document. It is throwing an error "STORAGE_PARAMETERS_WRONG_SET".

Our operating system is 32-bit and windows server 2003.

Previously we had 4GB of RAM and now we have upgraded it to 16GB. SInce then, it hits an error MEMORY LOW.

Following are the profile parameters on our SAP:

em/address_space_MB 4092

abap/heap_area_nondia 2000000000

abap/heap_area_dia 2000000000

ztta/roll_area 3000320

abap/buffersize 300000

rdisp/max_wprun_time 1800

ztta/diag_area 500000

rsdb/ntab/ftabsize 48000

rsdb/ntab/entrycount 36000

login/no_automatic_user_sapstar 0

SAPSYSTEMNAME DEV

SAPGLOBALHOST development

SAPSYSTEM 00

INSTANCE_NAME DVEBMGS00

DIR_CT_RUN $(DIR_EXE_ROOT)\$(OS_UNICODE)\NTI386

DIR_EXECUTABLE $(DIR_INSTANCE)\exe

PHYS_MEMSIZE 4096

rdisp/wp_no_dia 8

rdisp/wp_no_btc 3

icm/server_port_0 PROT=HTTP,PORT=80$$

ms/server_port_0 PROT=HTTP,PORT=81$$

rdisp/wp_no_enq 1

rdisp/wp_no_vb 2

rdisp/wp_no_vb2 1

rdisp/wp_no_spo 1

DIR_CLIENT_ORAHOME $(DIR_EXECUTABLE)

Request you to recommend me on this.. Shall i have to set more parameters.??

Thanks,

Disha Gupta

[Former Member]

Thread was quite helpful to me.. Markus helped me a lot in this.

[markus_doehr2]

"STORAGE_PARAMETERS_WRONG_SET".

> Our operating system is 32-bit and windows server 2003.

> Previously we had 4GB of RAM and now we have upgraded it to 16GB. SInce then, it hits an error MEMORY LOW.

On a 32bit platform one process can only allocate a maximum of 2 GB (3 GB) RAM bar any available memory, this is an architectural limitation by the 32bit implementation.

You can try to adapt the operating system according to

Note 110172 - Windows: Transactions with large memory requirements

but in medium term I can just highly suggest upgrading to 64bit.

Markus

[former_member189546]

Hello,

Check note 88416 Zero administration memory management as of 4.0A/

Also make sure you have /3Gb and /pae switches enabled in boot.ini

reboot if you enter them

regards,

John Feely

[Former Member]

Hi John,

Would you please tell me how to enable /3Gb and /pae switches in boot.ini ....

Please guide me and tell me the steps for activating both switches..

Thanks & Regards

Disha

[markus_doehr2]

Please read the note I mentioned in my post, everything is described in it.

Markus

[Former Member]

HI Markus,

Thanks for your help..

Please tell,

1. following steps right for activating /3GB switch:????

[boot loader]

timeout=30

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

operating systems

multi(0)disk(0)rdisk(0)partition(2)\WINDOWS="Windows Server 2003, Standard x64 Edition" / fastdetect /noexecute=optout /3GB

2. Is it neccessary to enable /pae switch??? or if yes, is the following command right ?

[boot loader]

timeout=30

default=multi(0)disk(0)rdisk(0)partition(1)\WINDOWS

operating systems

multi(0)disk(0)rdisk(0)partition(1)\WINDOWS="Windows Server 2003, Standard x64 Edition" / fastdetect /noexecute=optout /3GB /PAE

3. After enabling both switches manually, i have to implement the note 110172 ??

Thanks

Disha

[markus_doehr2]

This switch is for 32bit system, your system seems to be on 64bit already!

Markus

[Former Member]

Hi Marcus,

I was asking you about the command as this is not enabled in my system.

Our is 32-bit only.

I was asking, shall i have to update either 1st point or 2nd point mentioned in my previous thread to boot.ini ???

Thanks

Disha

[markus_doehr2]

> I was asking you about the command as this is not enabled in my system.

> Our is 32-bit only.

Your system says:

"Windows Server 2003, Standard x64 Edition"

And "x64" is a synonym for x86_64 - which is 64bit - so your operating system is apparently not a 32bit system.

Please post the first 20 lines of a developer trace (dev_w0).

Markus

[Former Member]

Hello Markus,

Log of dev_w0 is as :

-

---

trc file: "dev_w0", trc level: 1, release: "700"

-

---

*

• ACTIVE TRACE LEVEL 1

• ACTIVE TRACE COMPONENTS all, MJ

*

M sysno 00

M sid DEV

M systemid 560 (PC with Windows NT)

M relno 7000

M patchlevel 0

M patchno 254

M intno 20050900

M make: multithreaded, Unicode, optimized

M pid 4752

M

M

M Sat Jan 22 09:10:03 2011

M kernel runs with dp version 244000(ext=110000) (@(#) DPLIB-INT-VERSION-244000-UC)

M length of sys_adm_ext is 576 bytes

M ***LOG Q0Q=> tskh_init, WPStart (Workproc 0 4752) [dpxxdisp.c 1349]

I MtxInit: 30000 0 0

M DpSysAdmExtCreate: ABAP is active

M DpSysAdmExtCreate: VMC (JAVA VM in WP) is not active

M DpShMCreate: sizeof(wp_adm) 27264 (1704)

M DpShMCreate: sizeof(tm_adm) 4415616 (21968)

M DpShMCreate: sizeof(wp_ca_adm) 24064 (80)

M DpShMCreate: sizeof(appc_ca_adm) 8000 (80)

M DpCommTableSize: max/headSize/ftSize/tableSize=500/8/528056/528064

M DpShMCreate: sizeof(comm_adm) 528064 (1048)

M DpSlockTableSize: max/headSize/ftSize/fiSize/tableSize=0/0/0/0/0

M DpShMCreate: sizeof(slock_adm) 0 (96)

M DpFileTableSize: max/headSize/ftSize/tableSize=0/0/0/0

M DpShMCreate: sizeof(file_adm) 0 (72)

M DpShMCreate: sizeof(vmc_adm) 0 (1544)

M DpShMCreate: sizeof(wall_adm) (38456/34360/64/184)

M DpShMCreate: sizeof(gw_adm) 48

M DpShMCreate: SHM_DP_ADM_KEY (addr: 07930040, size: 5084560)

M DpShMCreate: allocated sys_adm at 07930040

M DpShMCreate: allocated wp_adm at 07932178

M DpShMCreate: allocated tm_adm_list at 07938BF8

M DpShMCreate: allocated tm_adm at 07938C28

M DpShMCreate: allocated wp_ca_adm at 07D6ECA8

M DpShMCreate: allocated appc_ca_adm at 07D74AA8

M DpShMCreate: allocated comm_adm at 07D769E8

M DpShMCreate: system runs without slock table

M DpShMCreate: system runs without file table

M DpShMCreate: allocated vmc_adm_list at 07DF78A8

M DpShMCreate: allocated gw_adm at 07DF78E8

M DpShMCreate: system runs without vmc_adm

M DpShMCreate: allocated ca_info at 07DF7918

M DpShMCreate: allocated wall_adm at 07DF7920

M rdisp/queue_size_check_value : -> off

M ThTaskStatus: rdisp/reset_online_during_debug 0

X EmInit: MmSetImplementation( 2 ).

X MM global diagnostic options set: 0

X <ES> client 0 initializing ....

X Using implementation view

X <EsNT> Using memory model view.

M <EsNT> Memory Reset disabled as NT default

X ES initialized.

X mm.dump: set maximum dump mem to 96 MB

mine is 32-bit OS..

Operating System= Windows NT

Machine Type= 8x Intel 8

Thanks

Disha

[markus_doehr2]

Your SAP kernel is 32bit, yes, but it appears, according to the entries in boot.ini, that the OS is 64bit. And all 4-core CPUs support a 64bit OS.

So I HIGHLY suggest, instead of fiddling with a /3GB option and /PAE install a 64bit OS - and a 64bit SAP kernel.

If your OS is already 64bit that kernel boot option will not have any effect.

Markus

[Former Member]

Thanks Markus for your help..

I'll upgrade my OS to 64-bit as we went through lots of problem after enabling /3GB switch.

Thanks

Disha

[Former Member]

After RAM upgrade, Change value of PHYS_MEMSIZE.

If you have central system dedicated to One SAP instance then you can set this parameter at 60% of total RAM.

(40 % for Database).

Regards,

Nirav Shah.

Edited by: Nirav Shah on Jan 9, 2011 5:17 AM

[Former Member]

Hi Nirav,

Before upgrading RAM, it was 1000 but now i have changed it to 4096. But still error persists in the system. I have two servers, one is DEV and other is PRD.

Suggest me something else.

Thanks

Disha