Runtime Error...

[former_member186775]

Hi team,

Can anyone help me in resolving "PXA_NO_FREE_SPACE" C short dump error

occurring frequently while executing Transactions like MIRO and MIGO etc?

for this I anlaysed the issue in ST22 ABAP dump analysisu2026where I found that

Current size =144868 kilobytes

And the program is requesting memory= 1837056

Largest and contiguous Memory chunk = 1421312 bytes

I checked the Profile file in which it is given as u2026.

SAPSYSTEMNAME = CPD

SAPGLOBALHOST = windows

SAPSYSTEM = 99

INSTANCE_NAME = DVEBMGS00

DIR_CT_RUN = $(DIR_EXE_ROOT)\$(OS_UNICODE)\NTI386

DIR_EXECUTABLE = $(DIR_INSTANCE)\exe

PHYS_MEMSIZE = 512

rdisp/wp_no_dia = 6

rdisp/wp_no_btc = 3

icm/server_port_0 = PROT=HTTP,PORT=80$$

#----

---

1. SAP Messaging Service parameters are set in the DEFAULT.PFL

#----

---

ms/server_port_0 = PROT=HTTP,PORT=81$$

rdisp/wp_no_enq = 1

rdisp/wp_no_vb = 1

rdisp/wp_no_vb2 = 1

rdisp/wp_no_spo = 1

DIR_CLIENT_ORAHOME = $(DIR_EXECUTABLE)

So in this file its stating phys_memsize as 512 in Tcode ST22 its been

Suggested to increase the PXA size.

Error analysis

Unable to load a program of 1837056 bytes.

The PXA ('program execution area') was too small to hold all

currently active programs for all users.

At present, the size of the PXA is set at 144868 Kbytes.

The largest contiguous and unlocked memory chunk has 1084416 bytes.

Information on where terminated

Termination occurred in the ABAP program "SAPLARFC" - in "ARFC_BP_REQUEST".

The main program was "SAPLMIGO "

In the source code you have the termination point in line 25

of the (Include) program "LARFCU07".

Can anyone tell me how to set parameters for this PXA size and also how to

Set abap/buffer sizeu2026.etc?

Hard disk capacity of server =640GB

RAM =4GB

[Former Member · Accepted solution]

Hi Manju,

Please increase your system buffer size in the parameter i guess it starts with abap/buffersize. SAP Notes are also helpful.

Feel free to update any issues.

Raghunandan

[Former Member]

Hi,

Also check the SAP NOTE 307976.

It may help you.

Thanks

Rama

[Former Member]

Hello,

Please read SAP note 147568. You will find possible causes and solution.

Best regards,

Olivier