MEMORY_NO_MORE_PAGING and TSV_TNEW_PAGE_ALLOC_FAILED

Hi All,
We are facing these errors approx. daily (but not everyday):
MEMORY_NO_MORE_PAGING
TSV_TNEW_PAGE_ALLOC_FAILED
Now, I searched the Forum but there is no acceptable answer for the current issue. Some person said that it could be possible if a user have entered any illegal range in program.
How can i modify the parameter values? RZ11 shows all parameters but not in RZ10(where we can modify).
Here is the current configuration:
Roll, extended and heap memory EXTM
ztta/roll_area        3000320    Byte Roll area per workprocess (total)
ztta/roll_first       1024       Byte First amount of roll area used in a dialog WP
ztta/short_area       3200000    Byte Short area per workprocess
rdisp/ROLL_SHM        32768      8 kB Part of roll file in shared memory
rdisp/PG_SHM          16384      8 kB Part of paging file in shared memory
rdisp/PG_LOCAL        150        8 kB Paging buffer per workprocess
em/initial_size_MB    14500      MB   Initial size of extended memory
em/blocksize_KB       4096       kB   Size of one extended memory block
em/address_space_MB   4096       MB   Address space reserved for ext. mem. (NT only)
ztta/roll_extension   2000683008 Byte Max. extended mem. per session (external mode)
abap/heap_area_dia    2000683008 Byte Max. heap memory for dialog workprocesses
abap/heap_area_nondia 0          Byte Max. heap memory for non-dialog workprocesses
abap/heap_area_total  6442450944 Byte Max. usable heap memory
abap/heaplimit        40894464   Byte Workprocess restart limit of heap memory
abap/use_paging       0               Paging for flat tables used (1) or not (0)
I also read that some parameter values like Roll Area should not be changed like here: http://help.sap.com/saphelp_nw70/helpdata/en/02/96274f538111d1891b0000e8322f96/content.htm
Furthermore, some suggestions were to modify the Heap Parameters, Roll etc...
Here is our PRD SPEC:
Processor: Intel Xeon X5450  3.00GHz
RAM: 20 GB
HDD: 140 GB Internal
SAN: 700 GB RAID
Please Advise,
Regards.

Hi Michael,
Thank you for your information, here is the current dump (most recent one):
Runtime Errors         MEMORY_NO_MORE_PAGING
Date and Time          13.10.2010 14:32:19
How to correct the error
     The amount of storage space (in bytes) filled at termination time was:
     Roll area...................... 16192
     Extended memory (EM)........... 305858320
     Assigned memory (HEAP)......... 0
     Short area..................... " "
     Paging area.................... 16384
     Maximum address space.......... " "
And Current View EM (in ST02):
SAP Memory      Curr.Use % CurUse[KB] MaxUse[KB]  In Mem[KB] OnDisk[KB] SAPCurCach HitRatio
Roll area           40.18     24,274     24,976     262,144          0   IDs           99.59
Page area           10.94     28,678     34,400     131,072    131,072   Statement     97.00
Extended memory     31.43  4,665,344  5,296,128  14,843,904          0                  0.00
Heap memory                  139,015          0     139,015          0                  0.00
Detailed Information:
Roll memory     Dialog session   kB      2,930
                Nondialog sess.  kB      2,930
                Available        kB     60,416
                in shared memory kB    262,144
                on disk          kB          0
                Used             kB     24,274
                Maximum used     kB     24,976
Paging memory   Session buffer   kB      1,200
                Available        kB    262,144
                in shared memory kB    131,072
                on disk          kB    131,072
                Used             kB     28,678
                Maximum used     kB     34,400
Extended memory Dialog session   kB  1,953,792
                Nondialog sess.  kB  1,953,792
                Available        kB 14,843,904
                Used             kB  4,665,344
                Maximum used     kB  5,296,128
Heap memory     Dialog session   kB  1,953,792
                Nondialog sess.  kB          0
                Used             kB    139,015
                Maximum used     kB    139,015
Current Parameters Setting:
Buffer Name                    Comment
Profile Parameter     Value      Unit Comment
Roll, extended and heap memory EXTM
ztta/roll_area        3000320    Byte Roll area per workprocess (total)
ztta/roll_first       1024       Byte First amount of roll area used in a dialog
ztta/short_area       3200000    Byte Short area per workprocess
rdisp/ROLL_SHM        32768      8 kB Part of roll file in shared memory
rdisp/PG_SHM          16384      8 kB Part of paging file in shared memory
rdisp/PG_LOCAL        150        8 kB Paging buffer per workprocess
em/initial_size_MB    14500      MB   Initial size of extended memory
em/blocksize_KB       4096       kB   Size of one extended memory block
em/address_space_MB   4096       MB   Address space reserved for ext. mem. (NT on
ztta/roll_extension   2000683008 Byte Max. extended mem. per session (external mo
abap/heap_area_dia    2000683008 Byte Max. heap memory for dialog workprocesses
abap/heap_area_nondia 0          Byte Max. heap memory for non-dialog workprocess
abap/heap_area_total  6442450944 Byte Max. usable heap memory
abap/heaplimit        40894464   Byte Workprocess restart limit of heap memory
abap/use_paging       0               Paging for flat tables used (1) or not (0)
Please guide me if it requires any further analysis.

Similar Messages

  • TSV_TNEW_BLOCKS_NO_ROLL_MEMORY and  TSV_TNEW_PAGE_ALLOC_FAILED

    Hi All,
    I am getting to dumps while running the DTP. they are   TSV_TNEW_BLOCKS_NO_ROLL_MEMORY and  TSV_TNEW_PAGE_ALLOC_FAILED. These happened only after transporting some transformations from dev to quality.  the same DTP's are working fine in DEV. But they are failing in QUA.
    I have checked the scenario. At the trasformation the process is getting stopped and from after sometime i am getting the DUMP. can anyone suggest me regarding the same.
    Thank You,
    Poornima.

    Hi All,
    I have tried loading two records, its showing the same error.
    and i checked out with BASIS they are saying in RZ10 everything is fine.
    even while entering into debugging its throwing TIME_OUT.
    I am wondering  why this is happening again and again
    and only for few DTP which has been trasnported is throwing the error.
    Kindly suggest.
    Thank You,
    poornima.

  • Jobs are failing and give dump "TSV_TNEW_BLOCKS_NO_ROLL_MEMORY"

    Hi ,
    Jobs are failing and giving dump "TSV_TNEW_BLOCKS_NO_ROLL_MEMORY " and TSV_TNEW_PAGE_ALLOC_FAILED.
    Here are the logs:
    ===================================================================
    15.04.2009 07:11:35 Job started                                                                                00           516          S
    15.04.2009 07:11:35 Step 001 started (program ZAPO_REALIGNMENT_MPOS_PA, variant AP_AP_REALG_S1, user ID aaa_bbb_apo)      00           550          S
    15.04.2009 07:12:52 ABAP/4 processor: TSV_TNEW_BLOCKS_NO_ROLL_MEMORY                                                      00           671          A
    15.04.2009 07:12:52 Job cancelled                                                                                00           518          A
    ===================================================================
    Job log overview for job:    BIREQU_4DHSSKZ38YF3KALR4ZBRCDNQT / 00382400
    Date       Time     Message text                                                                     Message class Message no. Message type
    15.04.2009 00:38:24 Job started                                                                           00           516          S
    15.04.2009 00:38:24 Step 001 started (program SBIE0001, variant &0000000024435, user ID aaa_bbb_APO)      00           550          S
    15.04.2009 00:38:24 Asynchronous transmission of info IDoc 2 in task 0001 (0 parallel tasks)              R3           413          S
    15.04.2009 00:38:24 DATASOURCE = 9AZAP_AM                                                                 R3           299          S
    15.04.2009 00:38:24 *************************************************************************             R8           048          S
    15.04.2009 00:38:24 *          Current Values for Selected Profile Parameters               *             R8           049          S
    15.04.2009 00:38:24 *************************************************************************             R8           048          S
    15.04.2009 00:38:24 * abap/heap_area_nondia......... 2000683008                              *            R8           050          S
    15.04.2009 00:38:24 * abap/heap_area_total.......... 2000683008                              *            R8           050          S
    15.04.2009 00:38:24 * abap/heaplimit................ 100894464                               *            R8           050          S
    15.04.2009 00:38:24 * zcsa/installed_languages...... ED                                      *            R8           050          S
    15.04.2009 00:38:24 * zcsa/system_language.......... E                                       *            R8           050          S
    15.04.2009 00:38:24 * ztta/max_memreq_MB............ 256                                     *            R8           050          S
    15.04.2009 00:38:24 * ztta/roll_area................ 100000000                               *            R8           050          S
    15.04.2009 00:38:24 * ztta/roll_extension........... 8000683008                              *            R8           050          S
    15.04.2009 00:38:24 *************************************************************************             R8           048          S
    15.04.2009 00:38:54 ABAP/4 processor: TSV_TNEW_PAGE_ALLOC_FAILED                                          00           671          A
    15.04.2009 00:38:54 Job cancelled                                                                         00           518          A
    =================================================================
    Please suggest

    Hi,
    Here are the details as follows:
    ORACLE
    10.2.0.2.0
    =====
    HP-UX
    9000/800
    ====
    Kernel release    700
    Compilation       HP-UX B.11
    Sup.Pkg lvl.      108
    ABAP Load         1563
    CUA load          29
    =============
    SCM 5.00
    SAP_BASIS     700     0011     SAPKB70011
    SAP_ABA     700     0011     SAPKA70011
    ST-PI     2005_1_700     0003     SAPKITLQI3
    PI_BASIS     2005_1_700     0011     SAPKIPYJ7B
    SAP_BW     700     0012     SAPKW70012
    LCAPPS     2005_700     0004     SAPKIBHD04
    SAP_AP     700     0008     SAPKNA7008
    EA-IPPE     400     0007     SAPKGPID07
    SCM     500     0008     SAPKY50008
    SCM_BASIS     500     0008     SAPK-50008INSCMBASIS
    QIE     200     0004     SAPK-20004INQIE
    BI_CONT     703     0005     SAPKIBIIP5
    ST-A/PI     01I_SCM500     0000          -
    VIRSANH     530_700     0005     SAPK-53305INVIRSANH
    ========================
    Thanks,
    VK

  • TSV_TNEW_PAGE_ALLOC_FAILED error in report

    Hi Experts,
                        I am trying to run a report which will retrieve the Active BPs for a particular product Id in CRM environment.
    I am trying to run the report on development in background mode.
    It is being canceled out and TSV_TNEW_PAGE_ALLOC_FAILED is a DUMP I'm getting several times.
    There is chance for selecting a large amount of data.
    Please guide me how to resolve the issue.
    Regards

    Hi,
    For background processing you need to got sm36 and schedule job. I think the problem occurs in function module. it means new page allocation is failed for the business partner. so it is retriving more than one page active Business partner for the product id.
    thanks
    Hemant

  • Memory overflow in RSA3 but not in FM on which datasource created

    Hi
    I am getting the short dump in the generic datasource extraction ( To extract CDPOS and CDHDR data) which is based on a FM. when i directly execute the FM its not giving any dump and giving me correct data, but when execute through RSA3, it gives following error. Please help me how can i correct this ?
    STORAGE_PARAMETERS_WRONG_SET and TSV_TNEW_PAGE_ALLOC_FAILED errors
    Below is the code, highlited is the code which is giving problem.
    Declaration
          OPEN CURSOR WITH HOLD S_CURSOR FOR
          SELECT MANDANT OBJECTCLAS OBJECTID CHANGENR USERNAME UDATE FROM CDHDR
                 WHERE OBJECTCLAS EQ 'EINKBELEG'
                   AND OBJECTID IN L_R_OBJECTID
                   AND UDATE    IN L_R_UDATE.
        FETCH NEXT CURSOR S_CURSOR
               APPENDING CORRESPONDING FIELDS
               OF TABLE IT_CDHDR
               PACKAGE SIZE S_S_IF-MAXSIZE.
        IF SY-SUBRC <> 0.
          CLOSE CURSOR S_CURSOR.
          RAISE NO_MORE_DATA.
        ENDIF.
        S_COUNTER_DATAPAKID = S_COUNTER_DATAPAKID + 1.
      ENDIF.
    **************HERE IS SYSTEM GIVING DUMP
       SELECT * FROM CDPOS INTO TABLE IT_CDPOS
      FOR ALL ENTRIES IN IT_CDHDR
      WHERE OBJECTCLAS EQ IT_CDHDR-OBJECTCLAS
        AND OBJECTID EQ IT_CDHDR-OBJECTID
        AND CHANGENR EQ IT_CDHDR-CHANGENR
        AND TABNAME EQ 'EKKO'
        AND FNAME   EQ 'FRGZU'.
    **************HERE IS SYSTEM GIVING DUMP
    Further Processing
      LOOP AT IT_CDPOS INTO WA_CDPOS.
        READ TABLE IT_CDHDR INTO WA_CDHDR
         WITH KEY OBJECTCLAS = WA_CDPOS-OBJECTCLAS
                  CHANGENR = WA_CDPOS-CHANGENR
                  OBJECTID = WA_CDPOS-OBJECTID.
        WA_DATAPACKAGE-MANDANT = WA_CDPOS-MANDANT.
        WA_DATAPACKAGE-OBJECTCLAS = WA_CDPOS-OBJECTCLAS.
        WA_DATAPACKAGE-OBJECTID = WA_CDPOS-OBJECTID.
        WA_DATAPACKAGE-CHANGENR = WA_CDPOS-CHANGENR.
        WA_DATAPACKAGE-VALUE_NEW = WA_CDPOS-VALUE_NEW.
        WA_DATAPACKAGE-VALUE_OLD = WA_CDPOS-VALUE_OLD.
        WA_DATAPACKAGE-USERNAME = WA_CDHDR-USERNAME.
        WA_DATAPACKAGE-UDATE    = WA_CDHDR-UDATE.
        APPEND WA_DATAPACKAGE TO E_T_DATA.
        CLEAR: WA_DATAPACKAGE,WA_CDHDR,WA_CDPOS.
      ENDLOOP.
    ENDFUNCTION.
    Edited by: Tripple k on Oct 21, 2010 6:07 PM

    Hi Rahul
    I restricted to 1 data call and 1 record per call in RSA3, still i am getting the same problem.
    Regards
    Kamal
    > Hi,
    >
    > When your execute through RSA3, there is a limit to the number of records that can be held in the memory while extraction. So it may go for these dumps. You may restrict the number of records by changing Data Records / Calls & Display Extr. Calls while running RSA3.

  • Problem with Best Practices Installation Assistant

    Hello!
    I'm trying to installing the baseline (ecc6)  located to portugal, but i'm having lot's of problems with this. when i activate the projects, the system after some minutes stops in the ecatt /SMBA0/SKB1_O12T_J01 and generates the following runtime errors: SYSTEM_NO_ROLL and TSV_TNEW_PAGE_ALLOC_FAILED.
    Does anybody knows how to solve this problems?
    Thanks,
    Ana

    The dump TSV_TNEW_PAGE_ALLOC_FAILED occurs, if the workprocess reaches its system imposed maximum memory allocation which can be caused by a program error or by the amount of data becoming too big.
    What exactly are your trying to do when THIS dump occurs?
    Markus

  • TSV_TNEW_PAGE_ALLOC_FAILED and TSV_TNEW_BLOCKS_NO_ROLL_MEMORY

    Hello,
    Happy New Year 2007 to all!
    We are using SAP R/3 4.6C, kernel 46D_EXT Patch 2271, Oracle 9.2.0.5 and HP-UX 11.23, 16GB RAM, 17GB swap.
    Lately, at the end of this year, many ABAP runtime errors <b>TSV_TNEW_PAGE_ALLOC_FAILED and TSV_TNEW_BLOCKS_NO_ROLL_MEMORY</b> ocured.
    Some times there is MEMORY_NO_MORE_PAGING.
    I have read some notes regarding this issue.
    1. Maybe I should increase the ztta/roll_area, current is 3000000 and to change into 6500000.
    2. Can you please advice me regarding the rdisp/ROLL_SHM = 16384 (32768) and rdisp/ROLL_MAXFS = 80000 (131072), should I also increase them into the values in the brackets (there is a note which has the statement 'Must be adjusted if you change ztta/roll_area')?
    3. What about the ztta/roll_first = 1 and ztta/roll_extension = 2000000000, should I also change them?
    4. Regarding the Paging area, what should I do?
    rdisp/PG_SHM = 8192 (32768) and rdisp/PG_MAXFS = 65536 (131072) , should I change into the values in the brackets?
    em/initial_size_MB = 4092
    THANK YOU in advance,
    Ruzica

    Hello Mark,
    Yes, I should have told you, the previous day offline backup was performed on the instance, that's why the buffers are clean.
    <b>Roll area sizes [kB]</b>
    Used      Max. used      In SHM      On disk
    46.264       68.856     131.072      508.928 (today)
    3.608       68.856     131.072      508.928
    3.688       76.224     131.072      508.928
    3.440       76.224     131.072      508.928
    3.384       76.224     131.072      508.928
    3.384       76.224     131.072      508.928
    5.904       76.224     131.072      508.928
    3.520       76.224     131.072      508.928
    3.520       76.224     131.072      508.928
    3.384        8.064     131.072      508.928
    3.384        9.032     131.072      508.928
    3.576       56.656     131.072      508.928
    3.576       56.656     131.072      508.928
    3.576       56.656     131.072      508.928
    3.520       55.464     131.072      508.928
    3.384       24.248     131.072      508.928
    2.112      119.536     131.072      508.928
    2.112       66.040     131.072      508.928
    3.384        8.472     131.072      508.928
    3.384        8.472     131.072      508.928
    3.744       54.456     131.072      508.928
    4.048       54.456     131.072      508.928
    <b>Page area sizes [kB]</b>
    Used      Max. used      In SHM       On disk
    69.968      211.624       65.536      458.752 (today)
        56      211.624       65.536      458.752
        56      524.280       65.536      458.752
        56      524.280       65.536      458.752
        56      524.280       65.536      458.752
        56      524.280       65.536      458.752
    7.632      524.280       65.536      458.752
        56      524.280       65.536      458.752
        56      479.912       65.536      458.752
        56       16.072       65.536      458.752
        56       16.552       65.536      458.752
        56      278.512       65.536      458.752
        56      278.512       65.536      458.752
        56      278.512       65.536      458.752
        56      271.592       65.536      458.752
        56      118.384       65.536      458.752
        32      290.640       65.536      458.752
        32      256.112       65.536      458.752
        56       16.096       65.536      458.752
        56       16.096       65.536      458.752
        56      360.872       65.536      458.752
        56      360.872       65.536      458.752
            <b> Extended memory sizes [kB]</b>              
    Used            Max. used            Available  
    2.543.616            4.186.112           4.186.112 (today)
       77.824            4.186.112           4.186.112
       73.728            4.186.112           4.186.112
       69.632            4.186.112           4.186.112
       69.632            4.186.112           4.186.112
       69.632            4.186.112           4.186.112
      180.224            4.186.112           4.186.112
       73.728            4.186.112           4.186.112
       77.824            4.186.112           4.186.112
       69.632              139.264           4.186.112
       69.632              126.976           4.186.112
       73.728            3.178.496           4.186.112
       73.728            3.178.496           4.186.112
       73.728            3.178.496           4.186.112
       77.824            3.178.496           4.186.112
       73.728            1.245.184           4.186.112
       73.728            4.186.112           4.186.112
       77.824            4.186.112           4.186.112
       69.632              462.848           4.186.112
       69.632              462.848           4.186.112
       77.824            4.186.112           4.186.112
       86.016            4.186.112           4.186.112
    How it looks like?
    Can I shortly resume about the memory parameters?
    1. em/initial_size_MB, regarding the 16GB of  the RAM, should I increase to example: 8188 (the maximum value in RZ11 is 8196)?
    2. ztta/roll_area to 6500000 ?
    3. What about the rdisp/PG_MAXFS should it be increased for 50% = 131072 ? And the rdisp/PG_SHM to increase to 32768 ?
    4. What do you think about the ztta/roll_extension = 2000000000, should I increase or to decrease the parameter?
    5. And the roll area is there need to change the rdisp/ROLL_SHM = 16384 (32768) and rdisp/ROLL_MAXFS = 80000 (131072)?
    Thanks in advance.
    Many regards,
    Ruzica

  • ICR: FBICS3 selects cleared documents and old documents

    Hi, I have just gone live with ICR functionality (processes 002 & 003) and I have notice that FBICS3 transaction is not working as I expected:
    1/ "Old documents": If I set in the program FBICS3 "year = 2010" & "month = 01"" I expected that the program would select document posted on period 1 year 2010. The reality is that the program has selected data from 2007 to now. I am surprised but probably the problem is that I did not understand how FBICS3 select data.  I assume It is correct and was my error. Since fiscal year and period are used to determine the key date of open items (open items "opened" at mm yyyy).
    2/But my real problem is that FBICS3 has selected cleared items and shows them on FBICA3 which I am sure is not correct.
    Does any body know if there is a SAP note that applies on this issue?
    Thanks a lot

    In order to give more information:
    I have already implemented following SAP Notes
    1159776     ICR: Select data from newGL     FI-GL-GL-G
    1235689     ICR: Runtime error TSV_TNEW_PAGE_ALLOC_FAILED     FI-GL-GL-G
    1337276     ICR: Cleared documents are not deleted     FI-GL-GL-G
    Thanks in advance for your help

  • MEMORY_NO_MORE_PAGING problem

    Hi,
      I need help with this issue:
      I am facing a MEMORY_NO_MORE_PAGING problem, and I don't know how to solve it. This problem is happening often during the week.
      As an example I pasted on DUMP log. In addition, at the beginning I pasted the screen information of transaction ST02.
      I have already checked the disk space and itu2019s ok, there is plenty of free space.     
    Best regards,
    Fernando.
    ST02 information:
    System: SRV-SAPPROD_PRO_00                        Tune summary
    Date & time of snapshot: 05.11.2009  11:14:41     Startup: 19.10.2009  08:15:59
           Buffer            Hitratio   Allocated         Free space        Dir. size      Free directory         Swaps       Database
                                                               Entries      Entries                          accesses
    Nametab (NTAB)
       Table definition        99,28         6.447            0     0,00        30.000            0     0,00        17.354      106.524
       Field description       99,33        49.289        2.299     4,79        30.000       11.890    39,63        45.037       70.424
       Short NTAB              99,79         3.498        2.755    91,83         7.500        6.303    84,04             0        1.212
       Initial records         99,08         9.998        8.192    86,23         7.500          653     8,71        41.690       48.659
    Program                   98,99       400.000        1.102     0,29       100.000       89.560    89,56       159.655      520.665
    CUA                       99,89         5.000          208     4,67         2.500        1.464    58,56             0        1.360
    Screen                    99,88        19.531        6.272    32,31         2.000        1.298    64,90             0        1.667
    Calendar                 100,00           488          369    76,88           200           54    27,00             0          146
    OTR                      100,00         4.096        3.657   100,00         2.000        2.000   100,00             0            0
    Tables
       Generic key             99,92        48.828       20.810    43,46         5.000          262     5,24           168       97.934
       Single record           92,56        30.000          479     1,60           500          394    78,80            70      439.952
    Export/import             87,68         4.096          110     3,01         2.000          187     9,35       245.701            0
    Exp./Imp. SHM             95,02         4.096        3.581    97,92         2.000        1.999    99,95             0            0
         SAP memory              Current use      Max. use  In memory   On disk
      Roll area                 2,29      6.009      8.728     65.536    196.608
      Paging area              91,36    239.487    262.136    124.480    137.664
      Extended Memory          64,86  1.325.056  1.728.512  2.042.880
      Heap Memory                             0  1.356.990
    DUMP LOG:
    Errores tiempo ejec.   MEMORY_NO_MORE_PAGING
    Fecha y hora           05.11.2009 10:43:41
    Txt.brv.
    SAP paging overflow when storing data in the ABAP/4 memory.
    ¿Qué ha sucedido?
    The current program requested storage space from the SAP paging area,
    but this request could not be fulfilled.
    of this area in the SAP system profile.
    Notas para corregir errores
    |    The amount of storage space (in bytes) filled at termination time was:                   
    Roll area...................... 8112
    Extended memory (EM)........... 143208832
    Assigned memory (HEAP)......... 0
    Short area..................... " "
    Paging area.................... 32768
    Maximum address space.......... " "
    You may able to find an interim solution to the problem
    in the SAP note system. If you have access to the note system yourself,
    use the following search criteria:
    "MEMORY_NO_MORE_PAGING" C
    "SAPDBIOC" or "DBIOCF02"
    "FILL_MEMORY"
    Entorno sistema
    SAP Release.............. "640"
    Application server....... "SRV-SAPPROD"
    Network address.......... "172.16.1.11"
    Operating system......... "Windows NT"
    Release.................. "5.2"
    Hardware type............ "4x Intel 801586"
    Character length......... 8 Bits
    Pointer length........... 32 Bits
    Work process number...... 3
    Short dump setting....... "full"
    Database server.......... "SRV-SAPPROD"
    Database type............ "MSSQL"
    Database name............ "PRO"
    Database owner........... "pro"
    Character set............ "Spanish_Spain.1252"
    SAP kernel............... "640"
    Created on............... "Aug 7 2009 22:57:17"
    Created in............... "NT 5.2 3790 Service Pack 2 x86 MS VC++ 14.00"
    Database version......... "SQL_Server_9.00 "
    Patch level.............. "295"
    Patch text............... " "
    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,
    Windows NT 6.0"
    Memory usage.............
    Roll..................... 8112
    EM....................... 143208832
    Heap..................... 0
    Page..................... 32768
    MM Used.................. 121508448
    MM Free.................. 9141720
    SAP Release.............. "640"
    Usuario y transacción
    Client.............. 300
    User................ "AMATUCHESKI"
    Language key........ "S"
    Transaction......... "COOISPI "
    Program............. "SAPDBIOC"
    Screen.............. "SAPMSSY0 1000"
    Screen line......... 6
    Líneas de pila C en núcleo (estructura diferente según la plataforma)
    SAP (R) - R/3(TM) Callstack, Version 1.0
    Copyright (C) SAP AG. All rights reserved.
    Callstack without Exception:
    App       : disp+work.EXE (pid=5596)
    When      : 11/5/2009 10:43:38.343
    Threads   : 2
    Computer Name       : SRV-SAPPROD
    User Name           : SAPServicePRO
    Number of Processors: 4
    Processor Type: x86 Family 15 Model 4 Stepping 3
    Windows Version     : 5.2 Current Build: 3790
    Stack Dump for Thread Id 15e0
    Edited by: Fernando Zanelli on Nov 5, 2009 1:29 PM

    Hi,
               After the first chart that displays the actual system memory status you can find the system parameters.The rdisp/PG_MAXFS as you can see is deactivated and his default value is 32768.
               It should stay deactivated or I need to bring it active?
    SAP Memory St02:
    SAP memory              Current use      Max. use  In memory   On disk
                                         [%]      [kB]            [kB]          [kB]       [kB]
    Roll area                   2,15      5.630      6.888     65.536    196.608
    Paging area              91,63    240.203   262.136    124.480    137.664
    Extended Memory     60,75  1.241.088  1.514.496  2.042.880
    Heap Memory                             0          0
    system parameters:
    |X|abap/fieldexit                             |yes
    |X|login/system_client                        |300
    |X|SAPSYSTEMNAME                              |PRO
    |X|INSTANCE_NAME                              |DVEBMGS00
    |X|SAPSYSTEM                                  |00
    |X|rdisp/wp_no_dia                            |8
    |X|rdisp/wp_no_btc                            |4
    |X|rdisp/wp_no_vb                             |3
    |X|rdisp/wp_no_vb2                            |2
    |X|rdisp/wp_no_enq                            |1
    |X|rdisp/wp_no_spo                            |2
    |X|SAPGLOBALHOST                              |srv-sapprod
    |X|PHYS_MEMSIZE                               |1996
    |X|DIR_TRANS                                  |C:\usr\sap\trans
    |X|icm/server_port_0                          |PROT=HTTP,PORT=8000
    |X|abap/buffersize                            |400000
    |X|zcsa/table_buffer_area                     |50000000
    |X|rtbb/buffer_length                         |30000
    |X|rsdb/cua/buffersize                        |5000
    |X|gw/max_conn                                |2000
    |X|gw/max_sys                                 |2000
    |X|gw/max_overflow_size                       |25000000
    |X|enque/table_size                           |10000
    |X|zcsa/presentation_buffer_area              |20000000
    |X|rdisp/appc_ca_blk_no                       |100
    |X|rdisp/wp_ca_blk_no                         |300
    |X|rsdb/ntab/entrycount                       |30000
    |X|rsdb/ntab/ftabsize                         |48000
    |X|rsdb/ntab/irbdsize                         |9500
    |X|rsdb/ntab/sntabsize                        |3000
    |X|DIR_ROLL                                   |C:\usr\sap\PRO\DVEBMGS00\data
    |X|DIR_PAGING                                 |C:\usr\sap\PRO\DVEBMGS00\data
    |X|DIR_DATA                                   |C:\usr\sap\PRO\DVEBMGS00\data
    |X|DIR_REORG                                  |C:\usr\sap\PRO\DVEBMGS00\data
    |X|DIR_TEMP                                   |.
    |X|DIR_SORTTMP                                |C:\usr\sap\PRO\DVEBMGS00\data
    |X|zcsa/system_language                       |S
    |X|zcsa/installed_languages                   |EDPS
    |X|install/codepage/appl_server               |1100
    |X|abap/use_paging                            |0
    | |ztta/roll_first                            |1024
    | |ztta/roll_area                             |2000896
    |X|rdisp/ROLL_SHM                             |8192
    | |rdisp/ROLL_MAXFS                           |32768
    |X|rdisp/PG_SHM                               |15560
    | |rdisp/PG_MAXFS                             |32768
    | |abap/heap_area_dia                         |2000683008
    | |abap/heap_area_nondia                      |2000683008
    | |abap/heap_area_total                       |2000683008
    | |abap/heaplimit                             |40894464
    |X|abap/swap_reserve                          |20971520
    | |ztta/roll_extension                        |2000683008
    | |em/initial_size_MB                         |1840
    |X|em/blocksize_KB                            |1024
    |X|em/stat_log_size_MB                        |20
    |X|em/stat_log_timeout                        |0
    | |em/address_space_MB                        |512

  • MEMORY_NO_MORE_PAGING

    Hi
    I have just installed NSP testdrive - in System:Status it says: SAP EHP 1 for SAP NetWeaver 7.0
    When i try to run transaction SWO3 i get a MEMORY_NO_MORE_PAGING dump. What can I do about that?
    The dump:
    Runtime Errors         MEMORY_NO_MORE_PAGING
    Short text
         SAP paging overflow when storing data in the ABAP/4 memory.
    What happened?
         The current program requested storage space from the SAP paging area,
         but this request could not be fulfilled.
         of this area in the SAP system profile.
    Error analysis
         The ABAP/4 runtime system and the ABAP/4 compiler use a common
         interface to store different types of data in different parts of
         the SAP paging area. This data includes the
         ABAP/4 memory (EXPORT TO MEMORY), the SUBMIT REPORT parameters,
         CALL DIALOG and CALL TRANSACTION USING, as well as internally defined
         macros (specified with DEFINE).
         To store further data in the SAP paging area, you attempted to
         allocate a new SAP paging block, but no more blocks were
         available.
         When the SAP paging overflow occurred, the ABAP/4 memory contained
         entries for 5 of different IDs.
         Please note:
         To facilitate error handling, the ABAP/4 memory was
         deleted.
    Trigger Location of Runtime Error
         Program                                 SAPLSEUT
         Include                                 LSEUTU12
         Row                                     60
         Module type                             (FORM)
         Module Name                             TR_PUSH

    Hi Thomas,
    Go to ST22, click on "How to correct" it will give the necessary steps.
    You need to tweak some meomory pramater to get rid of this paging error.
    Thanks,
    Debasis.

  • MEMORY_NO_MORE_PAGING " dump

    Hi All,
    We are at SAP ECC 5.0 SAP_BASIS 640.
    Today morning while running mb51 we got " MEMORY_NO_MORE_PAGING " dump.
    Could please help to fix this problem?
    Here is the error info:
    What happened?
    The current ABAP program had to be terminated because the
    ABAP processor detected an internal system error.
    The current ABAP program "RM07DOCS" had to be terminated because the ABAP
    processor discovered an invalid system state.
    Error analysis
    An internal error occurred when releasing memory in
    SAP Paging. The release ended with the error code
    "-1".
    How to correct the error
    It is probably not possible to eliminate the system error
    with ABAP alone.
    If you have access to SAPnet, you can search for a relevant note
    using the following keywords:
    "MEMORY_PGFREE_FAILED" " "
    "RM07DOCS" bzw. "RM07DOCS_GENERATED"
    "DATA_SELECTION"
    171 endloop.
    172
    173 * process SELECT command depending on the
    174 * required material selection
    175 if l_cnt_matnr_total > 0 and
    176 l_cnt_matnr_total = l_cnt_matnr_i_eq.
    177 * work with .. for all entries ...
    178 select (l_t_fields)
    179 into corresponding fields of table itab
    180 from mkpf inner join mseg
    181 on mkpfmandt = msegmandt
    182 and mkpfmblnr = msegmblnr
    183 and mkpfmjahr = msegmjahr
    184 for all entries in matnr
    185 where matnr = matnr-low
    186 and MKPF~BUDAT in BUDAT
    187 and MSEG~BWART in BWART
    188 and MSEG~CHARG in CHARG
    189 and MSEG~KUNNR in KUNNR
    190 and MSEG~LGORT in LGORT
    191 and MSEG~LIFNR in LIFNR
    192 and MKPF~MJAHR in MJAHR
    193 and MSEG~SOBKZ in SOBKZ
    194 and MKPF~USNAM in USNAM
    195 and MKPF~VGART in VGART
    196 and MSEG~WERKS in WERKS
    197 and MKPF~XBLNR in XBLNR
    198 .
    199 else.
    200 * work with the select command as usual
    >>>>> select (l_t_fields)
    202 into corresponding fields of table itab
    203 from mkpf inner join mseg
    204 on mkpfmandt = msegmandt
    205 and mkpfmblnr = msegmblnr
    206 and mkpfmjahr = msegmjahr
    207 WHERE MKPF~BUDAT in BUDAT
    208 and MSEG~BWART in BWART
    209 and MSEG~CHARG in CHARG
    210 and MSEG~KUNNR in KUNNR
    211 and MSEG~LGORT in LGORT
    212 and MSEG~LIFNR in LIFNR
    213 and MSEG~MATNR in MATNR
    214 and MKPF~MJAHR in MJAHR
    215 and MSEG~SOBKZ in SOBKZ
    216 and MKPF~USNAM in USNAM
    217 and MKPF~VGART in VGART
    218 and MSEG~WERKS in WERKS
    219 and MKPF~XBLNR in XBLNR
    Regards,
    Leo

    Note 1091141 & note 1104914 also are recommending that you upgrade your Basis kernel release to resolve the error.
    4.6D: 2348
    6.40: 204
    7.00: 131
    If your Basis kernel release is not listed but you are receiving the error often, I would still upgrade to the latest kernel release.

  • MEMORY_NO_MORE_PAGING error

    Hi,
    We are using ECC 5.0 here. Our DB is Oracle 9.2.0.6 and OS is AIX.
    We have a problem here.
    Our Finance people run a report "S_ALR_87013542". It was working fine.
    But now it is giving an error with ABAP Dump. The error is MEMORY_NO_MORE_PAGING.
    I have increased the parameter "rdisp/PG_SHM" to the double value. Now the value is 16384. But it is still giving the same error.
    I increased it on a Dialog Instance (application server through which Finance people access SAP)
    I searched the notes, but could not find anything relevant about my error.
    I have tried to run the report in the night when there is no load on the server. But even then it gives the same error.
    My different Memory Paramters for the App server for finance people are listed below:-
    ztta/roll_area                              3000320   
    rdisp/ROLL_SHM                              16384     
    rdisp/ROLL_MAXFS                            32768     
    rdisp/PG_SHM                                16384     
    rdisp/PG_MAXFS                              32768     
    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
    My ABAP dump gives this error:-
    Error analysis
        The ABAP/4 runtime system and the ABAP/4 compiler use a common
        interface to store different types of data in different parts of
        the SAP paging area. This data includes the
        ABAP/4 memory (EXPORT TO MEMORY), the SUBMIT REPORT parameters,
        CALL DIALOG and CALL TRANSACTION USING, as well as internally defined
        macros (specified with DEFINE).
                                                                                    To store further data in the SAP paging area, you attempted to
        allocate a new SAP paging block, but no more blocks were
        available.
                                                                                    When the SAP paging overflow occurred, the ABAP/4 memory contained
        entries for 55 of different IDs.
                                                                                    Please note:
        To facilitate error handling, the ABAP/4 memory was
        deleted.
    How to correct the error
        The amount of storage space (in bytes) filled at termination time was:
                                                                                    Roll area...................... 16128
        Extended memory (EM)........... 418992800
        Assigned memory (HEAP)......... 0
        Short area..................... " "
        Paging area.................... 40960
        Maximum address space.......... 4294967295
                                                                                    By calling Transaction SM04 and choosing 'Goto' -> 'Block list',
        you can display an overview of the current roll and paging memory
        levels resulting from active users and their transactions. Try to
        decide from this whether another program requires a lot of memory
        space (perhaps too much).
                                                                                    The system log contains more detailed information about the
        termination. Check for any unwanted recursion.
        Determine whether the error also occurs with small volumes of
        data. Check the profile (parameter "rdisp/PG_MAXFS", see
        Installation Guidelines).
        Is the disk or the file system that contains the paging file
        full to the extent that it cannot be increased, although it has
        not yet reached the size defined in the profile? Is the
        operating system configured to accommodate files of such a
        size?
                                                                                    The ABAP processor stores different types of data in the SAP paging area
        . These include:
                                                                                    (1) Data clusters (EXPORT ... TO MEMORY ...)
           (2) Parameters when calling programs (SUBMIT REPORT ...),
            dialog modues (CALL DIALOG ...) and transactions
            (CALL TRANSACTION USING ...)
        (3) Internally defined macros (DEFINE ...)
                                                                                    Accordingly, you should check the relevant statements in a program
    that results in an overflow of the SAP paging area.
                                                                                    The EXPORT statement is particularly critical - specifically when many
    internal tables, possibly with different IDs, are written to the
    memory.                                                                   
    Kindly help
    Regards,
    Tajinder

    Hello,
    Here the parameters for concern are
    1.rdisp/PG_SHM
    2.rdisp/PG_MAXFS
    1.rdisp/PG_SHM :
    The value specifies the size of the paging buffer in 8KB blocks.
    A paging buffer is no longer required for SAP Memory Managment,
    because internal tables and lists are not stored in SAP paging.
    Default : 0
    2.rdisp/PG_MAXFS :
    This value specifies the size of the SAP paging file in 8KB
    blocks.  The paging file is used to store extracts and for
    Export to Memory.
    Aim:
    The paging file must be sufficiently large. It is not a problem
    if it is set to too large a size.
    Dependencies:
    Sufficient disk space
    You can try
    1.Optimize the code, to use less memory.
    OR
    2.Increasing the parameter rdisp/PG_MAXFS as per the availability of disk space.
    Hope this solves your problem.
    Regards,
    Edited by: Satish P on Oct 21, 2008 2:01 PM

  • MEMORY_NO_MORE_PAGING dump in LCEI0F6O

    Hi Experts,
    When i run a background job for a zprogram automatically another job is getting triggered and it is getting cancelled after some time. When i check the Job log i saw the dump
    MEMORY_NO_MORE_PAGING in the iinclude LCEI0F6O of SAPLCEI0
    Short text says "SAP paging overflow when storing data in the ABAP/4 memory"
    and soucre code extract shows dump at the "Clear Statement"
       49   EXPORT
       50          multi_lingual
       51          mi
       52          wi
       53          anw
       54          gt_ghcl
       55          TO MEMORY ID gs_memory_id.
       56
    >>>>>   CLEAR gs_memory_id-memid.
       58
       59   EXPORT gv_actual_memory_id
       60          gt_memory
       61          TO MEMORY ID gs_memory_id.
    Please suggest me in correcting the above dump
    Thank you,
    Kavya

    Hi,
    It is not problem in standarad program, but it in zprogram problem. When you export data to memory it has some limitation parameter to limit the maximum data to store. when your zprogram run it try to store more data in to application server memory and it not allow to store the maximum due to limit it.
    In your porgram you are reading large amount of data. Don't read all data at all but you do the modification in your program to read data partially and process it. do the same for may time but don't forget to refresh or free the memory of internal table which is store unnecessary data.

  • SAP_COLLECTOR_FOR_PERFMONITOR dumping MEMORY_NO_MORE_PAGING

    Dear friends,
    In one of our BW production system, 2 instance of hourly job SAP_COLLECTOR_FOR_PERFMONITOR is dumping MEMORY_NO_MORE_PAGING.
    I have already checked this thread :
    MEMORY_NO_MORE_PAGING
    But I am unable to find out the reason and also i do not find any Moni Key in abap dump. Please suggest.
    PART OF ABAP DUMP :
       40          SEGMT     = SEGMT.
       41 *     exceptions
       42 *          others       = 1.
       43
       44 EXPORT TS    TO MEMORY ID 'RSORAT2M'.
       45 EXPORT TD110 TO MEMORY ID 'RSORAT4M'.
    >>>>> EXPORT SEGMT TO MEMORY ID 'RSORAT6M'.
       47
       48 * INCLUDE rsorat0b.       T.S. 11/96
       49 * INCLUDE rsorat0m.       T.S. 11/96
       50 * INCLUDE rsorat0f.       T.S. 11/96
       51 *INCLUDE RSORAT2F.
    thanks
    ashish

    Hello friends,
    Of-Course MEMORY_NO_MORE_PAGING is a memory dump and it can be avoided if i increage paging sizes. We have smaller value for this parameter and I am not convinced if it is required now to increase it. This was working nicely sometime back.
    So, When we say we have abap statement EXPORT which is causing MEMORY_NO_MORE_PAGING. But the same abap statement was working fine sometime back and we did not had this problem. So i assume if there is something like large number of history records as per SAP Note 713211 is troubling us.
    Now, i want to findout what is causing so much of memory requirement & page files.
    We also get similar dumo when we manually try to perform DB Checks & update histories with transaction DB02OLD. This is the same this what Collector Job also doing and dumping.
    Any new suggestion please..
    thanks
    ashish

  • VC_I_GET_CONFIGURATION and paging memory

    Hi everyone
    I am modifying an existing program that makes use of the VC_I_GET_CONFIGURATION FM.  Under certain conditions SAP will throw a 'memory_no_more_paging' error.  This always happens at line 55 of the SET_MD_TO_BUFFER Form, which is called from within the form SETUP_MASTER_DATA, which is in turn called from VC_I_GET_CONFIGURATION.  The FM module is called from within a loop round an itab that holds VBAP records for a customer.  If the number of records is reasonably large (by our standards - >5000) then this error seems to occur.
    Looking at the code and debugging to see what is happening, it looks as if a config. table of about 400 rows is being repeatedly read and Exported to memory.  I think that this is acting as a buffer because prior to this a check is made to see if the exact combination has already been read. I guess this is why the memory error is being triggered.  Has anybody else experienced this? Is there anything I can do apart from requesting more hardware or re-writing the bespoke program?
    Thanks in advance...
    Andy
    Message was edited by: Andrew Wright
    Hi
    Just wanted to keep this one going - I'm no closer to figuring it out!

    Hi Bala
    This change has since gone into our production system where we had real performance issues.  I have been improving the performance of the program as a whole and at nno point have I found using VC_I_GET_CONFIGURATION_IBASE to be the cause of any performance problems - its generally been down to bad SQL!  Using this version of the function has compeltely solved the original problem (short dumps because the memory ran out).  I haven't personally tried creating a custom function to use the VC_I_GET_CONFIGURATION version because there didn't seem to be any point - after all it was using less memory and ran faster!  The OSS note states that the VC_I_GET_CONFIGURATION uses the buffer to improve online performance and so is not designed for mass updates.  I'm not sure I follow the logic there since I wold have thought that mass updates would be precisely when you want to make use of buffered data.  If you have any thoughts on that matter I would be interested to know.
    Kind regards
    Andy

Maybe you are looking for

  • Font rendering difference between Acrobat 8 and Acobat 9

    We received a PDF file that looks fine in Acrobat 8 and in Preview but when opened in Acrobat 9 the lower half of many fonts is cut off. We see the problem on multiple computers, Mac and PC with both Acrobat Pro 9 and Reader 9. Is there anything that

  • Power Mac G4 - 933 - maxium size of second internal hard drive

    I have a Power Mac G4 933 Mhz with an existing 60 Gb internal hard drive. I am trying to determine definitively the largest sized internal hard drive I can add in addition to my existing 60 Gb drive. There are a variety of articles saying 120 Gb is t

  • Old emails that I archived suddenly appeared in my Inbox again

    Yesterday over 330 old archived emails suddenly downloaded back into my Inbox. I didn't make any changes to my Gmail account nor did I sync anything. This happened while I was on vacation, so its very bizarre. The emails start from 10 months back - a

  • PSE 12 content aware fill

    If I use the content aware move tool to select an obect can I hit delete to remove it, if so will it fill in with surrounding image like it does in the full photoshop program?

  • Why does my iPhone 4S WiFi keeps shutting off?

    This is the SECOND black iPhone 4S with problems with WiFi once the IOS 8 updated is downloaded.  So frustrating! Just after the IOS 8 update was available, I updated my black iPhone 4S.  Soon after, I experienced a hot battery, screen freezes, and t