abap/buffersize issue with the dump PXA_NO_SHARED_MEMORY

[Former Member]

Hi Experts,

Could you please help me on this below issue.

We are getting many dumps "PXA_NO_SHARED_MEMORY" in ECC system.

So i have changed the abap/buffersize from 400000 into 600000 (KB) . But it is not reflecting in ST02 t.code.

In ST02 i have noticed that it is not reflecting the changed value i.e 600000(KB) .( Attached screenshot for reference)

Note : after i have changed i did restart also . But eventhough it is not reflecting .

Kindly help me on this on high priority .

Thanks

[madasamy_arunachalam]

Hi

Check the above OSS Note, given by SS.

Have you updated the parameter in the  instance profile ?

Looks like, you may missed the correct instance's profile & Do you have multiple app servers ?,

Memory parameters are instance specific, has to be updated in instance profile, check and confirm affected instance profile is updated and restarted ?, then this should be visible..

regards

Swami

[giri_ayyagari]

Hi Leelaprasad

Ps. double click on Extended memory on ST02 (SAP Memory) post screen shot.

-giri

[Sriram2009]

Hi

In which os /db ?

BR

[Sriram2009]

Hi

Could you refer the SAP KBA 1569318 - ST22 DUMP PXA_NO_SHARED_MEMORY

BR

SS

[Former Member]

Windows 2008 server

32 bit

[Sriram2009]

Hi

1. For the Dump refer the SAP Note

1790345 - PXA_NO_SHARED_MEMORY

2. In your production system memory & buffer parameters values are not defined in the right way. check the profile parameters as per the SAP Note
88416 - Zero administration memory management for the ABAP server

You have define the memory for 70%(For OS & SAP Application) +30% (Database usage)

BR

SS

[Matt_Fraser]

32-bit is part of the problem, although that's not the reason you are not seeing your parameter change reflected in ST02. I think Ross above probably has the right answer for that.

You should seriously consider migrating to 64-bit. It is actually very easy to do. If your hardware supports Windows 2008, then it probably also supports Windows 2008 64-bit. That does require a reinstall of the operating system (or system copy to new hardware), and you'll need to reinstall your DBMS in a 64-bit version. For SAP, the main thing you need to do is swap the kernel for a 64-bit version, and then you will probably want to adjust some of the memory parameters. Those adjustments will be so much easier, though, because 64-bit will give you more 'room' to play in.

How much memory does your server have?

Regards,

Matt

[former_member185239]

Hi Leela,

Can you run the transaction /$sync transaction.

Also do check the parameter if parameter is present in two diffrenet.

If you have done changes in DEFAULT.PFL changes then Instance profile will overwrite the value of DEFAULT profile.

With Regards

Ashutosh Chaturvedi

[Former Member]

what is the use of the $SYNC t.code , Because it is the Production system.

[Former Member]

Hi

Which profile did you change it in? Could you have perhaps changed it in your DEFAULT profile, but the instance profile has another value in it that is overwriting this?

Note that this is a per instance parameter and if you have multiple servers, you have to be on the relevant server (switch via SM51) to see. You can also run report RSPARAM from SE38/SA38 to see currently activated parameter values.

Regards

Ross