MEMORY_NO_MORE_PAGING and TSV_TNEW_PAGE_ALLOC_FAILED

[Former Member]

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.

[former_member204746]

you did not adapt your system, to SAP note 88416. This will make your life simpler.

basically, you set PHYS_MEMSIZE and unset parameters (from the middle of the SAP notes).

there ya go.

[Former Member]

Thank you all for ur replies.

Firstly, I will look into the Zero Memory Configuration but to do that I am going to create a Test server and check on that. Sorry for the late reply due to auditing is in process.

If it is unsuccessful, then i will try the other methods.

I am not closing the thread because I will try my best to implement your mentioned Notes onto Test Server.

[Former Member]

Hi ya all,

its been quite a while since last reply, i configured Zero Memory configuration on my Test Server and worked just fine but another question, can it be the issue originated from ABAP customized reports/Tcode?

If this is true, then im closing the subject.

Thank you again.

regards.

[Former Member]

Hi,

Paste the Abap Dump.........Here.

Mark

[Former Member]

Here it is:

Runtime Errors         MEMORY_NO_MORE_PAGING
Date and Time          12.10.2010 10:45:29

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 17 of different IDs.

    Please note:
    To facilitate error handling, the ABAP/4 memory was
    deleted.

Information on where terminated
    Termination occurred in the ABAP program "SAPLWDTM" - in "TABCONTROL_SH_START".
    The main program was "ZFAH_BATCH_SEARCH ".

    In the source code you have the termination point in line 135
    of the (Include) program "LWDTMU20".

If anything else is required in ABAP Dump, Please specifiy.

[Former Member]

Hi,

The answer you pasted is in Red ......I'd have a word with the developer about his "Z" program

Mark

[Former Member]

Thanks A lot.

This confirms out my confusion about the dump errors.

Thanks again.

[Former Member]

Well the interesting part of the dump is the section with the memory information:

How to correct the error                                                  
    The amount of storage space (in bytes) filled at termination time was:
                                                                                Roll area...................... 6219104                               
    "Extended memory (EM)........... 2002781760"                            
    "Assigned memory (HEAP)......... 2000034848"                            
    Short area.....................                                     
    Paging area.................... 90112                                 
    Maximum address space.......... 18446604360196005919                  

This for example shows, that 2gb EM and 2gb of heap memory were taken at the moment of the dump. In the most systems this is the configured maximum for one single workprocess. In this case i always consider it a program error (or too large data selection), unless the developer can explain, why he needs more than 4gb

Cheers Michael

[Former Member]

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.

[Former Member]

Well i was talking mainly about the TSV_TNEW_PAGE_ALLOC_FAILED dump, sorry for not being perfectly clear on this. Most has already been said in this thread, but here are my two cents:

The MEMORY_NO_MORE_PAGING basically means that your paging space (rdisp/PG_MAXFS) was exhausted. But still in most cases this is also a program error. As i see in your configuration you 256mb page area, you can savely increase this to 512mb for example.

The strange thing is that in your screen output, the page area was not exhausted. This could mean several things, the dump happend on another instance, the instance was restarted or else.

Cheers Michael

Edited by: mho on Oct 15, 2010 3:33 PM

[Former Member]

Exactly, due to some critical issues, we were shutting the servers (instances) down approx. after every 36-40 hours or so. But now its up and will run as maturely as it should.

Advise required again

We checked teh parameters, confirmed with other senior relations and also analysed ourselves that the buffer values are OK. I think this issue has 2 roots, 1st is ineffiecient development and 2nd: Shutting the systems (which obviously resets all buffer values) down. We are already facing a lot of ineffecient custom programs which are disturbing our perfomance.

Im really depressed about the Z stuff filling up all Dialogs.

What is the Optimal uptime for SAP?

Thank you all.

Regards.

[former_member204746]

What is the Optimal uptime for SAP?

on windows, we reboot weekly.... mostly to clear things up and apply MS patches.

for Unix, we use to do this once a month. on another place, this was done once every three months.

[Former Member]

Hi,

Please try the below steps also,

Goto st02 - detaiil analysis menu - history / buffer statistics - Roll & Page area.

check and increase the below parameters : rdisp/rol_maxfs, rdisp/pg_maxfs.

check the SAP notes : 133909 and 146289

With Regards,

Senthil Kumar.C

[former_member524429]

Hi,

I would refer this useful [SAP Note 103747 - Performance: Parameter recommendations as of Release 4.0|https://service.sap.com/sap/support/notes/103747] for the same and will compare existing parameter settings against this note and will do the required based on available memory.

Regards,

Bhavik g. Shroff

[Former Member]

Hi Bhavik,

Thank you for the reply,

here is some more info about the PRD Server:

PRD is ECC 6

O.S: Windows 2003 64 bit R2 SP1

Oracle DB 10.2.0.4

I will read the note you mentioned and will reply back.

Thanks again.

Regards.

[former_member524429]

Hi,

That SAP Note 103747 - Performance: Parameter recommendations as of Release 4.0 is also applied for your PRD configuration. Please refer it carefully.

Also keep in mind that the Performance Tuning is on-going Iterative process which requires lot of analysis.

The following [SAP Note 830576 - Parameter recommendations for Oracle 10g|https://service.sap.com/sap/support/notes/830576] is also helpful for Oracle.

Regards,

Bhavik G. Shroff