The purpose of this page is to clarify the understanding of PXA and Load inconsistencies.
abap/buffersize = size of the PXA shared memory [kB]
abap/pxa_cache = no. entries in the PXA cache (0 disables the cache, min = 1024, max = 16384, default depends on size of PXA)
abap/pxa_preload = max. percentage of the buffer space to be filled by the preload (default = 20), see note 1122370.
abap/buffer_fragments = no. of PXA fragments (valid: 1-16), default calculation has recently been changed, minimum fragment size: 7.20: 300000, 7.21: 500000.
The preload is configured by / operates on the following files in the work directory:
Each of those files contains a list of ABAP programs (one per line) in the following format:
x <technical program name>
Please also check 23642 - Description of pxanew and pxastat
Preload Processes during System Startup and Shutdown
PXA Runtime Errors
-PXA_DESTROYED (happens rarely)
Solution: Normally errors don’t come up again after re-initialization.
-PXA_HASH_LOOP (happens very rarely)
Solution: Assure protection is set (abap/pxa=..,protect)
If there are short dumps which could not be explained like•SYSTEM_RUDI_INVALID•RUNT_ILLEGAL_SWITCH•RUNT_INTERNAL_ERROR•CALL_FUNCTION_NOT_FOUND (with an invalid function module name)•SYSTEM_CORE_DUMPED•PXA_DESTROYED
it is very likely that program buffer memory has been overwritten.
Solution: Assure that the PXA protection is active and restart the server.
-PXA_NO_SHARED_MEMORY (happens rarely)
Solution: Reduce size of program buffer and restart
-PXA_NO_FREE_SPACE (happens more frequently)
Analysis: check sizes of program and fragment and number of fragments
Solution: Decrease number of fragments (profile parameter abap/pxa_fragment). If whole PXA too small increase its size