The SAP system at some point will generate ABAP dumps (various reasons). Viewable in ST22 transaction.
Here 5 commonly reported blogs that are generally encountered will be included.
These are by no means "the top 5" ST22 dumps that will be reported
by an SAP system as these obviously would change from system to system but perhaps you have
cataloged your top 5 and would like to share them. Please feel free to add comment and reply
to this blog with your findings.
Some background for the new reader on this topic.
In order to list the ABAP runtime errors that have occurred you must log on to the affected ABAP system.
Next thing to do is to run the ABAP Dump Analysis using the transaction code ST22.
On the this screen you have the options to define the selection criteria that is searched for the whole list of stored runtime errors.
It is also possible to call the most current runtime errors: by clicking on the 'Today' button in the Standard selection group box, the system displays a list of runtime errors for the current day in reverse i.e. the newest files first.
Then a list will appear of all of the runtime errors relevant to the selection criteria.
You can sort the list according to various criteria.
Ok, so everyone can now check on their system for any ABAP dumps and drill down for more information
into the selected dump reported.
Here is a selection of 5 common ST22 dumps encountered with a brief explaination and note. Do reply
to this blog with your top ABAP dumps (maybe your top 5) and share your experiences how you investigated
further and the impact they have on your daily administration tasks.
Some common ST22 dumps:
In most situations SYSTEM_CORE_DUMPED is related to the R/3 system kernel. As generally advised and in keeping with best practice upgrade to the latest available kernel patch to solve the issue (see note SAP 19466).
Detailed analysis of the coredump at the Kernel will provide more reasons behind the dump.
In brief the ST22 DUMP 'TSV_TNEW_PAGE_ALLOC_FAILED' simply indicates an
exhaustion of available SAP memory resources by a process.
When this DUMP is reported more memory was requested by the SAP system because the program needed to expand an internal table. The memory resource was not vailable. When the available Extended Memory is exhausted the process will enter PRIV mode (seen in SM50) and will start to use Heap Memory (local memory). This will happen in this order in Windows or vice versa in Unix. A process in PRIV mode locks out any other user to use the corresponding work process. If there is enough memory for the process to finish no error is reported.
SYSTEM_NO_TASK_STORAGE dumps are also address space/memory related.
The advised steps to take in relation to this dump is to refer to SAP notes 110172, 552209, 546361 for further details. This dump in general relates to 32-bit address space limitation regarding memory resources. On 32-bit platforms the long term solution is to use 64bit (regarding MS Windows see SAP note 996600).
Another possible cause for the dump SYSTEM_NO_TASK_STORAGE is running an old SAP collector. SAP do recommend to run with the latest available collector.
This dump is generally reported when there are insufficient authorization to login to the trusted system.
4 different error codes are related to CALL_FUNCTION_SINGLE_LOGIN_REJ
0 - Incorrect logon data for valid security ID.
1 - Calling system is not a Trusted Systemor security ID is invalid.
2 - Either user does not have RFC authorization (authorization object S_RFCACL), or a logon was performed using one of the protected users DDIC or SAP*.
3 - Time stamp of the logon data is invalid.
Refer the below SAP notes about CALL_FUNCTION_SINGLE_LOGIN_REJ dump:
986707 - No authorization to log on as a trusted system (RC=1)
128447 - Trusted/Trusting Systems
204039 - Authorization check in trusted system
In most situations where the ST22 DUMP PXA_NO_SHARED_MEMORY occurs there is not enough contiguous address space to create the buffer of size
xMB Approx (where x is size in mega bytes).
The SAP note 129813 may be relevant as some DLLs may be positioned that are stopping the creation of this large buffer on Windows platforms.
Also SAP note 307976 gives information about this dump type PXA_NO_SHARED_MEMORY.