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

Hello Kavitha,

Check the following notes:

44528	STORAGE_PARAMETERS_WRONG_SET
51959	STORAGE_PARAMETERS_WRONG_SET

Regards,

Eduardo Rezende

[Former Member · 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.