EXSORT_NOT_ENOUGH_MEMORY

Dear All,
We are getting this dump while blocking PO in ME32L in our production.
Production is on Windows NT 32Bit with 4 GB physical RAM.
Standard parameter--
ztta/roll_first          1
ztta/roll_area          2000000
ztta/roll_extension                     2000000000
ztta/max_memreq_MB     1048          
em/address_space_MB     512
em/initial_size_MB                     4092          
em/max_size_MB          20000
em/global_area_MB                     128
em/stat_log_size_MB                     20
em/stat_log_timeout                     0
ztta/roll_area          2000000
abap/heap_area_dia                     2000000000
abap/heap_area_nondia     2000000000
abap/heap_area_total                     2000000000
rdisp/ROLL_SHM          32768          
rdisp/PG_SHM          16384          
rdisp/PG_MAXFS          32768          
abap/buffersize          400000
abap/heap_area_dia                     2000000000
abap/heap_area_nondia     2000000000
abap/heap_area_total                     2000000000
abap/heaplimit          40000000
Please suggest
Regards,
Mahesh

Hello,
The reasons for the dump are described in SAP note #193529 (Sort as of 4.5A /
EXSORT_NOT_ENOUGH_MEMORY) I will also outline some other steps:
Possible solutions:
1. Normally reducing parameter abap/heap_area_nondia is sufficient
   to provide HEAP memory for example a SORT operation.  So you can
   reduce the parameter slightly, and then check the problem
   again. For more info, please refer to note #193529. Suggest
   to leave this option until last if it's a Windows 32-bit instance.
2. You can consider reducing the shared memory areas such as the
   program, roll or paging buffers. If necessary investigate
   the potential for this on the instance where the dumps occur
   if the information below is not clear enough to determine if
   roll and paging buffers can be reduced from defaults.
3. Activate the '/3GB' option, please refer to note #313347 to check
   if your edition supports this being set in the C:\boot.ini file.
   http://support.microsoft.com/kb/28303, has more information about
   the /3GB option.
These errors can be due to lack of address space or that
the data selection is too large for the available memory of the
instance and needs to be reduced to ensure that it can finish without
memory terminations.
More information about this topic that can be applied to any
Windows 32-bit instance:
====================================================
To re-allocate some of the unused shared memory to program memory,
a prime candidate for this is Roll and Page "In Memory" values.
Alternative memory management via PHYSMEMSIZE generally overallocates
roll and page memory. Please reduce the amounts allocated to the "in
memory" part (see ST02) using the parameters below...
Zero administration memory management (Note #88416) generally
overallocates roll and page memory. Usually you can reduce the
the amounts allocated to the "in memory"
rdisp/ROLL_MAXFS....Total amt of ROLL (Filesystem+SHM); in 8KB blocks
rdisp/ROLL_SHM......Shared memory element of Roll; in 8KB blocks
rdisp/PG_MAXFS......Total amt of Page (Filesystem+SHM); in 8KB blocks
rdisp/PG_SHM........Shared memory element of Roll; in 8KB blocks
=>Filesystem amount. = MAXFS - SHM
Bear in mind that Roll_SHM MUST be greater than 10% of Roll_MAXFS.
60MB or so each in memory should be sufficient. rdisp/ROLL_SHM &
rdisp/PG_SHM only to be changed. This should allow extra
memory for process memory.
It also important that after changing the parameters that you
monitor in TA ST02 the consumption of Roll and Paging in the system.
If the value of 'Max. use' for the Roll-Area reach the value
'In memory' then you should increase the parameter rdisp/ROLL_SHM
to e.g. 10000.
Example:
rdisp/ROLL_SHM changed from 32768 to 7500 (60000/8) to change
the 'in memory' Roll area from 262,144 kB to 60,000 kB
====================================================
An increase in available address space by reducing buffers as above or
more importantly the PAE /3GB flag if possible may be enough to ensure the
successful completion.
Regards.

Similar Messages

  • Short dump "EXSORT_NOT_Enough_MEMORY" in production system

    Hi,
    "EXSORT_NOT_Enough_MEMORY" dump occuring in production system,Could any one please tell me how to fix this dump.
    Please refer the error message below
    What happened?
        The current ABAP program had to be terminated because the
        ABAP processor detected an internal system error.
        The current ABAP program "RSBPCOLL" had to be terminated because the ABAP
        processor discovered an invalid system state.
    Error analysis:
        The current ABAP/4 program was meant to sort a dataset (internal table
        or extract). For reasons of capacity, this was not possible due to
        insufficient main storage space. Therefore, the
        external sort was called and resulted in the following error:
        the following error:
        SAP runtime system internal error.
                   Last error logged in SAP kernel
        Component............ "EM"
        Place................ "SAP-Server cambsvr15_PEC_00 on host cambsvr15 (wp 12)"
        Version.............. 37
        Error code........... 7
        Error text........... "Warning: EM-Memory exhausted: Workprocess gets PRIV "
        Description.......... " "
        System call.......... " "
        Module............... "emxx.c"
        Line................. 1886
    and i see that background job  "SAP_COLLECTOR_FOR_JOBSTATISTIC" job being failed with  below error.
    Job started
    Step 001 started (program RSBPCOLL, variant , user ID BACKGROUND)
    ABAP/4 processor: EXSORT_NOT_ENOUGH_MEMORY
    Job cancelled
    Please help me to correct this error.
    Best Regards,
    Vinod

    Hi Bhaskar,
    yes, I have checked the Wp status and it looks fine.I'm getting this error on My PRD system on regular basis since 1 week.
    We have tried to restart the server but no luck.
    Here are the ST02 values and background job SAP_COLLECTOR_FOR_JOBSTATISTIC also being failed with this error.
      Buffer              Hitratio    Allocated       Free space          Dir. size      Free directory        Swaps      
                              [%]         [kB]           [kB]      [%]      Entries       Entries    [%]                  
    Program                   99.11       400,000        1,481     0.38      100,000      90,774    90.77       36,307
    CUA                       99.31         3,000          264    10.53        1,500       1,263    84.20       14,934
    Screen                    98.45         4,297           27     0.82       10,000       9,653    96.53         645
    Calendar                  99.76           488          359    75.10          200          48    24.00         0
    OTR                      100.00         4,096        3,439   100.00        2,000       2,000   100.00         0
    SAP memory              Current use      Max. use  In memory   On disk
                            [%]      [kB]       [kB]       [kB]       [kB]
    Roll area              1.45      3,808     7,680    262,144         0
    Paging area            3.40      8,904     13,056       0        262,144
    Extended Memory        9.05    389,120    812,032  4,299,776
    Swaps
            0
       21,249
            0
       16,399
       36,307
       14,934
          645
            0
            0
          272
            0
      210,742
            0
    Please let me know if you require further information.
    Thanks & Regards,
    Vinod

  • EhP4 - EXSORT_NOT_ENOUGH_MEMORY Error during EhP4 installation on WIN32

    Hi Gurus.
    I am installing EhP4 on win32 system.
    Background:
    ERP 6.0 with EhP3 installed.
    Windows Server 2003 on 32 Bit /fastdetect /3GB /PAE
    3G enabled
    PAE enabled
    I have referred to most of the threads on the error but no luck.
    Please find error details below:
    -   Error in phase: DDIC_ACTIVATION
    -   Reason for error: TP_STEP_FAILURE
    -   Return code: 0012
    -   Error message: OCS Package SAPK-40401INEAIPPE, tp step A, return code 0012
    Runtime Errors         EXSORT_NOT_ENOUGH_MEMORY
    Date and Time          17.06.2010 20:18:40                                        
    Short text
    Internal error: Too little memory for the external sort
    What happened?
    Error in the SAP kernel. The current ABAP "RADMASDSC" program had to be terminated because the ABAP processor detected an internal system error
    SAP runtime system internal error.
    Last error logged in SAP kernel
    Component............ "EM"
    Place................ "SAP-Server esmart03_ESM_00 on host esmart03 (wp 7)"
    Version.............. 37                                                                      
    Error code........... 7
    Error text........... "Warning: EM-Memory exhausted: Workprocess gets PRIV "
    Description.......... " "                                                                     
    System call.......... " "                                                                     
    Module............... "emxx.c"                                 
    Line................. 2207
    The error reported by the operating system is
    Error number..... " "
    Error text....... " "
    The amount of storage space (in bytes) filled at termination time was:
    Roll area...................... 1709536
    Extended memory (EM)........... 386729920
    Assigned memory (HEAP)......... 1639377312
    Short area..................... " "
    Paging area.................... 65536
    Maximum address space.......... " "
    Thanks in advance for your help.
    Regards
    Shreeshail
    Edited by: Shreeshail Ganiger on Jun 18, 2010 8:28 AM

    > The amount of storage space (in bytes) filled at termination time was:
    > Roll area...................... 1709536
    > Extended memory (EM)........... 386729920
    > Assigned memory (HEAP)......... 1639377312
    You may try to offer the system more heap memory by decreasing abap/heap_area_nondia.
    Any reason why you don't use a 64bit OS? 32bit is deprecated and you may see other memory related errors...
    Markus

  • EXSORT_NOT_ENOUGH_MEMORY dump

    Hi,
    We have an ECC6 [windows 2003 server 32 bit system] and we were getting the error "EXSORT_NOT_ENOUGH_MEMORY".
    We have activated  the 3 GB boot option which has resolved the issue.
    I would like to know if there is any long term solution to this problem.
    Thanks,
    Rajiv.

    a few pointers:
    1. read SAP note 88416
    2. consider separating your SAP central instance from your SAP database instance. This way, each of them will be allowed to use 3GB instead of sharing it.
    3.decrease memory related Oracle parameters... and increase the SAP memory related parameters.
    4. ask your user to choose their parameters properly when starting their reports. Ask them to cut their reports in multiple parts.
    5. if this error occurs on Z Program, ask your developers to use internal tables less aggressively.
    6. switch to 64-bit as soon as possible. 32-bit for servers is old technology!
    good luck.

  • Short DUMP: EXSORT_NOT_ENOUGH_MEMORY

    Hello everyone,
    Our user is running some reports using Transaction IQ09-
    Display Material Serial Number List, and its going to the dump
    by giving error message as "STORAGE_PARAMETERS_WRONG_SET"
    or "TSV_TNEW_PAGE_ALLOC_FAILED" or EXSORT_NOT_ENOUGH_MEMORY.
    We have tried to execute this transaction in background mode
    and still getting the same dump/error message. We are getting
    this error in our Production R/3 system (PU1) and it is
    affecting business operations.
    "In the what you can do" section in DUMP log, this is what I find:
    Set the system profile parameters
    - abap/heap_area_dia
    - abap/heap_area_nondia
    to a maximum of 687977744. Then reduce the value by 10.000.000 to be on the
    safe side.
    Then restart the SAP System.
    Our system is 32-bit SAP kernel and what these DUMPs means is additional memory is required to extend the internal table, but none is available. This error is usually due to a lack of system resources for the roll area where internal tables are processed.
    Below are the profile parameters we have set in our PRD system.
    ztta/roll_first                             1024
    ztta/roll_area                             2000896
    abap/heap_area_dia                   2000683008
    abap/heap_area_nondia              2000683008                
    abap/heap_area_total                 2000683008
    abap/heaplimit                           40894464
    abap/swap_reserve                     20971520
    ztta/roll_extension                      2000683008
    em/initial_size_MB                     5765
    em/blocksize_KB                       1024
    Do I need to change any of the above profile parameters in RZ10 to get rid of the dump? Do you think this will have any adverse effect on our production system such are system may run out of shared memory.
    Any help will be greately appreciated and points will be rewarded.
    Thanks,
    Shahid Anjum

    Hi Shahid,
    To understand how the system performs sorting and the EXSORT_NOT_ENOUGH_MEMORY error, see SAP Note 193529 Sort as of 4.5A/EXSORT_NOT_ENOUGH_MEMORY.
    The error TSV_NEW_PAGE_ALLOC_FAILED means that more memory was requested  because the program needed to expand an internal table, but the memory was not available.
    When Extended Memory is used up, the process will go into PRIV mode as it starts using Heap Memory (or vise-versa).  No other user will be able to use this wp while it is in PRIV mode.  If there is enough heap for it to finish, you will not see the error TSV_NEW_PAGE_ALLOC_FAILED and the wp will be freed.
    You should check your settings for the profile parameters abap/heap_area_total and abap/heap_area_nondia against the Notes:
    146289  Parameter Recommendations for 64-Bit SAP Kernel
    425207  SAP memory management, current parameter ranges
    Also, see the Notes:                                          
    20527  Runtime error TSV_TNEW_PAGE_ALLOC_FAILED                        
    217262  Runtime error text for TSV_TNEW_PAGE_ALLOC_FAILED              
    185185  Application: Analysis of memory bottlenecks                    
    649327  Analysis of memory consumption              
    However, often the problem may not be with memory settings, but with the selection values the user is entering for the report.  That is, they may be entering a very wide range against a very large table.  In these cases, check the selection values and reduce them.  Also, check the affected table size and consider if parts of it may be archived.
    Best Regards,
    Matt

  • Short Dump - EXSORT_NOT_ENOUGH_MEMORY in ACT_UPG

    Hello Experts,
    I am in the process of Upgrading ECC6 EHP3 to EHP4.
    Upgrade is stalled in phase  ACT_UPG phase for last almost 24 hours now.
    I posted a thread about that
    [EHP4 upgrade stucl in MAIN_SHDRUN/ACT_UPG;
    Now my phase got an error EXSORT_NOT_ENOUGH_MEMORY .
    How can I approach this problem?
    I already changed the parameters as per note 1387739.
    My physical memeory is 12G
    Can anyone seen this problem during ehp4 uPGRADE.
    Other than above I don't see any other short dumps in Shadow instance.
    Please suggest.
    Thanks for your time.
    Regards,
    M

    Hi Sunny,
    Thanks for your reply. Yes I increased non-dia/total abap heap area and roll area as suggested by note
    1387739 to
    abap/heap_area_total = 5000000000
    abap/heap_area_nondia = 5000000000
    ztta/roll_area = 10000000
    I have restarted the phase where it stopped. It's currently running now. Wil update the forum as I see any results.
    Also I increased swap file of the system to 22G. Eralier it was 10G.
    Thanks,
    M

  • MAIN_SHDCRE/SUBMOD_SHDDBCLONE/ADJUSTCHK_EHPI -  EXSORT_NOT_ENOUGH_MEMORY

    Hello Friends
    We are upgrading our ECC 6.0 system to EHP7 sp02.
    We are using SUM tool for the same and SUM version is 1.0 SP11, AIX 6.1 TL09, ORACLE 11.2.0.3
    Our environment is installed as CI DB on different servers.
    I am in preprocessing stage and in phase MAIN_SHDCRE/SUBMOD_SHDDBCLONE/ADJUSTCHK_EHPI I am getting dump EXSORT_NOT_ENOUGH_MEMORY.
    i have already followed 193529 - Sort as of 4.5A/EXSORT_NOT_ENOUGH_MEMORY but no success.
    Our memory parameters are as below.
    em/initial_size_MB            8184       MB
    em/blocksize_KB               4096       kB
    em/address_space_MB           4092       MB
    ztta/roll_extension           2000000000 Byte
    abap/heap_area_dia            4000000000 Byte
    abap/heap_area_nondia         2000000000 Byte
    abap/heap_area_total          6000000000 Byte
    abap/heaplimit                40000000   Byte
    abap/use_paging               0
    Please suggeat if I am missing something.
    Regards
    SS

    Hi Divyanshu,
    ulimit -a for sidadm was already unlimited. And reduced the ,abap/heap_area_nondia to 1500000000 Byte.
    But it still failed.
    ulimit -a
    time(seconds)        unlimited
    file(blocks)         unlimited
    data(kbytes)         unlimited
    stack(kbytes)        unlimited
    memory(kbytes)       unlimited
    coredump(blocks)     unlimited
    nofiles(descriptors) 32000
    threads(per process) unlimited
    processes(per user)  unlimited
    Regards
    SS

  • Not enough memory short dump

    I am investigating a performance problem with a SAP standard report.  It falls over when trying to sort a table, the table size is [194994x294].  In know this is large but is it common for it to cause a EXSORT_NOT_ENOUGH_MEMORY short dump?

    Hi,
    Go to my computer and right click on it....
    and go to properties.....
    then go to advanced tab...
    in it go to performance settings...
    then go to advanced tab
    in that go to virtual memory....in it click on change...
    in change click on the radio button  'system managed size'
    click on set and save it...
    it might help you...
    Regards
    Debarshi

  • Datapackage size problem

    Hi all,
    I'm trying to decreasse one infosource max datapackage size in order to avoid a dump EXSORT_NOT_ENOUGH_MEMORY without succes. I've tried with Datasaource default data transfer changing the max size but it seems nothing changes.
    Thanks in advance,
    Regards,
    Carlos.

    Hi Carlos,
    even the note talks about the same...
    Error EXSORT_NOT_ENOUGH_MEMORY:
    Large tables are sorted during the check and kept in the roll area. The SAP directory DIR_SORTTMP is used for the sorting process; this is the name of the profile parameter designating the physical directory.
    check the note..

  • Support pack SAPKB70014 stuck at ddic activation

    Hi!
    While upgrading Support Pack SAPKB70014, import stuck at phase DDIC_ACTIVATION, reason for error is TP_STEP_FAILURE, the return code is 0012 and the error message: OCS Package SAPKB70014, tp step A, return code 0012.
    I can see in the log of the import queue that the job RDDMASGL was terminated and I found the entry "ABAP / 4 processor: EXSORT_NOT_ENOUGH_MEMORY" in the log of that job.
    In SAP memory analysis (transaction st02) I can see that maximal 285 MB heap memory were used while 2 GB are possible. During installation of the support pack always 8 GB of physical memory were free in the OS. The SAP system is running under Windows 2003 R2 Enterprise Edition SP2 with 12 GB of physical memory.
    What's the reason for this and what can I do?
    Thanks in advance!
    Nico Wallmeier

    Hi
    Please help
    I am new in Basis my system has 4GB Ram running windows system 32. To what value should I set my memory parameters.

  • Ehp1:Solution Manager:Stuck at ddic activation

    Hello All,
    While upgrading the Solution Manager to Ehp1, import stuck at phase DDIC_ACTIVATION, reason for error is TP_STEP_FAILURE, the return code is 0012 and the error message: OCS Package ******** , tp step A, return code 0012.
    I can see in the log of the import queue that the job RDDMASGL was terminated and I found the entry "ABAP / 4 processor: EXSORT_NOT_ENOUGH_MEMORY" in the log of that job.
    My system is a 32 bit Windows operation system with 3GB physical Ram.
    I have the following doubt
    1.) If i keep on re-runing  again will the already activated program will be skip or will be re-activated.
    2.)How can i resolve this error.
    Regards
    Anthony

    Hi
    If i keep on re-runing again will the already activated program will be skip or will be re-activated.
    It will be skiped and will proceed with rest of the object
    How can i resolve this error.
    You need to check import logs for better analysis
    Rerun the import and see how the things go
    Regards
    Uday

Maybe you are looking for

  • TrackPad physical click not working after upgrade to Mountain Lion

    Does anybody know how to get my trackpad working again after upgrading to Mountain Lion? I recently upgraded my MacBook (13-inch, Late 2009, Intel Core 2 Duo) from Snow Leopard to Mountain Lion. Everything seems to have gone well, except for trackpad

  • IPad will not be recognized by itunes and wont start up

    Hello, I have an (iPad 2, WiFi+3G) 64GB and when i try to open it it stucks in the black screen with the apple logo. I cant loggin! Also it is not recognizable by itunes so I cant restore it to its factory settings. Does anyone here knows any third p

  • 10.5.3 has broken printing to my Brother printer

    I updated both my MacBook Pro and my wife's MacBook to 10.5.3 three days ago. Since then, we cannot print to our Brother MFC-440CN (usually connected to our Airport Express). All attempts at printing, wireless or USB, fail. When I'm watching from the

  • Iphoto - slideshow in trash freezing Iphoto

    I moved an iphoto slideshow to trash yesterday and now cannot empty the trash as any attempt to click on the slideshow or empy the trash brings up the  rainbow ball  and I have to force quit.  I have tried reorganising my itunes media files but they

  • Footnote placement in columned document!??

    In my document, the text box is set to 2 columns. The paragraph text flows in those 2 columns, but headings/subheadings span. It all worked wonderfully until the client requested the addition of footnotes. I want the footnotes to be at the bottom of