Professional Documents
Culture Documents
e
Top 10 ABAP Dumps... Print
Rajeev P Permalin
Business Card k
Company: Allianz Cornhill Information Services Share
Posted on Jul. 31, 2010 10:32 PM in Application
Server, SAP NetWeaver Platform, SAP Solution Manager
ABAP short dumps are something which trouble any SAP user (sometimes help the
user to understand the system needs better). We normally do a search for SAP
notes or contact SAP to solve these dumps. But hardly takes any chance
to understand the meaning of the dumps. Here I am listing some 'famous' ABAP
dumps and trying to explain what are they. Please note that the solutions provided
here may different from case to case. These should be used just as a 'first aid'.
1) STORAGE_PARAMETERS_WRONG_SET
b) Another way to avoid this problem is to try to add more criteria to your
report/program/transaction so that there will be fewer entries that need to be
retrieved from your database or buffers. This way, the system would not need to
use up much resource to complete the transaction. The query may have been
quite big already and the load cannot be accommodated. So please do add more
criteria or options so that there will less data to fetch.
c) To decrease the value of the parameters: rdisp/ROLL_SHM, rdisp/PG_SHM
d) Migrate to 64-bit OS (as per SAP Note 931024 and SAP Note 996600)
2) TSV_TNEW_PAGE_ALLOC_FAILED
4) LOAD_PROGRAM_LOST
The LOAD_PROGRAM_LOST error can occur when there are two or more versions
of a given program loaded into the buffer at any given time. This happens when
the program is changed by one user while it is still in use by another user. When a
user gets to the program that is having this problem and R/3 attempts to load the
generated version from the buffer, it sees that the version is not the most current
and tries to swap it out for the most current, but the load was lost from the PXA
buffer, hence it throws the dump of LOAD_PROGRAM_LOST. LOAD_PROGRAM_LOST
are the result of the combination of not enough PXA space + changes of programs
which are in use currently. A running program can't run with two different versions
of one program. Ask the users restart their transactions (/nST22). By the way, if
the PXA would be big enough then the user who does not leave their transaction
for weeks will not see the changes to this application until they restart the
transaction.
Other way to correct the error is you need to run transaction SAMT & regenerate
the program(s) that are listed in the dump. You can then do a $SYNC in the
command field in the affected application server, but make sure that the other
application servers are not running at that time. After the $SYNC, the other app
servers can be brought up and the buffers should then be in sync.
Please refer the following SAP notes:
SAP Note 5451 - LOAD_PROGRAM_LOST
SAP Note 24824 - Inconsistencies in a Program Load
SAP Note 10367 - Termination LOAD_PROGRAM_LOST
5) CALL_FUNCTION_SIGNON_INCOMPL
This error mostly appears with the user SAPSYS. The user SAPSYS is an internal
user, it is not a personally used ID in the R/3 system. However, all system errors
and ABAP programs are run via this user id. As per note 93254, since release 4.0
the parameter auth/rfc_authority_check is set on 1 per default. This means, as
long as you did not set it explicitly to value ‘0', any incoming RFC call is checked
as described in the mentioned note.
The common approaches which we can take on this dump are:
For this error, please go to service market to download the latest patch for your
SAP Application release and apply the patch. The latest patch would be useful for
the problem. The SYSTEM_NO_TASK_STORAGE is a known problem and related to
limitation of 32bit OS. Please see notes 110172, 552209, 546361 for details. As
long term solution you have to use 64bit Windows (Note 996600).The cause for
the dump SYSTEM_NO_TASK_STORAGE could also be an old sap collector. SAP
recommends using the updated collector version always.
The common approaches which we can take on this dump are:
1. Check your settings match the recommendations mentioned in SAP Note
146289.
2. Are ulimits set according to SAP Note 323816? (Referenced in SAP
Note 146289)
3. If there is no additional instances on same host then it should be possible to
increase EM/TOTAL_SIZE_MB from 4096 MB towards the RAM and even higher so
that ztta/roll_extension can be reached. Also the swap space should be set
according to SAP Note 153641 for this.
Please refer the following SAP notes:
SAP note 789477 - Large extended memory on AIX (64-bit) as of Kernel
SAP note 191801 - AIX 64-bit with a lot of Extended Memory
SAP note 445533 - Lots of extended memory on AIX (64-bit)
SAP note 581319 - Signal 33 on AIX (64-bit only)
SAP note 153641 - Swap space requirement for R/3 64-bit kernel
8) CALL_FUNCTION_NOT_FOUND
The error CALL_FUNCTION_NOT_FOUND is due to the fact that the program called
the function which doesn't exist in the library. Means the requested function
module is not found in table TFDIR. Also you may get this error if the buffered
version of the TFDIR contains errors. The error needs to attention based on the
function module. You may take a general approach mentioned in the SAP Note
98458.
Please refer the following SAP note:
SAP Note 98458 - SAPMSSY1, CALL_FUNCTION_NOT_FOUND
9) CALL_FUNCTION_SINGLE_LOGIN_REJ
This error usually comes when you don't have sufficient authorization to login to
the trusted system. This dump accompanies with 4 different error codes:
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.
Please refer the following SAP notes:
10) SYSTEM_CORE_DUMPED