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_member211576]

Hi Kavitha,

   I have seen a lot of same messages before. In your message, you limit your system with(abap/heap_area_dia =2000000000) so if your dialog process use more than 2GB memory(EM...... 2002743520). It caused ABAP dump: PXA_NO_SHARED_MEMORY.

  You can increase abap/heap_area_dia = 8,000,000,000 to 8GB if you want your dialog process use more memory. Beware this may cause more  PXA_NO_SHARED_MEMORY errors if there are already two dialog processes consumed 8GB memory because you have only 16GB memory in total.