Zero administration memory management

[Former Member]

Hi,

We are onm windows 2003 server-32Bit, SAP 4.6C, Oracle 9.2.0.5.0, and RAM = 8GB.

We have implemented ZAMM in out server ans also the /3gb&/pae switches in the boot.ini file. the following is the list of parameters in in my instance profile.

rdisp/max_wprun_time = 300000

rsdb/reco_sleep_time = 5

rsdb/reco_trials = 3

abap/heap_area_nondia = 2000000000

abap/heap_area_dia = 2000000000

rsdb/reco_sosw_for_db = OFF

rsdb/reco_add_error_codes = ,3127,3114,+12152

auth/no_check_in_some_cases = Y

login/system_client = 900

rdisp/gui_auto_logout = 0

eu/iwb/help_type = 5

eu/iwb/path_win32 =
nccsapdev\old\en

DIR_TRANS =
nccsapdev\sapmnt\trans

SAPSYSTEMNAME = C11

INSTANCE_NAME = DVEBMGS00

SAPSYSTEM = 00

SAPGLOBALHOST = nccsapdev

rdisp/wp_no_dia = 8

rdisp/wp_no_vb = 2

rdisp/wp_no_vb2 = 1

rdisp/wp_no_enq = 1

rdisp/wp_no_btc = 5

rdisp/wp_no_spo = 2

zcsa/system_language = E

PHYS_MEMSIZE = 5600

zcsa/presentation_buffer_area = 4400128

rdisp/appc_ca_blk_no = 100

rdisp/wp_ca_blk_no = 300

DIR_ROLL = |D:\usr\sap\C11\DVEBMGS00data

DIR_PAGING = |D:\usr\sap\C11\DVEBMGS00data

DIR_DATA = |D:\usr\sap\C11\DVEBMGS00data

|DIR_REORG = |D:\usr\sap\C11\DVEBMGS00data

|DIR_TEMP |.

|DIR_SORTTMP = |D:\usr\sap\C11\DVEBMGS00data

zcsa/installed_languages = ED

install/codepage/appl_server = 1100

ztta/roll_first = 1

ztta/roll_area = 2000000

rdisp/ROLL_SHM = 32768

rdisp/ROLL_MAXFS = 32768

rdisp/PG_SHM = 16384

rdisp/PG_MAXFS = 32768

abap/heap_area_total = 2000000000

ztta/roll_extension = 2000000000

em/initial_size_MB = 5600

em/max_size_MB = 20000

em/address_space_MB = 512

Can someone suggest if these parameters are right as per Zero administration memory management.

Regards

[Former Member]

Hi to alll....

hope you are doing fine.... am very thankful to every one

When i posted this issue to sap market place they gave me this reply...

" Firstly important to set swap size in Windows to 3-4 times physical memory

Also to set the/3Gb and /pae switches in the boot.ini.The master note is 88416.

From the note these are the 32 bit parameters.

As a rule of thumb, use SAP/DB = 70/30 and set the

parameter PHYS_MEMSIZE to approximately 70% of the installed main

physical memory

So set PHYS_MEMSIZE = 5600 as you have 8Gb of memory

set the parameters like this remove any other memory parameters

Profile parameter Standard 32-bit

em/initial_size_MB [PM]

em/max_size_MB 20000

em/address_space_MB 512

ztta/roll_first 1

ztta/roll_area 2000000

ztta/roll_extension 2000000000

abap/heap_area_dia 2000000000

yte

abap/heap_area_nondia 2000000000

abap/heap_area_total 2000000000

rdisp/ROLL_MAXFS [BE] * 100

rdisp/ROLL_SHM [BE] * 100

rdisp/PG_MAXFS 32768

rdisp/PG_SHM [BE] * 50

Central instance with 8 GB main memory

The dialog users work on other application servers. The SAP

instance on the database server does not require much memory. For

this reason, most of the physical memory can be used for the

database.

If you have a setup where the dialogue users work off other application

servers then

You can set PHYS_MEMSIZE = 2400 to give more memory to Oracle."

You all guys are saying to delete the parameters mentioned in note 88416.

Hey plzz dont mind guys i wanna confirm before taking any step because this i wd be doing in my production server ...so plzzz bear with me and help me out resolve it.

waiting for your replies

Regards

[former_member204746]

for the 4th time, delete those parameters from SAP note 88416.

If you are not confident about this, don't do it and leave your system to a bizarre config.

your call.

[Former Member]

Hi,

sorry for the trouble am giving you.....why am confirming this again because if you scroll up to the top a guy named peter tells that we can set a biggger value for parameter PHYS_MEMSIZE.

So i just wanted to confirm that how much value should i set 2700 or 5600.

what do u think is the best ....so that i dont need to replace it again in future and i do not face any problems.

Thanks again !!!!

Regards

[former_member433984]

> what do u think is the best ....so that i dont need

> to replace it again in future and i do not face any

> problems.

I will suggest 5600

However you will definitely have problems after upgrade to next SAP release if you stay on 32-bit Windows. To solve all memory management problems you will need 64-bit platform. For your future release planning please refer to SAP note 996600.

best regards

[Former Member]

Hi,

Thanks for your very kind reply i really appreciate it.

I got it now what you are saying.

How much i should set the value for PHYS_MEMSIZE= ?.

I have a RAM of about 8GB and we are on windows 2003 server 32-bit. if you any more details please let me know.

waiting for your reply....

regards

[former_member204746]

you asked the same question in the same topic and you got an answer... just scroll you way up in your topic.

[Former Member]

Hi,

thanks to all for your replies....

When i consulted SAP they recommended to opt for zero administration memory mangement as i was facing lots of swaps.

They told me to put only the parameters mentioned in not-88416 in my instance profile.

You all are saying to delete those parameters?

Iam getting confused about this

Regards

[former_member433984]

Hello Saifuddin,

do not get you to be confused with swaps... swaps might be always present if you use different components and old buffer entries are replaced with new ones.

ZAMM is aimed to simplify memory management for you, so it sounds reasonable to remove all parameters mentioned in the note 88416 and maintain only one:

PHYS_MEMSIZE

After that you have to watch the system for some time - because some ZAMM values might be optimized by overriding its value (setting corresponding profile parameter).

As Rob mentioned in his post, the first candidates for review are

rdisp/ROLL_SHM

rdisp/PG_SHM

rdisp/ROLL_MAXFS, rdisp/PG_MAXFS are not critical as they do not consume any memory

best regards

[Former Member]

hi,

see below link

http://help.sap.com/saphelp_nw04/helpdata/en/84/7ed387d81f11d188be0000e83539c3/frameset.htm

regards

ajai

[Former Member]

Hi,

Thanks for your reply

1) So how much should i set the PHYS_MEMSIZE am getting confused can you please specify me the value which i should i set.

2) Should i delete the parameters which you have mentioned .

Iam working on windows 2003 server, SAP 4.6C, Oracle-9.2

Waiting for your reply

Regards

[former_member204746]

1) set PHYS_MEMSIZE to 2700.

2) yes, delete them

[Former Member]

Although with ZAMM some memory areas will be automatically set much higher than required. Through monitoring in ST02 you may wish to set:

rdisp/ROLL_MAXFS

rdisp/ROLL_SHM

rdisp/PG_MAXFS

rdisp/PG_SHM

These won't stop ZAMM from working.

[Former Member]

well this depends on the transactions you are using.

Sometimes those values where to small - so it depends on the usage of the system and often can be optimized.

peter

[former_member204746]

read Note 88416 - Zero administration memory management as of 4.0A/ Windows

set PHYS_MEMSIZE to 2700 you should not be able to use more than that, but Peter tells us that you can use a bigger value, check

then, delete all these parameters from your SAP profiles:

em/initial_size_MB

em/max_size_MB

em/address_space_MB

ztta/roll_first

ztta/roll_area

ztta/roll_extension

abap/heap_area_dia

abap/heap_area_nondia

abap/heap_area_total

rdisp/ROLL_MAXFS

rdisp/ROLL_SHM

rdisp/PG_MAXFS

rdisp/PG_SHM