Dump PXA_NO_SHARED_MEMORY

erugu_suresh · ‎04-11-2015

Hi All,

We are getting dump PXA_NO_SHARED_MEMORY in Solution Manager 7.1

We have already increased the value of abap/buffersize parameter to 19000000.

Please can anybody suggest.

Thanks in advance.

Category Installation Errors

Runtime Errors PXA_NO_SHARED_MEMORY

Date and Time 10.04.2015 08:44:31

----------------------------------------------------------------------------------------------------

|Short text |

| 1900000 kilo bytes of shared memory for PXA not available. |

----------------------------------------------------------------------------------------------------

|What happened? |

| When starting the R/3 System, 1900000 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 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 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 1757164 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..... " " |

| SAP Basis Level. " " |

| |

| Application server... "XXXXXX" |

| Network address...... " " |

| Operating system..... "Windows NT" |

| Release.............. "6.1" |

| Hardware type........ "24x AMD64 Level" |

| Character length.... 16 Bits |

| Pointer length....... 64 Bits |

| Work process number.. 18 |

| Shortdump setting.... "full" |

| |

| Database server... "XXXXX" |

| Database type..... "MSSQL" |

| Database name..... "XXX" |

| Database user ID.. "XXX" |

| |

| Terminal.......... " " |

| |

| Char.set.... "C" |

| |

| SAP kernel....... 721 |

| created (date)... "Dec 4 2013 16:28:35" |

| create on........ "NT 6.0 6002 S x86 MS VC++ 16.00" |

| Database version. "SQL_Server_9.00 " |

| |

| Patch level. 201 |

| Patch text.. " " |

| |

| Database............. "MSSQL 9.00.2047 or higher" |

| SAP database version. 721 |

| Operating system..... "Windows NT 5.1, Windows NT 5.2, Windows NT 6.0, Windows |

| NT 6.1, Windows NT 6.2, Windows NT 6.3" |

| |

| Memory consumption |

| Roll.... 0 |

| EM...... 35048016 |

| Heap.... 0 |

| Page.... 0 |

| MM Used. 0 |

| MM Free. 0 |

----------------------------------------------------------------------------------------------------

|User and Transaction |

| Client.............. "###" |

| User................ "############" |

| Language key........ "#" |

| Transaction......... " " |

| Transaction ID...... " " |

| |

| EPP Whole Context ID.... " " |

| EPP Connection ID....... " " |

| EPP Caller Counter...... 0 |

| |

| Program............. "########################################" |

| Screen.............. " " |

| Screen Line......... " " |

| Debugger Active..... "none" |

----------------------------------------------------------------------------------------------------

|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 2121 of the module |

| "//bas/721_REL/src/krn/runt/abload3.c#9". |

| The internal operation just processed is " ". |

| Internal mode was started at "##############". |

----------------------------------------------------------------------------------------------------

Former Member · ‎04-15-2015

Hi Suresh,

Has this issue been fixed?

Matt_Fraser · ‎04-11-2015

That's a pretty big reservation for the program buffer. The error is basically saying that this much contiguous memory isn't available for the buffer. Have you tried just making it smaller? Also, I think you meant that you set it at 1.9 GB, not 19 GB, right? Try making it just 1 GB, i.e. 1 000 000, and restart, and see if that helps.

How much physical RAM does the system have, how large a pagefile, and what is the PHYS_MEMSIZE setting?

Cheers,

Matt

former_member189797 · ‎04-11-2015

Hello Suresh,

Please check the note :

307976 - PXA_NO_SHARED_MEMORY

1790345 - PXA_NO_SHARED_MEMORY

Regards,

Gaurav

Former Member · ‎04-11-2015

Sometimes reboot of the system fixes before tuning the params, some user session hanging and eating that memory, usually this type of dump does not show that in information. Can check those work process logs for the root cause.

HTH

rs,

Giridhar

srinivasan_vinayagam · ‎04-11-2015

Hi Suresh,

Your system current size of the PXA was set at 1757164 kilobytes. You can adjust your PXA size

44528STORAGE_PARAMETERS_WRONG_SET

51959STORAGE_PARAMETERS_WRONG_SET

PXA_NO_SHARED_MEMORY - ABAP Development - SCN Wiki

Regards,

V Srinivasan