STORAGE_PARAMETERS_WRONG_SET problem

Dear Guru,
When i run one copa report , it showed me below short-dump ,
and i have changed some memory parameters ...
but still unavailable ........
Has someone can guide me how to solve this issue ?
Many thanks !
Message :
Runtime errors STORAGE_PARAMETERS_WRONG_SET
Occurred on 10/20/2008 at 17:28:43
&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 1303069936 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.
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 1303069936. Then reduce the value by 10.000.000 to be on the
safe side.
Then restart the SAP System.
Error analysis
When the program was running, it was established that more
memory was needed than the operating system is able to provide savely.

Yes , i think so . the problem is not a standard SAP report , it is a copa customer report.
But anyway, has a good idea to slove this issue ? Such as change some memory parameters ......
Note : We are using 32bit OS with ibm-x3650 server. Os startup parameters also include "/3GB" and "/PAE".

Similar Messages

STORAGE_PARAMETERS_WRONG_SET

hi,
we are facing runtime error "STORAGE_PARAMETERS_WRONG_SET" in production server( r/3 entprise 4.7 with ms sql 2000, RAM=24 GB). when we run t-code pa30 to get HR data. it generate dump
Runtime Error STORAGE_PARAMETERS_WRONG_SET
Occurred on 18.01.2012 at 12:34:06
&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 1482760560 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.
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 1482760560. Then reduce the value by 10.000.000 to be on the
safe side.
Then restart the SAP System.
while we set
- abap/heap_area_dia = 2000000000
- abap/heap_area_nondia = 2000000000
please guide how we resolve this issue
Regards
khan

Hi Imran,
In case you running the job in foreground set the following parameters
abap/heap_area_dia = 8000000000
abap/heap_area_nondia = 2000000000
abap/heap_area_total = 10000000000
In case you running the job in background set the following parameter
abap/heap_area_dia = 2000000000
abap/heap_area_nondia = 8000000000
abap/heap_area_total = 10000000000
check the shared memory configuration using the following command
sappfpar -check pf=<path of instance profile>
Ensure that there are no errors in above command.
Check the results post above steps.
Regards,
Deepak Kori

SRM 4.00: STORAGE_PARAMETERS_WRONG_SET

Hallo all,
when is running background job: SAP_COLLECTOR_FOR_JOBSTATISTIC,
under ABAP report: RSBPCOLL, I received (ST22):
--- ST22 log message ---
Runtime Error          STORAGE_PARAMETERS_WRONG_SET
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 205855952 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.
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 205855952. 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.
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 ntsap061_SR3_00 on host ntsap061 (wp 0)"
    Version.............. 37
    Error code........... 7
    Error text........... "Warning: EM-Memory exhausted: Workprocess gets PRIV "
    Description.......... " "
    System call.......... " "
    Module............... "emxx.c"
    Line................. 1886
    The error reported by the operating system is:
    Error number..... " "
    Error text....... " "
Database server.......... "NTSAP061"
Database type............ "ORACLE"
Database name............ "SR3"
Database owner........... "SAPSRM"
Character set............ "C"
SAP kernel............... "640"
Created on............... "Feb 25 2008 00:13:43"
Created in............... "NT 5.0 2195 Service Pack 4 x86 MS VC++ 13.10"
Database version......... "OCI_920_SHARE "
Patch level.............. "222"
Patch text............... " "
System environment
    SAP Release.............. "640"
    Application server....... "ntsap061"
    Network address.......... "192.168.22.165"
    Operating system......... "Windows NT"
    Release.................. "5.2"
    Hardware type............ "4x Intel 801586"
    Character length......... 16 Bits
    Pointer length........... 32 Bits
    Work process number...... 0
    Short dump setting....... "full"
    Database server.......... "NTSAP061"
    Database type............ "ORACLE"
    Database name............ "SR3"
    Database owner........... "SAPSRM"
    Character set............ "C"
    SAP kernel............... "640"
    Created on............... "Feb 25 2008 00:13:43"
    Created in............... "NT 5.0 2195 Service Pack 4 x86 MS VC++ 13.10"
    Database version......... "OCI_920_SHARE "
    Patch level.............. "222"
    Patch text............... " "
Supported environment....
Database................. "ORACLE 9.2.0.., ORACLE 10.1.0.., ORACLE
10.2.0.."
SAP database version..... "640"
Operating system......... "Windows NT 5.0, Windows NT 5.1, Windows NT 5.2,
Windows NT 6.0"
Memory usage.............
Roll..................... 8176
EM....................... 462304976
Heap..................... 205855952
Page..................... 16384
MM Used.................. 652141072
MM Free.................. 16014488
SAP Release.............. "640"
Any suggestions are welcome.
Thank you,
Augustin

Hi,
not really software logistics. Anyway, let me try to explain the problem a bit.
Basically you ran out of memory. Next time you run the job everything might be fine again. I would monitor this issue and see if it occurs more often. If it is only a one time occurance, may be there was some excpetional load on the sytem. The termination of the job itself is not a big problem, it will run again next time and collect the data, no need to restart this job manually.
If you get this problem more often you have to tune your memory parameters (or even plug in more memory). memory tuning is one of the hardest things. The easiest way would be to check if you can schedule your batch job to a time where nothting else is running (no dialog users no other batch job). If that is not possible, because you have 24x7 or the batch window is already more than full you have to get into the tuning. As you can see the work process is already in PRIV mode, this should be avoided.
See here what the parameters do http://help.sap.com/saphelp_nw70/helpdata/EN/02/96279d538111d1891b0000e8322f96/frameset.htm
I know it is not the final solution to your answer, but may be it helps. It is somehow unlikely that someone can give you via the forum a set of parameters which will eliminate this issue once and for all.
For Microsoft platforms you set some parameters to "zero memory management configuration", did you do that?
Regards,
Jochen

Sol. Man. dump STORAGE_PARAMETERS_WRONG_SET

Sol. Man. dump STORAGE_PARAMETERS_WRONG_SET
Hi experts,
We are facing the following problem in our SM system - SM 7.0 with EhP1 SPS 06. When certain transactions are started a short dump is generated with error text STORAGE_PARAMETERS_WRONG_SET. This is a part of the dump text:
What happened?
    The current program had to be terminated because of an error when installing the R/3 System.
    The program had already requested 1 382 466 704 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 safely to provide. To avoid a system crash, you must prevent this situation from occurring.
    Last error logged in SAP kernel
    Component............ "EM"
    Place................ "SAP-Server ... on host ... (wp 3)"
    Version.............. 37
    Error code........... 7
    Error text........... "Warning: EM-Memory exhausted: Workprocess gets PRIV "
    Description.......... " "
    System call.......... " "
    Module............... "emxx.c"
    Line................. 1897
    The error reported by the operating system is:
    Error number..... " "
    Error text....... " "
System environment
    SAP-Release 701
    Operating system..... "Windows NT"
    Release.............. "5.2"
    Hardware type........ "2x Intel 80686"
    Character length.... 8 Bits
    Pointer length....... 32 Bits
    Work process number.. 0
    Shortdump setting.... "full"
    Database type..... "ADABAS D"
    Char.set.... "English_United State"
    SAP kernel....... 701
    created (date)... "May 16 2010 22:55:15"
    create on........ "NT 5.2 3790 Service Pack 2 x86 MS VC++ 14.00"
    Database version. "SQLDBC 7.6.0.035 CL 139084 "
    Patch level. 93
    Patch text.. " "
    Database............. "MaxDB 7.6, MaxDB 7.7, MaxDB 7.8"
    SAP database version. 701
    Operating system..... "Windows NT 5.0, Windows NT 5.1, Windows NT 5.2, Windows
     NT 6.0, Windows NT 6.1"
    Memory consumption
    Roll.... 2609360
    EM...... 382578336
    Heap.... 1382466704
    Page.... 57344
    MM Used. 1708544512
    MM Free. 54755528
Edited by: Petar Yordanov on May 28, 2010 11:47 AM

These are some of the profile parameters of the system:
Parameter Name                     System Default Value System Default Value(Unsubst. Form) User-Defined Value
EM/TOTAL_SIZE_MB                   262144                262144
PHYS_MEMSIZE                       3071                  3071                                 2048
abap/NTfmode                       t                     t
abap/aab_log_field_size_limit      1024                  1024
abap/atrasizequota                 30000                 30000
abap/buffersize                    300000                300000
abap/cache_area                    1000000               1000000
abap/heap_area_dia                 2000000000            2000000000
abap/heap_area_nondia              2000000000            2000000000
abap/heap_area_total               2000000000            2000000000
abap/heaplimit                     40000000              40000000
abap/programs                      100                   100
abap/pxa                           shared                shared
abap/pxaclients                    32                    32
abap/restricted_dset_open          yes                   yes
abap/rsyntextln                    180000                180000
abap/rtm_high_water                1038336               1038336
abap/rtm_memory1_size              25000                 25000
abap/rtm_memory2_size              25000                 25000
abap/rtm_memory3_entries           1000                  1000
abap/set_textenv/ignore_errors     0                     0
abap/set_textenv/skip_all          0                     0
abap/shared_objects_size_MB        20                    20
abap/slin_intcheck                 off                   off
abap/string_sharing                on                    on
abap/super                         open                  open
abap/swap_reserve                  20000000              20000000
abap/table_sharing                 on                    on
abap/timeout                       512                   512
abap/unicode_check                 off                   off
abap/use_max_bcd                   0                     0
abap/use_mm                        1                     1
abap/use_paging                    0                     0
abap/warn2error_release            700                   700
em/address_space_MB                512                   512
em/as4/max_free_list               -1                    -1
em/blocksize_KB                    1024                  1024
em/execute_protection              TRUE                  TRUE
em/global_area_MB                  128                   128
em/initial_size_MB                 2048                  2048
em/max_dump_lines                  6291456               6291456
em/max_size_MB                     20000                 20000
ztta/cua_area                      250000                250000
ztta/diag_area                     250000                250000
ztta/dynpro_area                   800000                800000
ztta/hold_data_area                2000                  2000
ztta/max_memreq_MB                 250                   250
ztta/parameter_area                16000                 16000
ztta/roll_area                     2000000               2000000                              3000000
ztta/roll_extension                2000000000            2000000000
ztta/roll_extension_dia            2000000000            $(ztta/roll_extension)               2000000000
ztta/roll_extension_nondia         2000000000            $(ztta/roll_extension)               2000000000
ztta/roll_first                    1                     1
ztta/short_area                    1600000               1600000

Production dump STORAGE_PARAMETERS_WRONG_SET

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

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

STORAGE_PARAMETERS_WRONG_SET (EM-Memory exhausted) error in NW04

Hello experts,
We are having the following issue in our NW04 running on 32-bit Windows & Oracle 9.2 - report execution on the Portal, in BEx, or in RSRT frequently ends with the ST22 error STORAGE_PARAMETERS_WRONG_SET and text as copied below. At the same time our current parameters (also listed below) appear to be in line or even higher with SAP recommendations. Report design has also been optimized as per SAP suggestions and the overall data volume does not appear to be an issue as well. Have anyone experienced anything like that in BW or would have any suggestions? We have already gone through SAP note 779123 and related notes (546361, 552209, 110172) with no success. I have also seen some SDN posts regarding the error message, but so far nothing seems to apply to our case.
Any advice is greatly appreciated!
Profile parameter     Value          Unit
ztta/roll_area     2,000,000.00     Byte
ztta/roll_first     1.00          Byte
ztta/short_area     3,200,000.00     Byte
rdisp/ROLL_SHM     7,500.00          8 kB
rdisp/PG_SHM     7,500.00          8 kB
rdisp/PG_LOCAL     150.00          8 kB
em/initial_size_MB     6,500.00          MB
em/blocksize_KB     1,024.00          kB
em/address_space_MB     512.00     MB
ztta/roll_extension     2,000,683,008.00     Byte
abap/heap_area_dia     2,000,683,008.00     Byte
abap/heap_area_nondia     2,000,683,008.00          Byte
abap/heap_area_total                     2,000,683,008.00          Byte
abap/heaplimit     40,894,464.00          Byte
abap/use_paging     0.00
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 242172048 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.
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 242172048. 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.
r analysis
When the program was running, it was established that more
memory was needed than the operating system is able to provide save
To avoid a system crash, you must prevent this
situation.
           Last error logged in SAP kernel
Component............ "EM"
Place................ "SAP-Server SAP-PBD_PBD_00 on host SAP-PBD (w
Version.............. 37
Error code........... 7
Error text........... "Warning: EM-Memory exhausted: Workprocess gets PRIV'
Description.......... " "
System call.......... " "
Module............... "emxx.c"
Line................. 1886

Hi Sudhir,
These settings need to be done by basis people. Anyhow, you can go to the tcode RZ11 and put in these parameters mentioned in the error message. There will be documentation available for these parameters. Try to see if the defaults are not met for any of these parameters. If you find something strange, report it to the basis. The documentations in this are very helpful. Hope this helps.
Thanks and Regards
Subray Hegde

Runtime Errors STORAGE_PARAMETERS_WRONG_SET

Hi,
My functional team had run customized program in dialog, but after few minutes the error occured as below:-
Runtime Errors STORAGE_PARAMETERS_WRONG_SET
What happened?
The current program had to be terminated because of an
error when installing the R/3 System.
The program had already requested 344148608 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.
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 344148608. Then reduce the value by 10.000.000 to be on the
safe side.
Then restart the SAP System.
SAP Release.............. "620"
Application server.......
Network address..........
Operating system......... "Windows NT"
Release.................. "5.2"
Hardware type............ "8x Intel 80686"
Character length......... 8 Bits
Pointer length........... 32 Bits
Work process number...... 15
Short dump setting....... "full"
Database server..........
Database type............ "MSSQL"
Database name............ "PRD"
Database owner........... "prd"
Supported environment....
Database................. "MSSQL 7.00.699 or higher, MSSQL 8.00.194"
SAP database version..... "640"
Operating system......... "Windows NT 5.0, Windows NT 5.1, Windows NT 5.2"
Then we try run in background job, but error occurred show as below:-
Runtime Errors         TSV_TNEW_PAGE_ALLOC_FAILED
       Occurred on     25.03.2010 at 16:51:02
No storage space available for extending the internal table.
What happened?
You attempted to extend an internal table, but the required space wa
not available.
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 admini
termination messages, especially those beyond their normal deletion
date.
Try to find out (e.g. by targetted data selection) whether the
transaction will run with less main memory.
If there is a temporary bottleneck, execute the transaction again.
If the error persists, ask your system administrator to check the
following profile parameters:
o ztta/roll_area            (1.000.000 - 15.000.000)
       Classic roll area per user and internal mode
       usual amount of roll area per user and internal mode
o ztta/roll_extension       (10.000.000 - 500.000.000)
       Amount of memory per user in extended memory (EM)
o abap/heap_area_total      (100.000.000 - 1.500.000.000)
       Amount of memory (malloc) for all users of an application
       server. If several background processes are running on
       one server, temporary bottlenecks may occur.
       Of course, the amount of memory (in bytes) must also be
       available on the machine (main memory or file system swap
       Caution:
       The operating system must be set up so that there is also
       enough memory for each process. Usually, the maximum addr
       space is too small.
       Ask your hardware manufacturer or your competence center
       about this.
       In this case, consult your hardware vendor
abap/heap_area_dia:        (10.000.000 - 1.000.000.000)
       Restriction of memory allocated to the heap with malloc
       for each dialog process.
Parameters for background processes:
abap/heap_area_nondia:        (10.000.000 - 1.000.000.000)
       Restriction of memory allocated to the heap with malloc
       for each background process.
Other memory-relevant parameters are:
em/initial_size_MB:         (35-1200)
       Extended memory area from which all users of an
       application server can satisfy their memory requirement.
I had check parameter value in RZ10 and below is the result:-
1.abap/heap_area_dia = 2000683008
2.abap/heap_area_dia = 2000683008
3. ztta/roll_area = 2000896
4.ztta/roll_extension   = 2000683008
5.abap/heap_area_total   = 2000683008
6.em/initial_size_MB = 20000
I need advice on this.
Thank you
Regards,
Anang78
Edited by: anang78 on Mar 25, 2010 10:14 AM

Hi,
Your customized program execution is demanding more heap memory. It may be pointing to memory re-configuration.
Please refer the following SAP Notes and compare your exiting memory parameter settings and do the adjustment according to the available RAM.
[SAP Note 425207 - SAP memory management, current parameter ranges|https://service.sap.com/sap/support/notes/425207]
[SAP Note 88416 - Zero administration memory management as of 4.0A/ Windows|https://service.sap.com/sap/support/notes/88416]
Also analyze the execution of that Customized Program, weather the Coding is optimized, weather the program is executing any Expensive SQL Statement or not.
Refer SAP Note 129813, one alternative is mentioned to deal with this memory related issue by activating 3GB feature in your existing Windows OS. Please refer Microsoft KB article 283037 and KB 268363 for the same. You will have to edit your boot.ini file to append /PAE switch.
Regards,
Bhavik G. Shroff

Memory problem in BI query

Hello,
I have some short dumps about memory problems in my BI system (3.5) when I´m consulting a report through BEx. It shows the error STORAGE_PARAMETERS_WRONG_SET, and recommend to increase value of profile parameters:
- abap/heap_area_dia
- abap/heap_area_nondia
But if I check tx ST02 can see threshold of heap memory are never exceed,
Heap memory
Dialog session   kB            2.097.152
                                                                     Nondialog sess. kB            2.097.152
Used             kB                    0
                                 Maximum used     kB            1.069.519
My memory parameters and values:
ztta/roll_area                       2000000
ztta/roll_first     1
ztta/short_area     1600000
rdisp/ROLL_SHM     32768
rdisp/PG_SHM     16384
rdisp/PG_LOCAL     150
em/initial_size_MB     2458
em/blocksize_KB     1024
em/address_space_MB     512
ztta/roll_extension     2000000000
abap/heap_area_dia     2147483647
abap/heap_area_nondia     2147483647
abap/heap_area_total     2000000000
abap/heaplimit     40000000
abap/use_paging     0
What is wrong?? How can I tune it??
Thanks in advise.

It all depends on the OS your SAP is running on... I guess you are on on windows
Then you can get ride of many of theses params
Check note 88416 and delete the following params :
em/initial_size_MB
em/address_space_MB
em/total_size_MB
em/max_size_MB
ztta/roll_first
ztta/roll_area
abap/heaplimit
ztta/roll_extension
abap/heap_area_dia
abap/heap_area_nondia
abap/heap_area_total
rdisp/ROLL_SHM
rdisp/ROLL_MAXFS
rdisp/PG_SHM
rdisp/PG_MAXFS
rdisp/PG_LOCAL
ES/TABLE
Check also this note that is Bex related : 779123 - Memory-related terminations at runtime
Good luck

Problem regarding note 493472 and 362552

Hello All,
I was getting dump for transaction IQ09 ---> "STORAGE_PARAMETERS_WRONG_SET".
I searched in net and found note 493472 (Problems with performance / memory in IQ09) is useful for it.
But after downloading this note by transaction SNOTE, I am getting the status "cannot be implemented".
Can you please let me know the reason behind it.The same problem exists for note 362552.
And also let me know if there are any other alternative OSS notes for this problem.
Regards
Arindam

Hi,
First check in sap service market service.sap.com if the note can be implemented,,
For this, First check the Release, Support Pack(In menu->system->Status)..
If the sap note is valid for that release and support pack(already implemented) given there...Then the note is valid..
Also manually check if the prerequistis exist and are to be implemented...
Hope this helps you
regards
shiva

When i create role, then ---runtime errors: STORAGE_PARAMETERS_WRONG_SET

when i use the tcode:pfcg->change role "role_de"->menu->"from sap menu"->choose one node->save,
then error is display below:
http://picasaweb.google.com/lh/photo/Q-4BpuuXxBVpMpI40S5BBw
http://picasaweb.google.com/lh/photo/uyNkGRn3h6SXvTsMHPlH6g
How can i do it?
Thanks very much!

When i create the menu for the user, then "Runtime Errors STORAGE_PARAMETERS_WRONG_SET".
Please help me!
This is the error message:
Runtime Errors STORAGE_PARAMETERS_WRONG_SET
Date and Time 12.12.2008 10:26:56
Short text
 The system is configured incorrectly.
What happened?
 The current program had to be terminated because of an
 error when installing the R/3 System.
 The program had already requested 741665808 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.
What can you do?
 Note which actions and input led to the error.
 For further help in handling the problem, contact your SAP administrator
 You can use the ABAP dump analysis transaction ST22 to view and manage
 termination messages, in particular for long term reference.
 In the system profile, set the parameters
 -abap/heap_area_dia and
 -abap/heap_area_nondia
 to a maximum of 741665808. To be on the safe side, reduce the value by 10,000,
 000.
 Then restart the SAP system.
Error analysis
 When the program was running, it was established that more
 memory was needed than the operating system is able safely
 to provide. To avoid a system crash, you must prevent this
 situation from occurring.
 Last error logged in SAP kernel
 Component............ "EM"
 Place................ "SAP-Server DDDDDD_GREATWAYCOM_03 on host DDDDDD (wp 0)"
 Version.............. 37
 Error code........... 7
 Error text........... "Warning: EM-Memory exhausted: Workprocess gets PRIV "
 Description.......... " "
 System call.......... " "
 Module............... "emxx.c"
 Line................. 1881
 The error reported by the operating system is:
 Error number..... " "
 Error text....... " "
How to correct the error
 Report the error to the group responsible for installing your
 R/3 System.
System environment
 SAP-Release 700
 Application server... "DDDDDD"
 Network address...... "192.168.99.23"
 Operating system..... "Windows NT"
 Release.............. "5.1"
 Hardware type........ "Intel 801586 (M"
 Character length.... 16 Bits
 Pointer length....... 32 Bits
 Work process number.. 0
 Shortdump setting.... "full"
 Database server... "DDDDDD"
 Database type..... "MSSQL"
 Database name..... "GREATWAYCOM"
 Database user ID.. "ecc"
 Char.set.... "C"
 SAP kernel....... 700
 created (date)... "May 22 2007 00:14:27"
 create on........ "NT 5.0 2195 Service Pack 4 x86 MS VC++ 13.10"
 Database version. "SQL_Server_8.00 "
 Patch level. 111
 Patch text.. " "
 Database............. "MSSQL 7.00.699 or higher, MSSQL 8.00.194"
 SAP database version. 700
 Operating system..... "Windows NT 5.0, Windows NT 5.1, Windows NT 5.2, Windows
 NT 6.0"
 Memory consumption
 Roll.... 1609456
 EM...... 447355872
 Heap.... 313508640
 Page.... 16384
 MM Used. 734465040
 MM Free. 27458464
User and Transaction
 Client.............. 001
 User................ "ADMIN"
 Language Key........ "E"
 Transaction......... " "
 Program............. "SAPLSMNU_NEW"
 Screen.............. "SAPMSSY1 3004"
 Screen Line......... 2
 Information on caller of Remote Function Call (RFC):
 System.............. "GREATWAYCOM"
 Database Release.... 700
 Kernel Release...... 700
 Connection Type..... 3 (2=R/2, 3=ABAP System, E=Ext., R=Reg. Ext.)
 Call Type........... "synchron and transactional (emode 0, imode 0)"
 Inbound TID.........." "
 Inbound Queue Name..." "
 Outbound TID........."C0A8001609E04941C90A0045"
 Outbound Queue Name.." "
 Client.............. 001
 User................ "ADMIN"
 Transaction......... " "
 Call Program........."SAPLERFC"
 Function Module..... "ARFC_DEST_SHIP"
 Call Destination.... "NONE"
 Source Server....... "DDDDDD_GREATWAYCOM_03"
 Source IP Address... "192.168.99.23"
 Additional information on RFC logon:
 Trusted Relationship " "
 Logon Return Code... 0
 Trusted Return Code. 0
 Note: For releases < 4.0, information on the RFC caller are often
 only partially available.
Information on where terminated
 Termination occurred in the ABAP program "SAPLSMNU_NEW" - in
 "READ_MENU_HIERARCHY_FAST".
 The main program was "SAPMSSY1 ".
 In the source code you have the termination point in line 1131
 of the (Include) program "LSMNU_NEWF01".
Source Code Extract
Line SourceCde
1101 L_LIST_OF_TEXTS.
1102 PERFORM READ_HIERARCHY_INCLUDING_REFS
1103 TABLES L_LIST_OF_NODES
1104 L_LIST_OF_REFS
1105 L_LIST_OF_TEXTS
1106 L_VISITED_TREES
1107 USING P_TREE_ID
1108 SPACE
1109 L_MENU_LEVEL
1110 SPACE.
1111
1112 * get total number of nodes
1113 DESCRIBE TABLE L_LIST_OF_NODES LINES L_NUM_OF_NODES.
1114
1115 L_RATIO = L_NUM_OF_ALL_NODES / L_NUM_OF_NODES.
Thanks for your help!

Parameter error-STORAGE_PARAMETERS_WRONG_SET.

Hi all,
We are continuously facing abap dump STORAGE_PARAMETERS_WRONG_SET.
The current program had to be terminated because of an
error when installing the R/3 System.
The program had already requested 972175952 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.
Set the system profile parameters
-abap/heap_area_dia und
-abap/heap_area_nondia
to 972175952 maximum. For security, reduce the value by 10.000.000
Now shall i go ahead and change the parameter values and let me know the recommended
parameter values for my prod server as no issue arise in future.
Our System environment:
46C,oracle 10.2.0.2.0,win2003_64bit
Thanks in advance,
Kutty

Hi,
Check why program is requesting so much memory. If it is Z program then check with your ABAP guy if there is any problem in the code. otherwise increase the parameters as suggested in dump details.
Thanks
Sunny

Dump : storage_parameters_wrong_set

I am currently working on a new BI system.when i am trying to replicate datsources from r/3 the system gives me dump and it reads.
Runtime error:storage_parameters_wrong_set.
Kindly provide me with OSS note or any solution to this error.

Thanks for the reply.well i am have activated Resource and Program Management (APCO_XAPPS_RPM)datasources in r/3 and am trying to replicate these datasources in BI.The dump analysis is as follows.
Runtime Errors STORAGE_PARAMETERS_WRONG_SET
Date and Time 12.10.2007 13:22:14
Short text
 The system is configured incorrectly.
What happened?
 The current program had to be terminated because of an
 error when installing the R/3 System.
 The program had already requested 777670496 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.
What can you do?
 Note which actions and input led to the error.
 For further help in handling the problem, contact your SAP administrator
 You can use the ABAP dump analysis transaction ST22 to view and manage
 termination messages, in particular for long term reference.
 In the system profile, set the parameters
 -abap/heap_area_dia and
 -abap/heap_area_nondia
 to a maximum of 777670496. To be on the safe side, reduce the value by 10,000,
 000.
 Then restart the SAP system.
Error analysis
 When the program was running, it was established that more
 memory was needed than the operating system is able safely
 to provide. To avoid a system crash, you must prevent this
 situation from occurring.

About STORAGE_PARAMETERS_WRONG_SET

Hi Experts ,
When i execute ke24 the system popup the error message :
Runtime errors STORAGE_PARAMETERS_WRONG_SET
Occurred on 07/25/2007 at 17:32:11
&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 1256707392 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.
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 1256707392. Then reduce the value by 10.000.000 to be on the
..
In this case is it reduce the parameter value in abap/heap_area_nondia can solve this problem ??
Our Server's memory is 12GB .. and i think the memory is enough ...
Many thanks !!!

nothing to do with RAM.. there is not enough free space in virtual address space for heap - see notes
<a href="https://service.sap.com/sap/support/notes/110172">110172</a>
<a href="https://service.sap.com/sap/support/notes/546361">546361</a>
<a href="https://service.sap.com/sap/support/notes/552209">552209</a>
if not help this might be case for 64bit migration - [url=https://service.sap.com/sap/support/notes/996600]996600[/url]

STORAGE_PARAMETERS_WRONG_SET........for BI

Hello
If i genarate report up to 1 month it coming correctly. but if we put more than 1 month ,after report generation......if click on drill down for column. system is gives dump ......
STORAGE_PARAMETERS_WRONG_SET.
The current program had to be terminated because of an
error when installing the R/3 System.
The program had already requested 181180496 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.
Note which actions and input led to the error.
For further help in handling the problem, contact your SAP administrator
You can use the ABAP dump analysis transaction ST22 to view and manage
termination messages, in particular for long term reference.
In the system profile, set the parameters
-abap/heap_area_dia and
-abap/heap_area_nondia
to a maximum of 181180496. To be on the safe side, reduce the value by 10,000,
000.
Then restart the SAP system.
i have checked all threads related to this.......... did changes but no fruit.
regards
sachin

Hi,
this is a memory-related termination which occurs when the requested data is larger in size than the available memory.
Most probably a parameter is set too low.
For more info, you can read oss-note 779123.
Check with your BC-guy/grrl if you need to change the parameter settings.

STORAGE_PARAMETERS_WRONG_SET. when uploding catalogues ( not enough memory)

When a member of our SRM team tries to upload an xml catalogue of size
92mb the process hangs and we get a short dump
STORAGE_PARAMETERS_WRONG_SET. This does not happen when we upload
smaller catalogues. I changed the recommended parameters
abap/heap_area_dia and abap/heap_area_nondia i changed these to a lower
number and then to 0 as per the dump info. We still get this error for
larger catalogues. Any ideas, i looked at various notes but they seem to refer to reports and not catalogues.
Any ideas

may be notes 110172, 552209, 546361 would be helpful for you
you do not need to change "abap/heap_area_dia and abap/heap_area_nondia", the problem is limited virtual address space on 32-bit platforms. You can try to extend the address space as described in the notes above or reduce some SAP SHM (for example abap/buffersize, rdisp/ROLL_SHM, rdisp/PG_SHM etc.)
as long term solution you need 64-bit platform (note 996600).
or you can simply add 64-bit dialog instance to your landscape and leave the transaction run there.

STORAGE_PARAMETERS_WRONG_SET problem

Similar Messages

Maybe you are looking for