9 Replies Latest reply: Jan 19, 2010 12:51 PM by Shyam Dontamsetty RSS

MEMORY_NO_MORE_PAGING problem

Fernando Zanelli
Currently Being Moderated

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

 

  • Re: MEMORY_NO_MORE_PAGING problem
    Mahesh Chedde
    Currently Being Moderated

    CHeck SAP Notes : 192822, 441663. Seems to be your OS is on 32 Bit. Upgrade to 64 Bit OS, so that there will not be issues with the Memory.

  • Re: MEMORY_NO_MORE_PAGING problem
    Klaus Moeser
    Currently Being Moderated

    Hello,

    the error means that there is an overflow in the SAP paging area. You get some more information about this in note 133909. You just should increase the profile parameter rdisp/PG_MAXFS.

     

    Regards, Klaus

    • Re: MEMORY_NO_MORE_PAGING problem
      Fernando Zanelli
      Currently Being Moderated

      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

      • Re: MEMORY_NO_MORE_PAGING problem
        Amber Soni
        Currently Being Moderated

        Hi Fernanado, We also recieved this dumps in one of our production system.

         

        can you please check if this dump is raised in any particular application server ?

         

        If yes can you please ask your OS admin to check the disks if your PP's are in sync status and no bad sectors are there ?

         

        PP's - Physical Partitions.

         

         

        we faced the similar issue and our OS admin did sync of disks then we restarted our app server and problem got resolved.

         

        Regards, Amber S

        • Re: MEMORY_NO_MORE_PAGING problem
          Wim Van den Wyngaert
          Currently Being Moderated

          Hello,

           

          I see a mistake here that is often made by system administrators.

          In stead of trying to solve the problem by changing system parameters or instance parameters you have to look for the root cause first.

          Changing parameters always has to come on the second place.

           

          In your short dump I see that more then 1,4 Gb of memory was allocated in a DIAlog workprocess.

          You have to analyze why such an amount of memory was allocated and by which program/user.

           

          You have all the statistics you need in transaction ST03N, check the top memory consumers both on program and user level.

          Maybe a wrong selection is made by the end user

           

          Wim

          • Re: MEMORY_NO_MORE_PAGING problem
            Nico Bresseleers
            Currently Being Moderated

            Hi,

             

            I believe Wim is right, there is unsufficient HW in the world for all errors in any application..

             

            Saying that, altought de dump only contains the first part so not the code extract, i noticed the sap standard program SAPDBIOC , without knowing the exact part of the source where the dump occured i can only guess that this note could be helpfull:

             

            Note 698303 - POIT: Download of orders, performance, memory consumption

             

             

            if not, please post the source codextract ( do mark the line where the dump is comming from ) so we can check further

             

            Rgds

            Nico

            • Re: MEMORY_NO_MORE_PAGING problem
              Jeroen Verbrugge
              Currently Being Moderated

              Ask google : 143208832 bytes in MB

               

              Result : 143 208 832 bytes = 136.574585 megabytes

              • Re: MEMORY_NO_MORE_PAGING problem
                Gopal vvs
                Currently Being Moderated

                Hi Fernando,

                 

                Can you give me the below inputs

                 

                1) Values for the parameters rdisp/pg_shm,rdisp/pg_maxfs values of from the instance profile

                2) Below screen or the values from below

                   a) Tcode ST02 (take care so that page and roll memory parameters are captured)

                   b) In ST02, double click on the values of the roll or page in SAP memory table , it will show a history of the roll and page       memories.

                3) Latest encountered dump

                 

                Most probably Klas is right ... you may need to increase the either of the parameters.

                 

                Thanks & Regards,

                Gopal.VVS

                • Re: MEMORY_NO_MORE_PAGING problem
                  Shyam Dontamsetty
                  Currently Being Moderated

                  Hi Fernando,

                  '

                  I will go with Wim words, Before looking at the parameters for analyzing.understand the problem.

                  First thing ,this problem appears recently or it is there long back also.Identify which app server dumps this memory problem.

                  Most of the memory related problems need to be understand ,process perspective;means identify which user/transaction causes this memory dump. Find out any way how to avoid this dump.Talk to the end user on this process and see if as an administrator can do avoid memory bottlenecks.

                   

                  Thanks,

                   

                  Best Regards,

                  Shyam Dontamsetty

Actions