SAP - runtime error @ st22

Hi Experts,

Please help me to resolve this error @ st22 "PXA_NO_SHARED_MEMORY" , my question is :

What particular memory or parameter I need to adjust?

I always reboot/restart my system in-order to refresh the memory. A huge thanks who will be able

to help me to solve this.

SAP Managed Tags:
SAP Business One

You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.

Comment

Accepted Solutions (0)

Answers (3)

Hi John,

If issue resolved,kindly close the thread.

Regards,

You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.

Comment

Hello Sir Gaurav,

Yes Sir , I will. This issue cannot be resolve right now , since we`re on the business operation and so it is only suggested to do if weren't on the operation because it needs a server restart/reboot. I can't do it at this time but I will be trying this solution, I had made an activity plan for parameter changing and changing of size of the paging file. I appreciated the way you help me Sir, thank you so much!

Hi,

you need to adjust the parameter abap/buffersize.

Follow the below link as well, in addition to the above suggested notes.

regards,

pavan

You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.

Comment

Hi John,

Please follow SAP notes 1790345 - PXA_NO_SHARED_MEMORY

307976 - PXA_NO_SHARED_MEMORY

746878 - Short dump PXA_NO_FREE_SPACE, buffer size of 4 MB

and make adjustments with parameter abap/buffersize

Regards,

Gaurav

You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.

Comment

Thanks Sir Gaurav!

Hi John

Could you share the full dump as text format attachment? you have to analysis the dump why its appeared?

Hello Sir Sriram;

Here`s the content of runtime error @ st22 :

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

Runtime Errors : PXA_NO_SHARED_MEMORY

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

What happened?

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

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"

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

I just want to know how to resolve this error.

Thanks Sir!

Hi John

Thanks for you info

In dump system environment & user & transaction information are require for that reason I asked full dump information as text format.

Runtime Errors : PXA_NO_SHARED_MEMORY

Date and Time: 01/13/2015 13:50:04

What happened?

When starting the R/3 System, 800000 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 adminis

You can use the ABAP dump analysis transaction ST22 to view and ma

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 y

R/3 System.

The current size of the PXA was set at 737764 kilobytes.

You can increase or decrease the PXA in the SAP profile. W

doing this, please refer to the relevent instructions in t

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 ma

find an interim solution in an SAP Note.

If you have access to SAP Notes, carry out a search with t

keywords:

"PXA_NO_SHARED_MEMORY" " "

"########################################" or

"########################################"

" "

If you cannot solve the problem yourself and want to send

notification to SAP, include the following information:

1. The description of the current problem (short dump)

To save the description, choose "System->List->Save->Lo

(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... "SAPRD-PRD-1"

Network address...... " "

Operating system..... "Windows NT"

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

Hardware type........ "16x AMD64 Level"

Character length.... 16 Bits

Pointer length....... 64 Bits

Work process number.. 6

Shortdump setting.... "full"

Database server... "SAPRD-PRD-2"

Database type..... "ORACLE"

Database name..... "prd1sap"

Database user ID.. "sapr3"

Char.set.... "C"

SAP kernel....... 720

created (date)... "Jan 16 2013 16:56:16"

create on........ "NT 5.2 3790 S x86 MS VC++ 14.00"

Database version. "OCI_10202_SHARE, 11.2.0.2.0 "

Patch level. 401

Patch text.. " "

Database............. "ORACLE 10.1.0.*.*, ORACLE 10.2.0.*.*, ORACLE 11.2.*.*.*"

SAP database version. 720

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

Heap.... 0

Page.... 0

MM Used. 0

MM Free. 0

User and Transaction

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

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

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

Transaction......... " "

Transactions ID..... " "

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

"//bas/720_REL/src/krn/runt/abload3.c#31".

The internal operation just processed is " ".

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

Hi John

On your Windows OS what is the size of Virtual memory? and also you can check the windows event viewer any error message " low virtual memory condition "?

Hi Sir Sriram,

On the ff. drives which I had allotted for paging file.

Drive I (label: Paging) : 70gb or 70000mb

Drive H (label: Installers) : 20gb or 20000mb

max. size for Drive I : 75000mb/75gb

Hi John

Thanks for your info,

1. Are you using Oracle Volume shadow copy services? during the Oracle DB backup ? you can refer the SAP KBA 1876395 - Huge virtual memory is used by oravssw.exe

Okay Sir Sriram. Thank you!

Ask a Question

Top Q&A Solution Author

User

Count

108