storage_parameters_wrong_set

[Former Member]

Hi all,

We are actually processing an internal table having 20000 records and 300 columns in the quality system. The values of the various memory parameters are:

ztta/max_memreq_MB 250

ztta/parameter_area 32000

ztta/roll_area 2000000

ztta/roll_extension 2000000000

ztta/roll_extension_dia 2000000000

ztta/roll_extension_nondia 2000000000

ztta/roll_first 1

ztta/short_area 3200000

em/blocksize_KB 1024

em/global_area_MB 128

em/initial_size_MB 2560

em/max_size_MB 20000

abap/heap_area_dia 2000000000

abap/heap_area_nondia 2000000000

abap/heap_area_total 2000000000

abap/heaplimit 40000000

We could run the same report in the development system both in foreground and background and the parameter settings in development and quality systems are same. But whenever we run the report in the quality system it goes into a short dump throwing the error "<b>storage_parameters_wrong_set</b>". When we analyse in ST02 we could see the report is consuming just one third of the extended memory and then goes to PRIV mode and consumes just 300MB of private memory. What could be the cause of error??? Please help me out.

[former_member433984]

first try to activate /3GB option in boot.ini, as second step (if first will not help) try to set

rdisp/ROLL_SHM = 6000

rdisp/PG_SHM = 6000

however the long term solution will be to use 64-bit platform

[Former Member]

Hello,

Eric is right to ask for all these information as many memory parameters settings change with version/OS/database

From the list I see , the one parameter I do not like that much is the em/global_area_MB 128

Would you like to increase it to 255 and if you have problems again to 512 and see what happens

I hope this helps

Andreas

[former_member433984]

> Hello,

>

> Eric is right to ask for all these information as

> many memory parameters settings change with

> version/OS/database

>

> From the list I see , the one parameter I do not like

> that much is the em/global_area_MB 128

>

> Would you like to increase it to 255 and if you have

> problems again to 512 and see what happens

>

> I hope this helps

>

> Andreas

... and do not increase em/global_area_MB - it will "eat" useful peace of memory in EM segment - leave it as it is

[former_member204746]

what is your SAP/Os/DB versions?

how much RAM installed?

how much pagefile/swap configured?

[Former Member]

Hi Eric,

Both the development and quality systems (both ECC 5.0) run on oracle 9i database and OS is windows NT.

The RAM size is 4GB for both the systems.

Swap size is 13GB for both the systems.

Thanks.

[former_member204746]

if you are using Windows NT, it would make thing easier if you would follow Note 88416 - Zero administration memory management as of 4.0A/ Windows.

you basically set one parameter called PHYS_MEMSIZE (I would set it at 2700).

you must also delete about 10 parameters from your SAP profiles, delete those that appear in the table in the SAP note.

This will let SAP decide how to distribute memory.

[Former Member]

Hi Eric,

Thanks for your quick response.

In our case the PHYS_MEMSIZE parameter stands at 2150 MB for the development system and 2560 MB for the quality system.

Still the error persists.

Thanks.

[former_member204746]

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