Common ABAP Dumps (ST22) and troubleshooting in SAP Top ABAP Dumps… (ST22) ABAP short dumps are something which trouble any SAP user (sometimes help the user to understand the system needs better). e e normally do a search !or SAP notes or contact SAP to sol"e these dumps. But hardly ta#es any chance to understand the meaning o! the dumps. $ere % am listing some &!amous' ABAP dumps and trying to eplain what are they. they. Please note that the solutions pro"ided here may di!!erent !rom case to case. These should be used ust as a '!irst aid'. *) ST+,A-/PA,A0T,S/,+1-/ST The problems with the dump ST+,A-/P ST+,A-/PA,A0T,S/, A,A0T,S/,+1-/ST +1-/ST are mainly related to the general restrictions o! the 2bit +S. 3ou 3ou can address up to 4-B o! "irtual memory. ach process in +S is running in its own contet and can address ma. 4-B. the parameters which are related to &heap memory' ie5 abap6heap/area/dia7 abap6heap/area/dia7 abap6heap/area/nondia7 abap6heap/area/total abap6heap/area/total are should be set to 2 -B. 8ommon approaches which we can ta#e !or this dump are9 a) Please use in the &boot.ini' !ile the switch &6-B' and restart your whole computer as described in the below SAP 1otes9 SAP 1ote ::22;< = 0aimum memory utili>ation !or processes on 1T6in 2;;; SAP 1ote *4? = indows 1T7 1T7 2;;;7 2;;9 ditions and memory usage. b) Another way to a"oid this problem is to try to add more criteria to your report6program6transaction so that there will be !ewer entries that need to be retrie"ed !rom your database or bu!!ers. This way7 way7 the system would not need to use up much resource to complete the transaction. The @uery may ha"e been @uite big already and the load cannot be accommodated. So please do add more criteria or options so that there will less data to !etch. c) To decrease the "alue o! the parameters9 rdisp6,+/S$07 rdisp6P-/S$0 rdisp6P-/S$0 d) 0igrate to 45bit +S (as per SAP 1ote <*;24 and SAP 1ote <<;;) 2) TSC/T1/PA-/A+8/A%D The error TSC/1/PA-/A+8/ TSC/1/PA-/A+8/A%D A%D means that more memory was re@uested by the system because the program needed to epand an internal table7 but not is a"ailable. hen tended 0emory is completely used up7 the process will go into P,%C mode and it will start using $eap 0emory in case o! indows indows or "ice "ersa in case o! E1%F. +nce this enters into P,%C mode7 no other user will be able to use the corresponding wor# process. %! there is enough memory !or it to !inish7 you will not see the error. Please re!er the !ollowing SAP notes9 SAP 1ote 4<2? = Analysis o! memory consumption. SAP 1ote 2;:2? 5 ,untime error TSC/T1/PA-/A+8/A%D SAP 1ote *G:*G: = Application9 Analysis Analysis o! memory bottlenec#s SAP 1ote
) TSC/T1/+88E,S/1+/,+/00+,3 The dump TSC/T1/B+8HS/1+/,+/00+, TSC/T1/B+8HS/1+/,+/00+,3 3 usually means that the roll bu!!er has been ehausted. Please chec# the usage o! your roll bu!!er with ST;25I$istory5IPage. ST;25I$istory5IPage. 1ear the bottom o! the screen you can see ,+ BE, history. history. %! the roll bu!!er has been ehausted7 you can increase the si>e with parameter rdisp6,+/0AFS7 rdisp6,+/0AFS7 but ma#e sure you ha"e su!!icient dis# space to handle the additional si>e o! this bu!!er i! it writes to dis#. Please re!er the !ollowing SAP note9 SAP 1ote *G:*G: 5 Application9 Analysis Analysis o! memory bottlenec#s 4) +AD/P,+-,A0/+ST The +AD/P,+-,A0/+ST +AD/P,+-,A0/+ST error can occur when there are two or more "ersions o! a gi"en program loaded into the bu!!er at any gi"en time. This happens when the program is changed by one user while it is still in use by another
user. hen a user gets to the program that is ha"ing this problem and ,6 attempts to load the generated "ersion !rom the bu!!er7 it sees that the "ersion is not the most current and tries to swap it out !or the most current7 but the load was lost !rom the PFA bu!!er7 hence it throws the dump o! +AD/P,+-,A0/+ST. +AD/P,+-,A0/+ST are the result o! the combination o! not enough PFA space J changes o! programs which are in use currently. A running program can't run with two di!!erent "ersions o! one program. As# the users restart their transactions (6nST22). By the way7 i! the PFA would be big enough then the user who does not lea"e their transaction !or wee#s will not see the changes to this application until they restart the transaction. +ther way to correct the error is you need to run transaction SA0T K regenerate the program(s) that are listed in the dump. 3ou can then do a LS318 in the command !ield in the a!!ected application ser"er7 but ma#e sure that the other application ser"ers are not running at that time. A!ter the LS3187 the other app ser"ers can be brought up and the bu!!ers should then be in sync. Please re!er the !ollowing SAP notes9 SAP 1ote :4:* = +AD/P,+-,A0/+ST SAP 1ote 24G24 = %nconsistencies in a Program oad SAP 1ote *;? = Termination +AD/P,+-,A0/+ST :) 8A/E18T%+1/S%-1+1/%18+0P The short dump 8A/E18T%+1/S%-1+1/%18+0P is typical o! an ,858all with incorrect or missing logon5data. So7 we ha"e to !ind out where the call is coming !rom. Please re!er the !ollowing SAP notes9 SAP 1ote *?*G;: 5 Determining ,8 client when sign5on problems occur. SAP 1ote G4?GG 5 Possible reason !or 8A/E18T%+1/S%-1+1/%18+0P. SAP 1ote <;*2: = ,aba M8A/E18T%+1/S%-1+1/%18+0PN.
) ,8/1+/AET$+,%T3 This error mostly appears with the user SAPS3S. The user SAPS3S is an internal user7 it is not a personally used %D in the ,6 system. $owe"er7 all system errors and ABAP programs are run "ia this user id. As per note <2:47 since release 4.; the parameter auth6r!c/authority/chec# is set on * per de!ault. This means7 as long as you did not set it eplicitly to "alue &;O7 any incoming ,8 call is chec#ed as described in the mentioned note. The common approaches which we can ta#e on this dump are9 *. Deacti"ate ,8 authority 8hec#9 set auth6r!c/authority/chec# to "alue ';O (>ero) in your pro!ile and restart the ser"er. (This is the least secure option as any authori>ation chec#s are disabled !or all ,8 re@uests). . 2. Assign !ull ,8 authorities to the users who need to connect to your system "ia ,8. Please also chec# the user id pro"ided in ,8 connection (chec# !rom S0:<) which cause the dump ,8/1+/AET$+,%T3. 0a#e sure that this user has su!!icient authori>ations. Please re!er the !ollowing SAP notes9 SAP 1ote *?*G;: = Determining ,8 client when sign5on problems SAP 1ote <2:4 5 ,8 short dump ,8/1+/AET$+,%T3 SAP 1ote <*
2. Are limits set according to SAP 1ote 2G* (,e!erenced in SAP 1ote *42G<) . %! there is no additional instances on same host then it should be possible to increase 06T+TA/S%Q/0B !rom 4;< 0B towards the ,A0 and e"en higher so that >tta6roll/etension can be reached. Also the swap space should be set according to SAP 1ote *:4* !or this. Please re!er the !ollowing SAP notes9 SAP note ?G<4?? = arge etended memory on A%F (45bit) as o! Hernel SAP note *<*G;* 5 A%F 45bit with a lot o! tended 0emory SAP note 44:: 5 ots o! etended memory on A%F (45bit) SAP note :G**< 5 Signal on A%F (45bit only) SAP note *:4* = Swap space re@uirement !or ,6 45bit #ernel
G) 8A/E18T%+1/1+T/+E1D The error 8A/E18T%+1/1+T/+E1D is due to the !act that the program called the !unction which doesn't eist in the library. 0eans the re@uested !unction module is not !ound in table TD%,. Also you may get this error i! the bu!!ered "ersion o! the TD%, contains errors. The error needs to attention based on the !unction module. 3ou may ta#e a general approach mentioned in the SAP 1ote ation to login to the trusted system. This dump accompanies with 4 di!!erent error codes9 ; = %ncorrect logon data !or "alid security %D. * = 8alling system is not a Trusted System or security %D is in"alid. 2 = ither user does not ha"e ,8 authori>ation (authori>ation obect S/,8A8)7 or a logon was per!ormed using one o! the protected users DD%8 or SAP. = Time stamp o! the logon data is in"alid. Please re!er the !ollowing SAP notes9 1ote ation to log on as a trusted system (,8*) SAP 1ote *2G44? = Trusted6Trusting Systems SAP 1ote 2;4;< = Authori>ation chec# in trusted system *;) S3ST0/8+,/DE0PD -enerally7 S3ST0/8+,/DE0PD is related to ,6 system #ernel. Epgrade the #ernel patch to the latest may sol"e the issue. But without a detail analysis o! the core dump at the Hernel7 we cannot conclude the reason behind the dump. % would recommend contacting SAP !or this dump. SAP 1ote *<4 = Downloading SAP #ernel patches 11) PFA/1+/S$A,D/00+,3
%n most situations where the ST22 DE0P PFA/1+/S$A,D/00+,3 occurs there is not enough contiguous address space to create the bu!!er o! si>e 0B Appro (where is si>e in mega bytes). The SAP note *2
3ou will get a ile Cersion similar to9 ?*;;.2.<.*;<……?*;; means SAP-E% ?.*;……..2 means 8ompilation 2…….< means Patch le"el…….*;< is a build number (it is o! no use !or us) 0essage/Type/F Dump also occurs when proper date !ormat is not maintained in SE;* transaction o! the user who ha"e !aced this dump. %ncase you ha"e recei"ed a complaint !rom customer that he is recei"ing this dump while running some transactions7 please go to SE;* and chec# the date !ormat in the de!aults tab. %! there is any date !ormat other than DD.00.33337 please change that to this !ormat to a"oid this error *) FS+,T/1+T/1+E-$ 00+,3 0emory bottlenec# encountered by the program while sorting. *4) S3ST0/,+/%1/,,+, 1ot enough memory !or user contet. *:) S3ST0/1+/0+,/PA-%11ot enough SAP Paging 0emory. Set Mrdisp6pg/ma!sN to su!!iciently large "alue ( say 27;;; ).%! the problem eists e"en a!ter assigning this "alue then there could be a !ault in the program itsel!. *) ST/PA,A0T,/00+,3/+C,+ 1ot enough memory !or ST6-T Parameter (+therwise #nown as SPA6-PA 0emory ).Try etending the memory area with SAP pro!ile M>tta6parameter/areaN. *?) SAPSU/A,,A3/%1S,T/DEP,8 1umber range problem7 li#ely document number eists. *G) FS+,T/,%T/A%D %s related to dis# space. There is not enough dis# space !or the eternal sorting process in the sort directory. To a"oid this mo"e either the etract !iles (D%,/FT,A8T) or the sort !iles (D%,/S+,TT0P) to a separate directory with enough space.
