PXA_NO_SHARED_MEMORY

[Former Member]

Hi All,

We have been facing lot of memory issues in production system and QA ECC ABAP only system after kernel upgrade from Basis 700 patch 310 to 347. Is there any known issue with this release? Users are not able to login then and there. We have all parameters set as per Note 146289 - Parameter Recommendations for 64-Bit SAP Kernel and Note 88416 - Zero administration memory management for the ABAP server. Our platform: 64 bit windows 2003 server/sql2005. I referred note Note 307976 - PXA_NO_SHARED_MEMORY and our abap buffersize is 1300000KB. Physical memory is 24GB. Do I have to increase the physical memory? System was much better before this kernel upgrade for add-on Vistex installation. Then so many memory related issues.

There are also other dumps like SYSTEM_CORE_DUMPED, STORAGE_PARAMETERS_WRONG_SET

"In the system profile, set the parameters

-abap/heap_area_dia and

-abap/heap_area_nondia

to a maximum of

1731363904. To be on the safe side, reduce the value by 10,000,

000."

But parameter values are kept standard from the above mentioned Notes. Please help ASAP.

Thanks,

Kavitha Rajan.

[Former Member]

Hi Kavitha,

Could you take a reboot of the windows server.It should probably help.

Regards,

Deepak Kori

[Former Member]

Hi Deepak,

It got cleared after almost 30 minutes by itself. This is occurring then and there, system is going to emergency mode. I am looking to fix the issue permanently. Please help.

Thanks,

Kavitha

[Nibu]

Hi Kavitha,

Hope you updated DEV and QA before going for PRD . If the issue is not in those systems, its not a kernel issue I guess.  Usually  the issue comes if PXA area is too high check  abap/buffer size  and reduce if needed , compare with DEV/QA the values, hope it will help.

Regards,

Nibu Antony

[Nibu]

Kavitha,

Hope the  Note 425207 - SAP memory management, current parameter ranges can help you to make decisions on values. Also you can search notes like Note 923610 - Memory parameter recommendations for banking systems for your scenario .  Refer https://scn.sap.com/blogs/tyronemapp/2012/05/11/how-to-fix-pxanosharedmemory-short-dump-error-in-sap...  to make changes on above said profile parameter .

Regards,

Nibu Antony

[Former Member]

Hi Nibu,

Your replied are very helpful. Now I am getting another dump in production only. (Dev, QA and prod are all different in config and also in usage and physical memory.) One of the batch job terminated due to this dump. Could you please help me with this one. I have already reduced abap/buffersize as per your earlier suggestion. (this weekend I will restart). In the meantime getting below dump.

Runtime Errors         TSV_TNEW_BLOCKS_NO_ROLL_MEMORY
Date and Time          06/12/2013 00:28:33

Short text
     No roll storage space of length 2517000 available for internal storage.

What happened?
     Each transaction requires some main memory space to process
     application data. If the operating system cannot provide any more
     space, the transaction is terminated.

What can you do?

     Try to find out (e.g. by targetted data selection) whether the
     transaction will run with less main memory.

     If there is a temporary bottleneck, execute the transaction again.
     -

     If the error persists, ask your system administrator to check the
     following profile parameters:

     o  ztta/roll_area            (1.000.000 - 15.000.000)
            Classic roll area per user and internal mode
            usual amount of roll area per user and internal mode
     o  ztta/roll_extension       (10.000.000 - 500.000.000)
            Amount of memory per user in extended memory (EM)
     o  abap/heap_area_total      (100.000.000 - 1.500.000.000)
            Amount of memory (malloc) for all users of an application
            server. If several background processes are running on
            one server, temporary bottlenecks may occur.
            Of course, the amount of memory (in bytes) must also be
            available on the machine (main memory or file system swap).
            Caution:
            The operating system must be set up so that there is also
            enough memory for each process. Usually, the maximum address
            space is too small.
            Ask your hardware manufacturer or your competence center
            about this.
            In this case, consult your hardware vendor
     abap/heap_area_dia:        (10.000.000 - 1.000.000.000)
            Restriction of memory allocated to the heap with malloc
            for each dialog process.
     Parameters for background processes:
     abap/heap_area_nondia:        (10.000.000 - 1.000.000.000)
            Restriction of memory allocated to the heap with malloc

           for each background process.
    Other memory-relevant parameters are:
    em/initial_size_MB:         (35-1200)
           Extended memory area from which all users of an
           application server can satisfy their memory requirement.
    Note which actions and input led to the error.

    For further help in handling the problem, contact your SAP administrator
    .

    You can use the ABAP dump analysis transaction ST22 to view and manage
    termination messages, in particular for long term reference.

Error analysis
    The internal table "\FUNCTION-POOL=STXC\DATA=OTF[]" could not be enlarged
     further.

    Memory location: "Session memory"

    You attempted to extend the data structure for the management of the
    memory blocks for table "\FUNCTION-POOL=STXC\DATA=OTF[]". However, the 2517000
     bytes required for
    this were no longer available in the specified memory area.

    The amount of memory requested is no longer available.

How to correct the error

    Try to decide by analysis whether this request is
    reasonable or whether there is a program error. You should pay
    particular attention to the internal table entries listed below.

     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:

    "TSV_TNEW_BLOCKS_NO_ROLL_MEMORY" " "
    "SAPLSTXC" or "LSTXCOTF"

    "OTF_APPEND"

    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".

    4. Details about the conditions under which the error occurred or which
    actions and input led to the error.

System environment
    SAP-Release 700

    Application server... "xxxxxxxxxxxxxxxxx"
    Network address...... "xxxxxxxxxxxxxx"
    Operating system..... "Windows NT"
    Release.............. "5.2"
    Hardware type........ "4x AMD64 Level"
    Character length.... 16 Bits
    Pointer length....... 64 Bits
    Work process number.. 1
    Shortdump setting.... "full"

    Database server... "xxxxxxxxxxxxxxxxxxxxx"
    Database type..... "MSSQL"
    Database name..... "PRD"
    Database user ID.. "prd"

    Terminal................. " "

    Char.set.... "C"

    SAP kernel....... 700
    created (date)... "Jun 12 2012 22:57:20"
    create on........ "NT 5.2 3790 Service Pack 2 x86 MS VC++ 14.00"
    Database version. "SQL_Server_8.00 "

    Patch level. 347
    Patch text.. " "

    Database............. "MSSQL 7.00.699 or higher, MSSQL 8.00.194"
    SAP database version. 700
    Operating system..... "Windows NT 5.0, Windows NT 5.1, Windows NT 5.2, Windows
     NT 6.0, Windows NT 6.1, Windows NT 6.2"

    Memory consumption
    Roll.... 16192
    EM...... 620096320
    Heap.... 0
    Page.... 40960
    MM Used. 572736240
    MM Free. 38945296

User and Transaction

    Client.............. 400
    User................ "BATCH"
    Language key........ "E"
    Transaction......... " "
    Transactions ID..... "6D10D3E2F56AF16EA87D001C23C3FCC3"

    Program............. "SAPLSTXC"
    Screen.............. "SAPMSSY0 1000"
    Screen line......... 6

Information on where terminated
    Termination occurred in the ABAP program "SAPLSTXC" - in "OTF_APPEND".
    The main program was "SD70AV3A ".

    In the source code you have the termination point in line 136
    of the (Include) program "LSTXCOTF".
    The program "SAPLSTXC" was started as a background job.
    Job Name....... "Z_EMAIL_COMMERCIAL_INVOICE"
    Job Initiator.. "BATCH"
    Job Number..... 23300301

Thanks,

Kavitha

[Nibu]

Kavitha,

This dump is with resource utilization issue only.

Need to optimize the parameters specially memory one. I advice to restart soon to get effect of above changes .Let me see if any other relevant note for parameter optimization.

[Former Member]

I appreciate your help. Unfortunately, I could restart only over the weekend. Please let me know fi you find anything for the third dump.

Thanks,

Kavitha.

[Nibu]

Kavitha,

Hope you have checked notes 20527    and note  369726   .\

I would tune the memory parameters and restart system in  such a situation. Restart after tuning will solve your issue .

Regards,

Nibu Antony