You are on page 1of 4

ABAP Dumps

1) STORAGE_PARAMETERS_WRONG_SET

The problems with STORAGE_PARAMETERS_WRONG_SET are related to the


general restrictions of the 32bit OS.You can address only 4GB of virtual memory.
Each process in OS is running in its own context and can address max. 4GB.The
"heap" parameter: abap/heap_area_dia, abap/heap_area_nondia,abap/
heap_area_total are should be set to 2 GB.

a) Please use in the 'boot.ini' the switch '/3GB' and restart you whole computer as
described in the attached OSS notes:

SAP Notes
#552209 - Maximum memory utilization for processes on
#313347 - Windows NT, 2000, 2003: Editions and memory usage.

b)One way to avoid this problem is to try to add more criteria to your
report/program/transaction so that there will be less entries that need to be retrieved
from your database or buffers. This way, the system would not need to use up much
resources 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 parameter: rdisp/ROLL_SHM, rdisp/PG_SHM

d) Migrate to 64-bit OS (as per SAP Note 931024 (5) and SAP Note 996600)

2) TSV_TNEW_PAGE_ALLOC_FAILED

The error TSV_NEW_PAGE_ALLOC_FAILED means that more memory was request


because the program needed to expand an internal table, but not is
available. When Extended Memory is used up, the process will go into PRIV mode as
it starts using Heap Memory (or vise-versa). No other user will
be able to use this wp while it is in PRIV mode. If there is enough heap for it to finish,
you will not see the error .

SAP Notes
649327 Analysis of memory consumption.
20527 Runtime error TSV_TNEW_PAGE_ALLOC_FAILED
185185 Application: Analysis of memory bottlenecks
369726 TSV_TNEW_PAGE_ALLOC_FAILED

3) TSV_TNEW_OCCURS_NO_ROLL_MEMORY

The dump TSV_TNEW_BLOCKS_NO_ROLL_MEMORY usually means that the roll


buffer has been exhausted. Please check the usage of your roll buffer with ST02-
>history->page near the bottom to see ROLL BUFFER history. If the roll buffer has
been exhausted, you can increase the size with
parameter rdisp/ROLL_MAXFS, but make sure you have sufficient disk space to
handle the additional size of this buffer if it writes to disk.

SAP Notes
185185 Application: Analysis of memory bottlenecks

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 the dump of
LOAD_PROGRAM_LOST.

LOAD_PROGRAM_LOST are the result of the combination 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
(/nva01). By the way, if the PXA would be big enough then the user which do not
leave their transaction (e.g. va01) 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 trancode SAMT & regenerate the
program(s) that are listed in the dump. You can then do a $SYNC in the OK code
field in the affected application server, but the other application servers should not be
running. After the $SYNC, the other app servers can be brought up and the buffers
should then be in sync.

SAP Notes
5451 LOAD_PROGRAM_LOST
24824 Inconsistencies in a Program Load
10367 Termination LOAD_PROGRAM_LOST

5) CALL_FUNCTION_SIGNON_INCOMPL

The short dump CALL_FUNCTION_SIGNON_INCOMPL is typical of an RFC-Call


with incorrect or missing logon-data. So, we have to find out where the call is coming
from.

SAP Notes
171805 Determining RFC client when sign-on problems occur.
684788 Possible reason for CALL_FUNCTION_SIGNON_INCOMPL.
901256 Rabax "CALL_FUNCTION_SIGNO N_INCOMPL".
6) RFC_NO_AUTHORITY

This error mostly appears with SAPSYS 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, without SAPSYS your system will crash. 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.
Solution:

1- deactivate RFC authority check :set auth/rfc_authority_check to value '0' (zero) in


your profile and restart the server.
This is the least secure option as any authorization checks are disabled for all RFC
requests.

2- Assign full RFC authorities to the users who need to connect to your system via
RFC.
Please also check the user id provided in RFC connection (check from SM59) which
cause the dump RFC_NO_AUTHORITY. Make sure that this user has sufficient
authorizations .

SAP Notes
171805 Determining RFC client when sign-on problems
93254 RFC short dump RFC_NO_AUTHORITY
91980 Missing output of RFC short dump after login errors

7) SYSTEM_NO_TASK_STORAGE

For the error, please go to service market to download the latest patch for your SAP
Appl release and apply the patch. The latest patch would be useful for the problem.
The SYSTEM_NO_TASK_STORAGE is 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 effect
system_no_task_storage could also be a old
collector, this collector should not much more used. Use now, the new collector
(described in note 868063).

Please check the following

1. Check your settings match the recommendations note 146289.


2. Are ulimits set according to note #323816 referenced in note #146289?
3. With alot e.g. 8GB of RAM and if there is no additional instances on same host
then it should be possible to increase EM/TOTAL_SIZE_MB from 4096 towards the
RAM and even higher so that ztta/roll_extension can be reached, the swap space
should be set according to note #153641 for this.
SAP Note 146289 - Parameter Recommendations for 64-Bit SAP Kernel also ensure
that your ulimits are set as per SAP Note 323816 User limits on AIX referenced in
SAP Note 146289
Also please adhere to the guidelines as per SAP note 789477 Large extended
memory on AIX (64-bit) as of Kernel

146289 Parameter Recommendations for 64-Bit SAP Kernel


191801 AIX 64-bit with a lot of Extended Memory
445533 Lots of extended memory on AIX (64-bit)
581319 Signal 33 on AIX (64-bit only)
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 if the requested
function module is not found in table TFDIR.

Error causes:

(1) The function module does not exist (SE16 table=TFDIR)


(2) The buffered version of the TFDIR contains errors.

98458 SAPMSSY1, CALL_FUNCTION_NOT_FOUND

9) CALL_FUNCTION_SINGLE_LOGIN_REJ

SAP Notes
128447 Trusted/Trusting Systems
204039 Authorization check in trusted system

10) SYSTEM_CORE_DUMPED

Generally, SYSTEM_CORE_DUMPED is related to R/3 system kernel. Upgrade the


kernel patch to the latest.

SAP Notes
19466 Downloading SAP kernel patches