PXA_NO_SHARED_MEMORY

[former_member196664]

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_member184473 · Accepted solution]

Hello Kavitha,

Check the following notes:

44528	STORAGE_PARAMETERS_WRONG_SET
51959	STORAGE_PARAMETERS_WRONG_SET

Regards,

Eduardo Rezende

[former_member196664 · Accepted solution]

Hi,

Eduardo,

I am mostly getting PXA_NO_SHARED_MEMORY than STORAGE_PARAMETERS_WRONG_SET. Copying full dumps here.

I am copying full dump here.

Short text
    1300000 kilo bytes of shared memory for PXA not available.

What happened?
    When starting the R/3 System, 1300000 Kbytes of storage space
    was required for the ABAP/4 program buffer (PXA), but this
    was not available.

    The system was started as an emergency system and is not fully
    operational.
    It is intended only for display and to eliminate errors.
    Under no circumstances should it be used for production
    purposes.

What can you do?
    The system was started as an emergency system and is not fully
    operational. It is intended only for display to eliminate errors.
    Under no circumstances should it be used for production
    purposes.
    used in production.

    Note which actions and input led to the error.

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

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

Error analysis
    The error probably occurred when installing the
    R/3 system.
    The return code of the SAP shared memory control was 1.
    The error reported by the operating system is:
    Error number..... 0
    Error text....... "No error"

How to correct the error
    Report the error to the group responsible for installing your
    R/3 System.

    The current size of the PXA was set at 1201980 kilobytes.
    You can increase or decrease the PXA in the SAP profile. When
    doing this, please refer to the relevent instructions in the
    installation manual.

    You can use the utility program 'ipclimits' to display the
    available system resources.

    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:

    "PXA_NO_SHARED_MEMORY" " "
    "########################################" or
     "########################################"
    " "

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

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

    Database server... "SAPECCPRD"
    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.... 0
    EM...... 0
    Heap.... 0
    Page.... 0
    MM Used. 0
    MM Free. 0

User and Transaction

    Client.............. "###"
    User................ "############"
    Language key........ "#"
    Transaction......... " "
    Transactions ID..... "94CAD1E27AD8F1E2A87D001C23C3FCC3"

    Program............. "########################################"
    Screen.............. " "
    Screen line......... " "

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

    In the source code you have the termination point in line 0
    of the (Include) program "########################################".
    The error occurred during initialization of the R/3 System.

Internal notes
    The termination was triggered in function "ab_pbinit"
    of the SAP kernel, in line 1909 of the module
     "//bas/700_REL/src/krn/runt/abload3.c#58".
    The internal operation just processed is " ".
    Internal mode was started at "##############".

Second dump:

Short text
    The system is configured incorrectly.

What happened?
    The current program had to be terminated because of an
    error when installing the R/3 System.
    The program had already requested 1731363904 bytes from the operating
    system with 'malloc' when the operating system reported after a
    further memory request that there was no more memory space
    available.

What can you do?
    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.

    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,00
    000.

    Then restart the SAP system.

Error analysis
    When the program was running, it was established that more
    memory was needed than the operating system is able safely
    to provide. To avoid a system crash, you must prevent this
    situation from occurring.

How to correct the error
    Report the error to the group responsible for installing your
    R/3 System.

System environment
    SAP-Release 700

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

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

    Terminal................. "Y-PLAZA2"

    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.... 6221152
    EM...... 2002743520
    Heap.... 1731363904
    Page.... 57344
    MM Used. 3638218400
    MM Free. 92800688

User and Transaction

    Client.............. 400
    User................ "YPLAZA"
    Language key........ "E"
    Transaction......... "MB51 "
    Transactions ID..... "81C7D1E29F07F16BA87D001C23C3FCC3"

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

Information on where terminated
    Termination occurred in the ABAP program "RM07DOCS" - in "DATA_SELECTION".
    The main program was "RM07DOCS ".

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

Please note that below are my parameter settings that are related to above 2 dumps. I have planned to reduce abap/buffersize to 1250000. Is that fine? How to adject these parameters to avoid these dumps?

abap/heap_area_dia =2000000000

abap/heap_area_nondia = 0

abap/heap_area_total = 17173577728

abap/heaplimit = 40000000

abap/buffersize = 1300000

Thanks,

Kavitha.

[Former Member]

Hi kavitha,

        You dnt have enough sapce in u r shred memory..,you can decrease ur abap/buffer size ,it will resolve u r problem..

Thanks

nani

[former_member196664]

Yes Nani, I decreased abap/buffer and increased required other parameter. It resolved my issue.

Thanks,

Kavitha Rajan.

[former_member211576]

Hi Kavitha,

   I have seen a lot of same messages before. In your message, you limit your system with(abap/heap_area_dia =2000000000) so if your dialog process use more than 2GB memory(EM...... 2002743520). It caused ABAP dump: PXA_NO_SHARED_MEMORY.

  You can increase abap/heap_area_dia = 8,000,000,000 to 8GB if you want your dialog process use more memory. Beware this may cause more  PXA_NO_SHARED_MEMORY errors if there are already two dialog processes consumed 8GB memory because you have only 16GB memory in total.

[Former Member]

Hi Kavitha,

Did u run the "sappfpar check" command from OS and see if there are any errors?

sappfpar check pf=<profile>

Regards,

RN

[former_member196664]

Hi RN,

I ran it and getting below result.

C:\Documents and Settings\prdadm>sappfpar check pf=PRD_DVEBMGS00_SAPECPAPP
sappfpar=>sapparam(2): fopenU("PRD_DVEBMGS00_SAPECPAPP","r"): No such file or di
rectory
sappfpar=>No Profile used.
sappfpar=>sapparam: SAPSYSTEMNAME neither in Profile nor in Commandline

================================================================================

==   Checking profile:     <no_profile>
================================================================================

Shared memory disposition overview
================================================================
Key:        1  Size:        2500 (   0.0 MB) System administration
Key:        2  Size:     6108428 (   5.8 MB) Disp. administration tables
Key:        3  Size:    13714400 (  13.1 MB) Disp. communication areas
Key:        4  Size:      503248 (   0.5 MB) statistic area
Key:        5  Size:        4096 (   0.0 MB) SCSA area
Key:        6  Size:   319488000 ( 304.7 MB) ABAP program buffer
Key:        7  Size:       14838 (   0.0 MB) Update task administration
Key:        8  Size:   134217828 ( 128.0 MB) Paging buffer
Key:        9  Size:   268435556 ( 256.0 MB) Roll buffer
Key:       11  Size:      500000 (   0.5 MB) Factory calender buffer
Key:       12  Size:     6000000 (   5.7 MB) TemSe Char-Code convert Buf.
Key:       13  Size:    60500000 (  57.7 MB) Alert Area
Key:       14  Size:     4400000 (   4.2 MB) Presentation buffer
Key:       16  Size:       22400 (   0.0 MB) Semaphore activity monitoring
Key:       17  Size:     2760892 (   2.6 MB) Roll administration
Key:       18  Size:      917604 (   0.9 MB) Paging adminitration
Key:       19  Size:    30000000 (  28.6 MB) Table-buffer
Key:       30  Size:        3072 (   0.0 MB) Taskhandler runtime admin.
Key:       31  Size:     1806000 (   1.7 MB) Dispatcher request queue
Key:       33  Size:    10240000 (   9.8 MB) Table buffer, part.buffering
Key:       41  Size:    25010000 (  23.9 MB) DB statistics buffer
Key:       42  Size:     7232992 (   6.9 MB) DB TTAB buffer
Key:       43  Size:    32534392 (  31.0 MB) DB FTAB buffer
Key:       44  Size:     7958392 (   7.6 MB) DB IREC buffer
Key:       45  Size:     4886392 (   4.7 MB) DB short nametab buffer
Key:       46  Size:       20480 (   0.0 MB) DB sync table
Key:       47  Size:     3073024 (   2.9 MB) DB CUA buffer
Key:       48  Size:      500000 (   0.5 MB) Number range buffer
Key:       49  Size:     2968344 (   2.8 MB) Spool admin (SpoolWP+DiaWP)
Key:       51  Size:     3200000 (   3.1 MB) Extended memory admin.
Key:       52  Size:       40000 (   0.0 MB) Message Server buffer
Key:       54  Size:     4202496 (   4.0 MB) Export/Import buffer
Key:       55  Size:        8192 (   0.0 MB) Spool local printer+joblist
Key:       57  Size:     1048576 (   1.0 MB) Profilparameter in shared mem
Key:       58  Size:        4096 (   0.0 MB) Enqueue ID for reset
Key:       62  Size:    85983232 (  82.0 MB) Memory pipes
Key:       63  Size:      409600 (   0.4 MB) ICMAN shared memory
Key:       64  Size:     4202496 (   4.0 MB) Online Text Repository Buf.
Key:       65  Size:     4202496 (   4.0 MB) Export/Import Shared Memory
Key:     1002  Size:      400000 (   0.4 MB) Performance monitoring V01.0

Nr of operating system shared memory segments: 40

Shared memory resource requirements estimated
================================================================
Total Nr of shared segments required.....:         40
Shared memory segment size required min..:  319488000 ( 304.7 MB)

Swap space requirements estimated
================================================
Shared memory....................:  999.0 MB
Processes........................:   29.0 MB
Extended Memory .................: 4096.0 MB
------------------------------------------------
Total, minimum requirement.......: 5124.0 MB
Process local heaps, worst case..: 16378.0 MB
Total, worst case requirement....: 21502.0 MB

Errors detected..................:    0
Warnings detected................:    0

[former_member188883]

Hi Kavitha,

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

Regards,

Deepak Kori

[former_member196664]

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_member196664]

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_member196664]

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