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

Similar Messages

  • STORAGE_PARAMETERS_WRONG_SET dump

    Hello,
    I have installed BW 3.5 on MS SQL 2005, Windows 32 bit system and facing lot of performance issues in BO reports execution. System goes in hang state when multiple users log in. Also geting dump STORAGE_PARAMETERS_WRONG_SET
    DUMP details are :
    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 140067200 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 
    - abap/heap_area_nondia    
    to a maximum of 140067200. Then reduce the value by 10.000.000 to be on the safe side.      
    Pls help
    Regards,
    Ankita.

    Hi,
    might be you enter wrong values in boot.ini
    did you follow  Note 110172 - Windows: Transactions with large memory requirements
    Activate the 3 GB boot option according to Microsoft KB article 283037.
    your boot.ini looks like following ( for example only )
    [boot loader]
    timeout=30
    default=multi(0)disk(0)rdisk(0)partition(2)\WINDOWS
    [operating systems]
    multi(0)disk(0)rdisk(0)partition(2)\WINDOWS="Windows Server 2003, Standard" /fastdetect /NoExecute=OptOut /3GB /USERVA=2800
    check following to edit boot.ini
    http://support.microsoft.com/kb/317526/
    regards,
    kaushal

  • ST22 Short Dump  STORAGE_PARAMETERS_WRONG_SET

    Hi
    We have a NW04 BW 350 system running on Windows 2003 32 Bit/MS SQL 2000 32 Bit.
    When I go into RSA --> Monitoring --> PSA  it says 'constructing administrators workbench' then fails with the short dump:
    <b>STORAGE_PARAMETERS_WRONG_SET</b>
    The shortdump reccommends increasing parameters abap/heap_area_dia and
    abap/heap_area_nondia, I would have thought you would want to avoid using HEAP memory as this locks the memory into a single work process ?
    Looking at the memory consumption in the shortdump :
    <b>Memory usage.............
    Roll..................... 1709536
    EM....................... 108964960
    Heap..................... 406948064
    Page..................... 57344
    MM Used.................. 495709152
    MM Free.................. 17059832
    SAP Release.............. "640"</b>
    EM has only been used for about 100 MB, then it go's to HEAP memory.
    Looking at ST02 the system has 4GB EM and only 1.7GB used at 42%, so why would the process only use 100 MB of EM?
    ztta/roll_extension is set to default 2GB so it appears EM memory should be utilised more by the work process before going to HEAP memory.
    What parameters affect the usage of EM before entering HEAP usage?
    Thanks for any advice.

    Dear friend
    kindly see the folowing rsdb/ntab/entrycount     Number of nametab entries administrated     20000     30000
    rsdb/ntab/ftabsize     Data area size for field description buffer     30000     60000
    rsdb/ntab/irbdsize     Data area size for initial records buffer     6000     8000
    rtbb/buffer_length     Size of single record table buffers     16383     60000
    zcsa/table_buffer_area     Size of generic table buffer     64000000     120000000
    zcsa/db_max_buftab     Directory entries in generic table buffer     5000     30000
    zcsa/presentation_buffer_area     Size of the buffer allocated for screens     4400000     20000000
    sap/bufdir_entries     Maximum number of entries in the presentation buffer     2000     10000
    rsdb/obj/buffersize     Size of export/import buffer     4096     40000
    rsdb/obj/max_objects     Max. no. of exporting/importing objects     2000     20000
    Parameters     Description     Current value     Recommended value
    em/initial_size_MB     Size of extended memory pool     4096     8192
    em/global_area_MB     Size of SAP Extended Global Memory (see SAP Note 329021)     96     255
    ztta/roll_area     Maximum roll area per user context     3000000     16773120
    rdisp/PG_SHM     Paging buffer size in shared memory     8192     32768
    Parameters     Description     Current value     Recommended value
    rdisp/wp_ca_blk_no     Work process communication blocks     300     1000
    rdisp/appc_ca_blk_no     Buffer size for CPI-C communications     100     2000
    gw/max_conn     Max. number of active connections     500     2000
    rdisp/tm_max_no     Max. number of entries in array tm_adm     200     2000
    rdisp/max_comm_entries     Max. number of communication entries     500     2000
    gw/max_overflow_size     Max. swap space for CPIC-requests in the gateway     5000000     100000000
    gw/max_sys     Max. number of connected clients     300     1000
    shailesh

  • 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

  • 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.
    <b>Runtime error:storage_parameters_wrong_set.</b>
    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.

  • SHORT DUMP  due to STORAGE_PARAMETERS_WRONG_SET in ALV

    Hello All,
    There is an internal table containing more than 200,000 thousand records.
    when this is passed to ALV grid for display, the program terminates with the exception STORAGE_PARAMETERS_WRONG_SET
    I was wondering if there is a way to prevent the program from terminating.
    Are there any system settings that can be changed/checked?
    (Its an Unix OS).
    Any help is welcome.
    Many thanks!
    Vinay

    This is what SAP documentation says:
    Set the system profile parameters                                   
    - abap/heap_area_dia                                                
    - abap/heap_area_nondia                                             
    to a maximum value. Then reduce the value by 10.000.000 to be on the
    safe side.                                                                               
    Then restart the SAP System.                                                                               
    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.                                                          
    The program had already requested &P1 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.

  • ABAP DUMP - STORAGE_PARAMETERS_WRONG_SET

    HI
    WHILE RUNNING REPORT FOLLOWING DUMP WAS OCCOUR PLEASE HELP ME
    What happened?                                                                               
    The current program had to be terminated because of an                                       
        error when installing the R/3 System.                                                        
        The program had already requested 1014772128 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.
    REGARDS
    MOHSIN

    32bit Windows? Standard program or self-written?
    Markus

  • 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

  • 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

  • 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

  • HR ABAP Posiition Holder Org Unit value going dump

    Hi Experts,
    I am working now HR ABAP. My issue is,  I am using standard Program RHXPEP01. This Program is nothing but. Profile Match up Position/Holder.
    Once i execute this program and enter the  value of Org. Unit Value is 60010128. Then after 15mints it will be going dump.
    The error message is going to many iterations are going on.
    If I execute 60010129 it is working fine. This Org Units are avilable in Production.
    Can you plz help me on this.
    Thank You
    Sri

    Hi ,
    Please check this thread might be helpful.
    Runtime Errors STORAGE_PARAMETERS_WRONG_SET
    Regards,
    Siraj.

  • PPOME - Org.Unit (Acount assignment) goes into DUMP

    Hello Gurus,
    ive got a Big issue, concerning SAP HR module.
    When we start the TC: PPOME we select org.unit from the structure.
    It is beeing showed normaly, but only when we select Acount assignment it goes straight into DUMP,
    saying:
    Runtime Errors         STORAGE_PARAMETERS_WRONG_SET
    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 189714480. To be on the safe side, reduce the value by 10,000,
        000.                                                                         
        Then restart the SAP system.       
    These corrections are not needed since the system for every other purpose (SD, MM, FI) is working, only for HR module during acount assignment is going into DUMP.
    Any advice why this happens to some of the Org.Units?
    Regards,
    Laurynas Prikockis

    Hi ,
    Please check this thread might be helpful.
    Runtime Errors STORAGE_PARAMETERS_WRONG_SET
    Regards,
    Siraj.

Maybe you are looking for