STORAGE_PARAMETERS_WRONG_SET Error

When ever i try to load data through BW i am getting the following error:
<b> STORAGE_PARAMETERS_WRONG_SET</b>
My values are
abap/heap_area_nondia--275864784
abap/heap_area_dia--275864784
But i also changed the profile parameters as mentioned, but still i am getting the error,but the value for abap/heap_area_nondia is different.
Pls help
<b>
Runtime Errors         STORAGE_PARAMETERS_WRONG_SET
Date and Time          27.06.2007 13:11:54
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 285864784 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 285864784. To be on the safe side, reduce the value by 10,000,
000.
|    Then restart the SAP system.   </b>

Hi Balaji
Kindly go through SAP Note :44528
Just check the parameter settings mentioned in that and do accordingly.
For sure not only Heap memory you need to have look at roll and Extended memory.
As First Roll memory, then extended later the Heap will be used by SAP.
So kindly have a look at Roll and extended memory values too.
Thanks & Regards
Vivek

Similar Messages

Getting this error: STORAGE_PARAMETERS_WRONG_SET

Hello Experts,
We keep on getting the said runtime error when we run a certain report in our production server. Please help as to how can this be solved. Thank you guys and take care!

Check OSS note: 72765 STORAGE_PARAMETERS_WRONG_SET with report execution
Cause and prerequisites
The report called up processes so much data, that the memory requirement exceeds the memory actually available.
Reason: for the direct output of the report following selection, the data is transferred via the memory.
Solution
Execute the report in two steps. Create an extract first, and output this extract later direct

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

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

Runtime error of STORAGE_PARAMETERS_WRONG_SET

Hi all,
I faced this runtime error when want to pull out high volume of data from cluster and transparent table to list down the output by using write statement. Do you have solution or recommendation to avoid this happen?
Thanks.

> Please lemme know the Recommended values of the parameters for this runtime error. Frequently I am getting this error.
This is a very common problem on 32bit systems.
No matter how much physical memory you have, the per-process limit is 2 GB. If you e. g. select a huge amount of data all buffers and the data in the process may reach the 32bit limit.
Therefore it's no more recommended to install 32bit systems. It can be VERY cumbersome to tune such systems and keep them running.
You need to understand how the memory is used to tune and configure it, therefor I recommend reading the following notes:
Note 546361 - FAQ: Storage problems on NT/Windows 2000
Note 552209 - Maximum memory utilization for processes on NT/Win2000
Note 110172 - Windows: Transactions with large memory requirements
Markus

Runtime Error *STORAGE_PARAMETERS_WRONG_SET*

Hi All,
I want to get open items from BSID table. I used the Function module BAPI_AR_ACC_GETOPENITEMS.It is populated in an internal table ITAB1 which is of BAPI3007_2 structure. from the int table itab1 i want to get open items with checking with the cheque number(ZUONR) in BSID table and those items having the credit entry(SHKZG) i.e(credit entry = H)
and also i want to print the amounts(DMBTR) of this above said open items. because i am using another internal table ITAB for printing those values which is given in ALV function module, when i give this amount it is showing error..
Thanks & Regards
Ajeeth ram.s
Edited by: Ajeeth ram.s on Jan 14, 2011 3:30 PM

Usually this message occurs when no sufficient memory available for the process. Try to reduce the amount of data to be processed or adjust the memory settings if possible.
BR,
Robert

Short Dump error - Please Read on (Error Attached)

Hello,
while loading Master Data from R/3 to BI 7.0, all Data Packets loaded successfully, but at the end I got the following error. Can somone pls help me understand this error and what action needs to be taken.
Thanks.
SD
Runtime Errors         STORAGE_PARAMETERS_WRONG_SET
Date and Time          14.05.2008 15:27:00
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 1452765184 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 1452765184. To be on the safe side, reduce the value by 10,000,
     000.
     Then restart the SAP system.

This problem is based in your parameter settings (RZ11).
In this case parameters
-abap/heap_area_dia and
-abap/heap_area_nondia
have a max value which is too low to load your data.
Follow the instructions of the shortdump (probably a BC-guy will do this):
In the system profile, set the parameters
-abap/heap_area_dia and
-abap/heap_area_nondia
to a maximum of 1452765184. To be on the safe side, reduce the value by 10,000,
000.

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

RFC error when sending logon data

Hi;
We cannot configure the STMS of our development system. When we try to
configure it, system gives an error message: Errors during distribution
of tp configuration; TMS Alert Viewers tells us
RFC_COMMUNICATION_FAILURE: RFC communications error with
system/destination TMSADM-FKT.DOMAIN_FKT RFC error when sending logon
data and READ_PROFILE_FAILED:File
erptest\sapmnt\trans\bin\TPPARAM
could not be opened for reading (No such file or directory).
Is there any advise for solution?
Best regards
Noyan
PS: Please find the profiles below:
START:
#.*       Start profile START_DVEBMGS00_erptest                                                                                *
#.*       Version                 = 000006                                                                                *
#.*       Generated by user = BASIS                                                                                *
#.*       Generated on = 30.12.2010 , 15:40:55                                                                                *
generated by R3SETUP
SAPSYSTEMNAME = FKT
INSTANCE_NAME = DVEBMGS00
SAPSYSTEM = 00
SAPGLOBALHOST = erptest
DIR_PROFILE = D:\usr\sap\FKT\SYS\profile
start database
#_DB = strdbs.cmd
#Start_Program_02 = immediate $(DIR_EXECUTABLE)\$(_DB) FKT
start message server
#_MS = msg_server.exe
Start_Program_03 = local $(DIR_EXECUTABLE)\$(_MS) pf=$(DIR_PROFILE)\FKT_DVEBMGS00_erptest
Start IGS
Start_Program_05 = local $(DIR_EXECUTABLE)$(DIR_SEP)igswd$(FT_EXE) -mode=profile pf=$(DIR_PROFILE)$(DIR_SEP)FKT_DVEBMGS00_erptest
start application server
#_DW = disp+work.exe
#Start_Program_04 = local $(DIR_EXECUTABLE)\$(_DW) pf=$(DIR_PROFILE)\FKT_DVEBMGS
General parameters for starting the system
#parameter created                          by: BASIS        24.12.2007 23:53:27
#SAPSYSTEM = 00
#parameter created                          by: BASIS        24.12.2007 23:53:27
#SAPSYSTEMNAME = FKT
#parameter created                          by: BASIS        24.12.2007 23:53:27
#INSTANCE_NAME = DVEBMGS00
#parameter created                          by: BASIS        24.12.2007 23:53:27
DIR_PROFILE = D:\usr\sap\FKT\SYS\profile
#parameter created                          by: BASIS        24.12.2007 23:53:27
#SAPGLOBALHOST = erptest
Start database
#parameter created                          by: BASIS        24.12.2007 23:53:27
_DB = strdbs.cmd
#parameter created                          by: BASIS        24.12.2007 23:53:27
Start_Program_01 = immediate $(DIR_EXECUTABLE)\$(_DB) $(SAPSYSTEMNAME)
Start message server
#parameter created                          by: BASIS        24.12.2007 23:53:27
MS = msgserver.exe
#parameter created                          by: BASIS        24.12.2007 23:53:27
Start_Program_02 = local $(DIR_EXECUTABLE)\$(_MS) pf=$(DIR_PROFILE)\FKT_DVEBMGS00_erptest
Start applications server
#parameter created                          by: BASIS        24.12.2007 23:53:27
_DW = disp+work.exe
#parameter created                          by: BASIS        24.12.2007 23:53:27
Start_Program_03 = local $(DIR_EXECUTABLE)\$(_DW) pf=$(DIR_PROFILE)\FKT_DVEBMGS00_erptest
DEFAULT:
SAPDBHOST = ERPTEST
dbms/type = mss
dbs/mss/server = ERPTEST
dbs/mss/dbname = FKT
dbs/mss/schema = fkt
SAPSYSTEMNAME = FKT
SAPGLOBALHOST = erptest
SAPFQDN = tr.delta.is
SAPLOCALHOSTFULL = $(SAPLOCALHOST).$(SAPFQDN)
SAPDBHOST = erptest
SAPTRANSHOST = erptest
DIR_TRANS =
$(SAPTRANSHOST)\sapmnt\trans
#DIR_TRANS = D:\usr\sap\trans
DIR_PROFILE = D:\usr\sap\FKT\SYS\profile
SAP Message Server for ABAP
rdisp/mshost = erptest
rdisp/sna_gateway = erptest
rdisp/sna_gw_service = sapgw00
rdisp/vbname = erptest_FKT_00
rdisp/enqname = erptest_FKT_00
rdisp/btcname = erptest_FKT_00
rdisp/msserv = sapmsFKT
rdisp/msserv_internal = 3900
rdisp/bufrefmode = sendoff,exeauto
login/system_client = 200
#GUVENLIK PARAMETRELERI
login/password_expiration_time = 90
login/min_password_lng = 6
#parameter created                          by: BASIS        25.03.2004 08:41:25
rdisp/gui_auto_logout = 10800
#parameter created                          by: BASIS        25.03.2004 08:37:47
#old_value: 3                                 changed: BASIS 25.03.2004 08:42:38
login/fails_to_user_lock = 6
#validasyon geregi, g#venligi artirma ama#i - check active but no check for SRF
#parameter created                          by: BASIS        16.06.2007 17:35:41
#old_value: 2
#changed: BASIS         14.05.2008 15:24:55
auth/rfc_authority_check = 1
#otomatik unlocki iptal eder
#parameter created                          by: BASIS        10.11.2006 17:47:15
login/failed_user_auto_unlock = 0
#AUDIT PARAMETRELER?
#old_value:                                   changed: BASIS 20.04.2005 17:13:37
rsau/max_diskspace/per_day = 1996800000
#old_value: 1000000000                        changed: BASIS 20.04.2005 17:17:01
#old_value: 0                                 changed: BASIS 20.04.2005 17:19:12
rsau/max_diskspace/local = 2048000000
#old_value: 2000000000                        changed: BASIS 28.03.2005 23:17:11
#old_value: 2                                 changed: BASIS 29.03.2005 12:09:14
#old_value: 0                                 changed: BASIS 20.04.2005 17:13:37
rsau/max_diskspace/per_file = 665600000
rsau/enable = 1
rsau/local/file = D:\usr\sap\FKT\DVEBMGS00\log\++++++++######..AUD
rsau/selection_slots = 12
#rec/client = ALL
DIR_AUDIT = D:\usr\sap\FKT\DVEBMGS00\log
FN_AUDIT = ++++++++######..AUD
#DIL PARAMETRELERI
#Turkish codepage settings
abap/import_char_conversion = 0
install/codepage/db/non_transp = 1610
install/codepage/db/transp = 1610
zcsa/installed_languages = DET
#zcsa/system_language = E
zcsa/system_language = T
zcsa/second_language = E
install/codepage/appl_server = 1610
#OS dependent
abap/locale_ctype = Turkish_turkey.28599
#DIR_PUT = D:\usr\sap\FKQ\upg\abap
   *** UPGRADE EXTENSIONS (RELEASE "701") ***
#rdisp/msserv_internal = 3900
#system/type = ABAP
INSTANCE:
SAPSYSTEMNAME = FKT
SAPGLOBALHOST = erptest
SAPSYSTEM = 00
INSTANCE_NAME = DVEBMGS00
DIR_CT_RUN = $(DIR_EXE_ROOT)\$(OS_UNICODE)\NTAMD64
DIR_EXECUTABLE = $(DIR_INSTANCE)\exe
icm/server_port_0 = PROT=HTTP,PORT=80$$
SAP Message Server parameters are set in the DEFAULT.PFL
ms/server_port_0 = PROT=HTTP,PORT=81$$
#rdisp/wp_no_dia = 10
#rdisp/wp_no_btc = 3
#rdisp/wp_no_enq = 1
#rdisp/wp_no_vb = 1
#rdisp/wp_no_vb2 = 1
#disp/wp_no_spo = 1
rdisp/wp_no_dia = 12
rdisp/wp_no_vb = 3
rdisp/wp_no_vb2 = 0
rdisp/wp_no_enq = 1
rdisp/wp_no_btc = 3
rdisp/wp_no_spo = 1
#PERFORMANS PARAMETRELERI
#parameter created                          by: SAP*         08.08.2001 10:30:18
abap/fieldexit = yes
#parameter created                          by: ALPER        13.10.2000 18:24:16
install/collate/active = 1
rdisp/max_wprun_time = 25000
MEMORY_NO_MORE_PAGING dump nedeniyle
#parameter created                          by: BASIS        27.12.2006 17:00:22
rdisp/PG_MAXFS = 262144
abap/heap_area_nondia = 2000000000
rdisp/PG_SHM = 16384
rdisp/ROLL_SHM = 32768
#'STORAGE_PARAMETERS_WRONG_SET' or 'TSV_TNEW_PAGE_ALLOC_FAILED'
#Note 552209 - Maximum memory utilization for processes on NT/Win2000
#parameter created                          by: BASIS        30.10.2007 10:57:24
#abap/heap_area_nondia = 50000
#parameter created                          by: BASIS        30.10.2007 10:58:54
#rdisp/PG_SHM = 0
#parameter created                          by: BASIS        30.10.2007 10:58:27
#rdisp/ROLL_SHM = 625
#EWA report 12.2007
#parameter created                          by: BASIS        03.01.2008 19:49:57
dbs/mss/stats_on = 1
#EWA report 12.2007
#parameter created                          by: BASIS        03.01.2008 19:49:33
dbs/oledb/stats_on = 1
#EWA report 12.2007
#parameter created                          by: BASIS        03.01.2008 19:48:23
dbs/oledb/add_procs = 8
#EWA report 12.2007
#parameter created                          by: BASIS        03.01.2008 19:47:29
rsdb/esm/max_objects = 2000
#EWA report 12.2007
#parameter created                          by: BASIS        03.01.2008 19:47:03
rsdb/otr/buffersize_kb = 4096
#EWA report 12.2007
#parameter created                          by: BASIS        03.01.2008 19:46:21
rsdb/esm/buffersize_kb = 4096
Eyl#l 2006 EWA raporu
#parameter created                          by: BASIS        24.11.2006 13:18:14
ztta/parameter_area = 16000
Eyl#l 2006 EWA raporu
#parameter created                          by: BASIS        24.11.2006 13:16:43
enque/table_size = 10000
Eyl#l 2006 EWA raporu
#parameter created                          by: BASIS        24.11.2006 13:16:20
gw/max_sys = 2000
#Eyl#l 2006 EWA raporu
#parameter created                          by: BASIS        24.11.2006 13:16:01
gw/max_overflow_size = 25000000
#Eyl#l 2006 EWA raporu
#parameter created                          by: BASIS        24.11.2006 13:15:19
rdisp/max_comm_entries = 2000
Eyl#l 2006 EWA raporu
#parameter created                          by: BASIS        24.11.2006 13:14:48
rdisp/tm_max_no = 2000
Eyl#l 2006 EWA raporu
#parameter created                          by: BASIS        24.11.2006 13:14:20
gw/max_conn = 2000
Eyl#l 2006 EWA raporu
#parameter created                          by: BASIS        24.11.2006 13:13:42
rdisp/max_arq = 2000
#Eyl#l 2006 EWA raporu
#parameter created                          by: BASIS        24.11.2006 13:12:57
ztta/roll_area = 3500000
#parameter created                          by: BASIS        18.05.2005 09:20:25
#old_value: 90                                changed: BASIS 18.05.2005 09:22:25
rdisp/max_hold_time = 300
#parameter created                          by: BASIS        20.08.2003 12:10:20
#old_value: 6144
#changed: BASIS         03.01.2008 19:42:10
rsdb/obj/buffersize = 20000
#parameter created                          by: BASIS        20.08.2003 12:09:48
#old_value: 6000
#changed: BASIS         03.01.2008 19:42:59
rsdb/obj/max_objects = 20000
note 103747
#parameter created                          by: BASIS        08.07.2003 20:42:11
#old_value: 250000
#changed: BASIS         30.10.2007 10:56:17
#abap/buffersize = 100000
#changed: BASIS         03.01.2008 19:40:36
#abap/buffersize = 300000
#by: BASIS 12.06.2008
abap/buffersize = 400000
note 103747
#parameter created                          by: BASIS        08.07.2003 20:41:32
#zcsa/presentation_buffer_area = 20000000
#64 bite gectikten sonra   by: BASIS 10.06.2008
zcsa/presentation_buffer_area = 30000768
note 103747
#parameter created                          by: BASIS        08.07.2003 20:40:55
rsdb/ntab/ftabsize = 30000
note 103747
#parameter created                          by: BASIS        08.07.2003 20:40:12
rtbb/max_tables = 500
note 103747
#parameter created                          by: BASIS        08.07.2003 20:39:15
#old_value: 20000
#changed: BASIS         03.01.2008 19:41:29
#rtbb/buffer_length = 30000
#64 bite gectikten sonra by: BASIS 10.06.2008
rtbb/buffer_length = 50000
note 103747
#parameter created                          by: BASIS        08.07.2003 20:38:26
zcsa/db_max_buftab = 10000
note 103747
#parameter created                          by: BASIS        08.07.2003 20:37:37
#zcsa/table_buffer_area = 50000000
#64 bite gectikten sonra   by: BASIS 10.06.2008
#zcsa/table_buffer_area = 89000000
by: BASIS 12.06.08
zcsa/table_buffer_area = 99000000
note 103747
#parameter created                          by: BASIS        08.07.2003 20:36:54
sap/bufdir_entries = 10000
note 103747
#parameter created                          by: BASIS        08.07.2003 20:36:12
rsdb/cua/buffersize = 8000
#note 103747
#parameter created                          by: BASIS        08.07.2003 20:34:46
#old_value: 5000                              changed: BASIS 08.07.2003 20:35:39
rsdb/ntab/sntabsize = 5500
#parameter created                          by: BASIS        08.07.2003 20:33:56
#note 103747
#old_value: 10607                             changed: BASIS 08.07.2003 20:34:58
#old_value: 10000                             changed: BASIS 08.07.2003 20:35:39
rsdb/ntab/irbdsize = 11000
#note 103747
#parameter created                          by: BASIS        08.07.2003 20:32:18
rsdb/ntab/entrycount = 40000
#old_value: 2076                              changed: BASIS 28.06.2005 19:36:21
#old_value: 5735                              changed: BASIS 28.06.2005 19:40:01
PHYS_MEMSIZE = 4096
#64 bite gectikten sonra   by: BASIS 10.06.2008
abap/heaplimit = 40894464
abap/heap_area_total = 2000683008
ztta/roll_extension = 2000683008
em/blocksize_KB = 4096
   *** UPGRADE EXTENSIONS (RELEASE "701") ***
#rdisp/elem_per_queue = 2000
#auth/auth_number_in_userbuffer = 9000
#snc/enable = 0

Hi Srikishan;
You are right. The problem was releated with secstore. I found a SAP note ( Note 1532825 - Deleting SECSTORE entries during system export/system copy). I created the program which ise mentioned in the note and than run it. After that everything seems ok now.
Thanks for your help and interest
Best regards
Noyan

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 Dump on BW

Hello experts,
We are receiving several DUMPS with the following error in our BW system:
STORAGE_PARAMETERS_WRONG_SET
ShrtText
&INCLUDE INCL_INSTALLATION_ERROR
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 CIMXDMSPR_BPR_00 on host CIMXDMBWFA (wp 0)"
Version.............. 37
Error code........... 7
Error text........... "Warning: EM-Memory exhausted: Workprocess gets PRIV "
Description.......... " "
System call.......... " "
Module............... "emxx.c"
Line................. 1890
Would you please suggest how can we identify what memory area is being exhausted so we can consider an increase in the memory parameters? What parameters changes would you suggest to perform in order to solve this issue?
Thanks and best regards,

Hi,
I want to include that this error is happening when executing a data load from an infosource we have identified.
Kindly suggest and let us know your recommendations.
Best regards

STORAGE_PARAMETERS_WRONG_SET Error

Similar Messages

Maybe you are looking for