Solution : https://service.sap.com/sap/support/notes/147568 (SAP Service marketplace login required)
Summary :
The runtime error PXA_NO_FREE_SPACE mainly arises due to insufficient program buffer space, fragmented buffer configuration, or under-provisioned shared memory, identifiable in transaction ST22. To mitigate this, users can adjust buffer sizes and configurations (parameter abap/buffersize) across individual application servers, reduce fragment counts using abap/buffer_fragments, or perform system checks to ensure adequate memory availability. SAP Notes 1267828, 103747, and 97497 provide guidance on handling these settings effectively. In addition, kernel patches and SAP Notes like 175320, 121808, and 160875 address specific issues and improve system resilience.
Key words :
undocumented profile parameter abap/buffer_fragments, avoid illegal lock counter values', goto -> system -> system areas, transaction st02 displays swaps, pxa_no_free_space short dump occurs, short dump pxa_no_free_space occurs, error situation increasingly occurs, runtime error pxa_no_free_space occurs, invalid lock counter values, separate program buffer exists
Related Notes :
| 1267828 | Swaps in program buffer even though plenty of space is free |
| 129813 | Windows: Problems due to address space fragmentation |
| 103747 | Performance: Parameter recommendations as of Release 4.0 |
| 97497 | Memory Management Parameter (3.0/3.1) |
| 77833 | PXA_NO_FREE_SPACE, buffer size 4MByte |
| 4101 | PXA_NO_SHARED_MEMORY |