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.

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

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

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

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.

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

Lock ups and dumping psyical memory!!!

Hi i have just installed a new pc most of the stuff im useing is from my old computer so i know they work fine im running a:
P4 3GHZ Prescot 800MHz, HT-Enabled
865PE Neo2-P
512 DDR-400 Twin moss
ATI Radeon 9000 pro
PSU-400
XP Pro
My computer locks up alot when running intense games (games have worked before no problem) i also get a error saying dumping pysical memory, i have looked about and tried to solve this myself, i found that someone was haveing the exact same problem as me and he fixed it by turning the FSB down as his memory wasnt compatable with his motherboard if doing that works how do i do it ?
Many thanks Jonathan

Flappa, Your memory " clock" is fine and there is no need to "underclock it" as long as you did not mess with the Bios.
I had the same problems. I could not even get thru a Clean install of windows as it would Blue Screen
1- are you running in " Dual Channel Mode"?
2- If so is your memory a " match Set"?
some times memory even thought it has the same markings is not matched . Dual channel sets are matched and made to run together in "Dual Channel Mode"{
( Even though I had the same manufacturer memory my set would not run in Dual Channel without " Blue Screening" I bought a Matched Set of Kingston Valueram and have not had a problem since
3- If it is not a matched set, pull one stick out and run it for a while , if it still bluescreens try the other stick
4- raise your memory voltage to 2.7 or 2.8 ( which ever is the lowest that it runs stable)
5- If all this does not work , run MEMTEST to see if there is a problem with both sticks
6- you are running a Bios Version that supports the " Prescott Microcode" right?
Let us know what your findings are
Good Luck
Dave

Report J_1IEWT_CERT getting cancelled, generating ABAP dump!

A long running report J_1IEWT_CERT in background mode is getting cancelled after running for a while and generating the following dump :
Error analysis
    When changing or deleting one or more lines of the internal table
    "\PROGRAM=J_1IEWT_CERT\DATA=PRINTTAB[]" or when inserting in the table
     "\PROGRAM=J_1IEWT_CERT\DATA=PRINTTAB[]", 0 was used as
    the line index. An index less than or equal to zero is not
    allowed.
    The error can occur when using the following options:
    1. "INDEX idx" for specifying the line number in the table
     "\PROGRAM=J_1IEWT_CERT\DATA=PRINTTAB[]"
       where you want to change, insert or delete.
    2. "FROM idx" for specifying the start index when deleting a line
       area from or inserting a line area into the table
     "\PROGRAM=J_1IEWT_CERT\DATA=PRINTTAB[]".
    3. "TO idx" for specifying the end index when deleting a line
       area from or inserting a line area into the table
     "\PROGRAM=J_1IEWT_CERT\DATA=PRINTTAB[]".
    At the time of the termination, the table contained 17008 lines.
How to correct the error
    If the error occurred in your own ABAP program or in an SAP
    program you modified, try to remove the error.
    If the error occures in a non-modified SAP program, you may be able to
    find an interim solution in an SAP Note.
    If you have access to SAP Notes, carry out a search with the following
    keywords:
    "TABLE_INVALID_INDEX" " "
    "J_1IEWT_CERT" or "J_1IEWT_CERT_F01"
    "FILTER_DATA"
    If you cannot solve the problem yourself and want to send an error
    notification to SAP, include the following information:
    1. The description of the current problem (short dump)
       To save the description, choose "System->List->Save->Local File
    (Unconverted)".
    2. Corresponding system log
       Display the system log by calling transaction SM21.
       Restrict the time interval to 10 minutes before and five minutes
    after the short dump. Then choose "System->List->Save->Local File
    (Unconverted)".
    3. If the problem occurs in a problem of your own or a modified SAP
    program: The source code of the program
       In the editor, choose "Utilities->More
    Utilities->Upload/Download->Download".
Tried searching for some SAP Notes to fix the issue, no success as of now, Please help me out...

Have you checked these notes ?
363107 Short dump occurs during TDS certificate printing.
803806 Error while genrating TDS certificate 03.01.2005
1066049 J1INCERT - Error while generating TDS certificate
Regards,
Subhash

Short dump 'Table does not exist in database'

Hello All,
When a report is executing it is going to short dump by saying 'Table does not exist in database'. As per the short dump analysis this issue is happening because of the following   Native SQL statement statement :
Program : %_T050N0 (This is a dynamic program generating by SAP )
Form Name : DYN_LIC_SEL_TOT
exec sql performing LOOP_MOVE_WRITE_ISAP.
select single_plate, itm_num, ctry_code, model_lot,
lic_hold_flg, qty into :dcat-lplate, :dcat-matnr,
:dcat-werks, :dcat-charg, :dcat-holdflag,
:dcat-qty from ZLICENSE_R2 where itm_num   = :p_matnr and
                model_lot = :p_charg
endexec.
As per the customer this issue occurring since they migrated the SAP back-end data base from Oralce to DB6. Here I felt that ZLICENSE_R2 is not migrated from the Oracle to DB6. But as per the BASIS Team, even this table was not maintained in Oracle also. If the table was not maintained in the Oracle, this issue should have been there even before migration also.
Following is the short dump details:
Short text
    Table does not exist in database.
What happened?
    The table or view name used does not
    exist in the database.
    The error occurred in the current database connection "DEFAULT".
What can you do?
    Check the spelling of the table names in your report.
    Note down which actions and inputs caused the error.
    To process the problem further, contact you SAP system
    administrator.
    Using Transaction ST22 for ABAP Dump Analysis, you can look
    at and manage termination messages, and you can also
    keep them for a long time.
Error analysis
    An exception occurred that is explained in detail below.
    The exception, which is assigned to class 'CX_SY_NATIVE_SQL_ERROR', was not
     caught in
   procedure "DYN_LIC_SEL_TOT" "(FORM)", nor was it propagated by a RAISING
clause.
Since the caller of the procedure could not have anticipated that the
exception would occur, the current program is terminated.
The reason for the exception is:
Triggering SQL statement: "select single_plate, itm_num, ctry_code, model_lot,
lic_hold_flg, qty from ZLICENSE_R2 where itm_num = ? and model_lot = ? "
Database error code: "-204"
Could you please let me know what might be the reason for this issue.
Many Thanks in Advance.

Transaction SE11, input ZLICENSE_R2 for table name, and display the table. Did the table display? If not, that is the main problem.
If the table displays, go to menu item Utilities -> Database Object -> Database Utility
In the resulting screen, under the "Status" fields, you should see text "Exists in the database." If you don't, then the table exists in the dictionary, but doesn't exist in the database system. Click the "Create database table" button and then you should be able to run the program.
You may need basis team's help to carryout some of these actions.

Short Dump while scrolling in a maintenance view

A maintenance view has one field, defined as "Radiobutton".
1) Select the radiobutton for one entry.
2) Scroll down so that in the new page (i.e. the entries displayed in the new page) the entry selected in the first step is not visible.
3) Select any radiobutton again corresponding to any of the entries displayed in the new page.
4) On scrolling up again the short dump occurs.
The short dump text says "More than one radio button is active".
Any inputs in this regards are appreciated.
Thanks.
Gajendra.

Hi,
that means you are trying to make two radio buttons active.
parameters: ra radiobutton group g1 default = 'X',
rb radiobutton group g1.
ra = 'X'.
and rb = 'X'.
in your case so obviously it will dump.
check your coding..
and show your code...
Regards
vijay

Is it possible to create manually a dump?

Dear all,
I have a question about Dumps created in SAP while programs run with unpredicted errors.
I have a specific table defined in the dictionary which has two coloumns progId and path.
The first one is a unique identifier given to a program and the second column is an absolute path on the
unix server where SAP is installed.
For example
MyProg | /usr/tmpbatch/data/E200
Means that the ABAP program named 'MyProg' will run and its output file (the output of the program) and the
log file are created in /usr/tmpbatch/data/E200.
In each of my programs, first of all I check the content of this table in order to ensure that the path is defined for the
given program (and therefore I may be able to create avec success both output and log files). If there is no entry
in the table for the given program, I leave the program by calling the STOP instruction.
My programs run at night, so the next day the corresponding users read the content of the generated output/log files.
As a result, if the path is not defined properly for a given program in the table, the program is not run and therefore
there will be no output/logfile the next day.
My question is How can I inform the user who arrives the next day observing that one program has not been run? How
can I tell him by some kind of system message that the program exited because the path for the files had not been defined in
my table?
Each morning, we can analyse the dumps which were produced during the precedent day. So that we may know
(approximately) what went wrong. But as far as I know, dumps are generated automatically by the system. Is it possible
to generate a dump (by calling some fucntion) with an appropriate error message for my problem?
Thanks in advance,
Dariyoosh

Hello again,
First of all I would like to thank everybody for their attention to my problem and
for spending time for answering my question. Thank you all very much.
Currently, Thomas' solution about MESSAGE_TYPE_X seems to work pretty well
for my problem. As all of you mentioned that, there should be softer methods to inform
users. One main problem is that the program which lanuches my programs during night
is not a sap user, it is a Unix scheduler (please forgive me I don't know these administration
details and how they work) so according to what the administrator told me it is not possible
to send email. As a result, I think I may go with MESSAGE_TYPE_X until I found another proper way.
Once again, thank you all for your help.
Kind Regards,
Dariyoosh

Error while importing a dump file in Oracle 10g R1

Hi all,
While trying to import a schema using Data Dump, I am facing the following issue -
UDI-00018 - Import utility version can not be more recent than the Data Dump server.
Following is the version information of the source and target DB and the utilities :
Source DB server : 10.1.0.2.0
Export utility : 10.1.0.2.0
Import utility : 10.1.0.2.0
Target DB server : 10.1.0.2.0
Export utility : 10.2.0.1.0
Import utility : 10.2.0.1.0
I can figure out the cause for the problem, but don't know how to resolve it.
Any help will be appreciated.
Thanks in advance.
Gitika Khurana

How did you get thre DMP file created and how are you trying to import the dump file? Could you post the commands you're using, please?

Error_Exception dump while opening the report in RRMX

Hi All,
When User trying to open the report Error_Exception dump is coming for few Info Providers. Please find attached dump for your reference.

Issue is res loved, We have analyze the short dump ,when loads were running and at that if time user executed the queries then that dump was occuring.

SHORT DUMP WHILE EXECUTING DTP.

Hi Gurus,
I have got a short dump while executing DTP the Error is as Follows.
Runtime Error: MESSAGE_TYPE_X.
Reasons for Error: 1.The installation of the SAP GUI on the present server is faulty or obselete
2.There is a error in the application program
And i have sent the sreen shot of the Short Dump to BASIS TEAM and they have replied me that they have to install some patches and it will take some time.
But i have no much time and i have to someway or the other execute the DTP and load the data.
Is there any shortcuts for this i mean to say without the involvement of Basis team that i can do in th BI System
Regards
Amar.

Hi Amar,
If the problem is with with System itself, how can we all have a short cut in that case. You may give it another trial, but you have to wait for the patches to be applied. Ask your basis team to get it done ASAP.
Thanks..
Shambhu

EXSORT_NOT_ENOUGH_MEMORY dump

Similar Messages

Maybe you are looking for