Basis administrator guide

8/13/2019 Basis administrator guide

http://slidepdf.com/reader/full/basis-administrator-guide 1/28

evel 2 Training

Table of Contents

No Topic Tasks Page

1Lock Entries(SM12)

Check and analyze unreleased Database Locks2

2Update records(SM13)

Check and analyze failed database updates4

3System Log(SM21)

Check and analyze SAP System Lo for any critical lo entries!

4Background o!s(SM3")

Check and analyze failed Background Jobs to determine the cause of the

termination11

"#orkprocess(SM$%)

Check and analyze the System #ork$Process o%er%ie& for errors as &ell asthe CP' usae of the &ork$process

13

(Printer &ueues(SP%1)

Check and analyze failed Print )obs1*

* Bu''ers (ST%2)

Check and analyze buffer statistics and s&aps2+

!BP umps(ST22)

Check and analyze SAP A,AP Short Dumps2"

207623304doc 30!01!201



1. Check and analyze unreleased database locks (SM12)

A -lock. is a mechanism that pre%ents other users from chanin the record on &hich you are &orkin/ 0he eamplebelo& illustrates the importance of usin this function/

/ You are changing a customer mailing address, while someone is simultaneously changing the customer

telephone number. You first save your change; then the other person saves his or her change. The othe person’s change overwrites your change, and your change will be lost.

1/ n the Command field enter transaction S512 and choose nter6or from the SAP standard menu choose 0ools 7 Administration 7 5onitor 7 S512$Lock entries8/

2/ n Client enter 9/3/ Clear the 'ser name field/4/ Press nter/"/ n the 0ime column look for locks from pre%ious days/

*utput +

207623304doc 30!01!201



Analysis (SM12) :

• 0he easiest &ay to locate for locks is to look for locks from prior days. 0hese locks are problematic because it

prevents access or changes to the locked record.

,auses o' unre-eased -ock entries +

1/ Sudden po.er 'ai-ures

2/ 'ser &as “disconnected” from the network and the R/3 System/

3/ Pro!-ems pre/enting Update f a problem is pre%entin the update the locks enerated by the update &ill not be released/ Locks set by theupdate function are maintained by the system until the database change has been processed or terminat

prematurely. Check transaction S513 for further details on the update problems/

4/ Premature SP0U termination/f a user s&itches off the PC &ithout first loin off or if the SAP:' proram is terminated prematurely forsome reason the user may remain loed onto the SAP System/ 0he locks held by the user &hen the probleoccurred are not released/

e-easing te -ock +

• The following process can be followed to release a lock

!. "re there any processes running under the user !#$ % Transaction S&'(

!!. "re there batch )obs running under the user !#$ % Transaction S&3*

!!!. "re there any updates in process for that user !#$ %Transaction S&+3

Check if there is any u"dates in "rocess for this user

iv. !s the user logged on any of the servers$ % Transaction S&,- or Transaction "(

• 0heck when the user was last active in the system if you can see the user under SM04. If the user was not a

for a long time, he or she may have shut down the PC without completing his/her wor or S!P"#I may haveterminated prematurely. $ou can release the lock by logging off the user %under SM04& 'ut mae sure there isactivity using the user(s I) %!nswers are *+ for the uestions i - iii&.his will release the lock . owever, you havdelete the lock if you still see loc entries after logging off the user.

e-eting a -ock +

• Deletin a lock is a danerous task/ Do not delete a lock &ithout checkin first to see if it is bein used/ f you del

lock that is in use you risk corrupting the database 1data loss 2 inconsistencies. ;nce you kno& that there acti%ity usin the user<s D %answers are *+ for the uestions %i iii&& select the lock entry for deletion/ =rom the

menu bar choose ock entries 4 #elete/

0lear only one lock entry at a time. #o not use the mass delete option 1 1oc entry → )elete all&. This

option will delete all the locks5 not )ust the ones for the user you have selected /

207623304doc 30!01!201



2. Check and analyse failed database updates (SM13)

#n u"date terminate $or failed u"date% is an u"date to the database that failed &hese terminates occur when a user en

or transaction is not entered or updated in the database.

'or "erformance reasons( the database u"date is done in an asynchronous mode. )n this mode( the user continues to *

*hile the system takes o+er the u"date "rocess and *aits for the database u"date to com"lete

)n a synchronous mode( users *ould ha+e to *ait until the database has successfully u"dated before they could conti

to *ork

Check the system for failed updates se%eral times a day/ Durin a dayshift the checks can be distributed>? =irst thin in the mornin? Late mornin? arly afternoon? Late afternoon

• n the Command field enter transaction S513 and choose nter 62efer )iagram8

6or from the SAP standard menu choose 0ools 7 Administration 7 5onitor 7 S513$'pdate8/

• n Client enter 9/

• n 'ser enter 9/• 'nder Status select All/

• n =rom date chane the date to pre%ious day/

• Choose

• n the Status column look for entries &ith an Err4 0hese entries are failed updates or update terminates/

207623304doc 30!01!201



207623304doc 30!01!201



Analysis (SM13) :

Updates .it 5Err6 status can !e caused !y te 'o--o.ing +

i. #atabase overflow Database table has reached its ma6 e6tents causin the updates to be stopped@delayed/ :o to SAPD,A and

add table space to the table that is runnin critical 6usually +B8/

ii. 7ot enough free space in "rchive directory. Chec availa'le free space in the archive directory.

iii. Server disconnected from network.erify if update status is acti%e as sho&n belo& >

f status is not acti%e troubleshoot for network problems and make sure the ser%er is in the net&ork/

Change back the status to acti+e

iv. 8rogram errors

• Double$click on an entry &ith an 9rr status/

207623304doc 30!01!201



• 0his screen sho&s in &hat module 1&od.name and &here in the process 1&od.!# that the update terminate

occurred/

• Eo& double click on the entry &ith error the output &ill look like >

• 0he abo%e eample tells you a =;F5 hence a SAPScript is not acti%ated/ Additionally the =;F5 in Guestion is

H9 or customer =;F5/ Contact the =unctional Area pert to determine &hat =;F5 to acti%ate or transport to thsystem/

E;0> Eot all update error solutions are found this easily or Guickly/ Iou may ha%e to di deeper 1S&:+ Systemog5 ST:: #ump "nalysis5 #;(: #; Storage5 database alert log and &ork &ith the =unctional Area pert resol%e the issue/

207623304doc 30!01!201



• =irst ask the user to re<key the data/ f the user can re$key then it is okay to delete the update record %update

records 3 delete 3 single&. f the oriinal &ork &as not posted the user may be able to repost/ f the oriinal &ork posted but there is a missin final step the user &ill ha%e to re%erse the document and then repost/

f the user cannot re$key %erify the fi really &orked/ 0hen you can use the 'pdate Aain function to reprocess a update/ ,e certain that no other chanes &ere made to the database obJect after the failed update occurred/

0he loner you &ait after the update terminate has occurred the more difficult it is for users to remember &hatthey did &hen the update terminate occurred/ f you &ait too lon the user &ill not remember/ Iou mihtconsider configuring an “event log monitor” to page you when an update terminate occurs / 0his stepreduces the need to constantly check transaction S513/ t also reduces the eposure bet&een the time theupdate terminate occurs &hen you find out about it and &hen you can et to the user/ 0he follo&inmessae appears> -Iou ha%e epress mail in you inbo/.

#o not attempt to reapply the failed update= 0here are conditions under &hich this reapplication can leadto corruption of the database.

207623304doc 30!01!201



3. Check and analyze SA syste! lo" (SM21)

0he system lo is the F@3 System<s lo of e%ents errors problems and other system messaes/ 0he lo is importantbecause unepected or unkno&n &arnins and errors could indicate a serious problem/ 0he ability to properly monitosystem lo comes &ith eperience/ ;%er time you &ill become familiar &ith &hat lo entries -normally. appear in yousystem lo and pick out the unusual ones that need in%estiation/

*ptions escription

System log entries imported Sho&s ho& many lo entries the system has read from the lo file/ #hen you firstenter the System Lo initial screen this field is set to +/

Reread system log Choose 2eread system log to read the lo/ 0he system then reads in entries fromlo file so that you can display them/ ;y default5 the system reads the log for thlast one to two hours.

Redisplay only Choose 2edisplay only to %ie& the last system lo you displayed/ f you like youuse the Selection options alon &ith this button to refine the old system lo dat

&ithout re$readin the lo/

Read in Sysog 'se this option if you &ant to retain the data from this last read but &ant to rereadsystem lo &ith different selection criteria/ 0his option lets you mi the informationan oriinal lo access &ith a second lo access into one list/

207623304doc 30!01!201



Procedure +

• n the Command field enter transaction S521 and choose nter / 6refer diaram8

• nter the beinnin date and time that you &ant to re%ie& from the lo in 5rom date/time/ Iou can also enter an e

date and time if you &ant to %ie& a specific time period/

• Choose 2eread system log /

0o make re%ie&in the lo easier under Pro'lem classes select one of the follo&in one at a time> K Pro'lems only K Pro'lems and warnings K !ll messages

*utput +

207623304doc 30!01!201



Analysis (SM21) :

1/ Look for unusual entries. ,ut before you can reconize the unusual entries you &ill need to become familia&ith -normal. entries/ 9rrors are in red and pink5 and warnings are in yellow.

2. Iou can display detailed information on a specific entry by selectin the entry and choosin 9dit #etail

'y double clicking on the error message.

3. 'se 9dit "naly>e errors to display a detailed error analysis in the detailed %ie& if short dumps or runtim

errors ha%e occurred/

Iou can use the System 1og → Sort function to sort a lo report by %arious criteria/

207623304doc 30!01!201



#. Check and analyze failed back"round $obs (SM3%)

,ackround Jobs are batch Jobs scheduled to run at specific times durin the day/ f you are runnin critical Jobs you to kno& if the Job failed because there may be other processes acti%ities or tasks that depend on these Jobs/

1/ n the Command field enter transaction S53* and choose nter

2/ n )ob name enter 9 to et all Jobs/

3/ nter one of the follo&in options>? 9 6for all users8? 'ser D that the batch Jobs run under

6to limit the display to those scheduled under a specific user D in 'ser name8/

4/ 'nder )ob status select>? Acti%e? =inished? Canceled

"/ n =r/ enter a start date/

(/ n 0o enter an end date/

*/ n after e%ent choose and select 9/

!/ Choose ecute/

207623304doc 30!01!201



Analysis (SM37) :

• Look for failed or cancelled )obs/ Analyze &hy Jobs failed or &ere cancelled and make the necessary correction

analyse you should ha%e a list of all the critical )obs that are scheduled to run/ =or each of these Jobs youshould ha%e a list that sho&s>

i. ?hen the )obs are scheduled to run

ii. The e6pected run time

iii. "n emergency contact 1names and phone numbers for )ob failure or problems

• Eet you ha%e to check the )ob log /

0o check a Job lo>

+. Select the )ob.:. 0hoose @ob log.3. 0heck )ob performance and record run times.

Compare it &ith your list/ A deviation from the usual run time on a Job may indicate a problem and should bein%estiated/

207623304doc 30!01!201



&. Check and analyze syste! 'orkprocessoerie' errors (SM&*)

Process o%er%ie& transactions allo& users to %ie& the status of &ork processes and monitor for problems/ 0ransactioS5"1 is a central transaction from &hich you can select the instance to monitor/ S5"1 starts transaction S5"+ for eapplication ser%er &hich is used for a system &ithout application ser%ers/

0ransaction S5"+ is one place to look for Jobs or prorams that may be -hun. &hich maybe indicated by lon run tim

1/ n the Command field enter transaction S5"1 and choose nter

6choose 0ools 7 Administration 7 5onitor 7 System monitorin 7 S5"1$Ser%ers8/

2/ Select the instance you &ant to %ie&n the Command field enter transaction S5"+ and choose nter

6choose 0ools 7 Administration 7 5onitor 7 System monitorin 7 S5"+$Process o%er%ie&8/

207623304doc 30!01!201



Types o' .ork processes+

#ork Process Type Use

1 Dialo 6DA8 ecutes dialog programs 1";"8

2 'pdate 6'PD8 Asynchronous database changes 6is controlled by a C;550 #;F statement in a di&ork process8

3 ,ackround 6,:D8 ecutes time$dependent or e%ent$controlled background )obs

4 nGueue 6EM8 ecutes locking operations 6if SAP transactions ha%e to synchronize themsel%es8

" Spool 6SP;8 8rint formatting 6to printer file or database8

207623304doc 30!01!201



207623304doc 30!01!201



Analysis (SM50) :

• ?ork processes in 8R!A mode

f you see &ork processes in 8R!A mode you need to analyze your memory manaement strateies and ser%er profile parameters/ Private mode is usually an indicator of serious or comple6 problems.

f the F@3 &ork dispatcher determines your proram is too lare for con%entional memory allocation or reGuires staddressin the &ork process &ill be placed in private mode/ Additionally programs with comple6 reBuiremeor improper coding techniGues can confuse the 2/6 memory managers and in%oke the pri%ate mode for relati%e

small tasks/ Pri%ate mode can also result from systemic overloading of e6tended memory 6that is too manyreGuests for similar allocations8 and a host of other conditions/

• The following parameters 1related to workprocesses can be ad)usted with t6n RC+( according to the nee

of the organi>ation

rdisp7.p8no8spo Number of spool work processes

rdisp7.p8no8!tc Number of background work processes

rdisp7.p8no8en9 Number of lock work processes

rdisp7.p8no8dia Number of dialog work processes

rdisp7.p8no8/! Number of update work processes

rdisp7.p8no8/!2 Number of update work processes for V

rdisp7ma:8.prun8time !a"imum run time for dialog work processes#default $ %&& seconds'

207623304doc 30!01!201



+. Check and analyze failed print $obs (S*1)

0he spool is SAP<s output manaer/ Data is first sent to the F@3 spool and then to the operatin system for printin/ 0may be problems &ith the printer at the operating system or S"8 level / 0hese problems need to be resol%edimmediately for time$critical print Jobs 6for eample checks in%oices shippin documents etc/8 or there may be anoperational impact/

• n the Command field enter transaction SP+1 and choose nter >

• nter 9 in the NCreated by< field/

• Set the NDate created< field to for eample a &eek ao or to any other date rane to check for other problem

0he rane of data &ill depend on your installation/ f you enerate hundreds or thousands of spools a day yo&ould choose e%ery day/ 0his data rane &ould be much shorter possibly only t&o days/

• Delete information in Client/

• Press =! to eecute

207623304doc 30!01!201



*utput +

Analysis (SP01) :

• n the NList of Spool FeGuests< screen scroll throuh the display and check the status of each spool reGuest

under the S0A0'S column/

• Look for Jobs &ith an error in the ;utput Status column/

• #ouble click on the 9rror.

207623304doc 30!01!201



• Fe%ie& the error/

• =rom this point troubleshootin depends on the specific problem/

• Dse the log to investigate the problem/

,ommon pro!-ems +

• "ctive spool )obs that have been running for over an hour /

0hese lon runnin Jobs could indicate a problem &ith the operatin system spool or the printer/

• Spoo- data!ase a-most 'u--

Fun spool reor in proram SP*%%;1 6Deletes old print jobs - sugg. older than 7 days)/ Can be schedto be run &eekly/

207623304doc 30!01!201



%. Check and analyze buffer statistics and s'aps (ST*2)

SAP F@3 instance buffers are memory areas of an application ser%er instance/ 0hey contain data and proram code is freGuently used by all &ork processes/ 0he SAP F@3 instance buffers are important for a hih interacti%e performan0he buffer tune summary transaction 6S0+28 displays the F@3 buffer performance statistics/ t is used to tune bufferparameters of F@3/

0he access to buffered data that is stored in the main memory of the application ser%er is much faster than the retrie%data from the database/ 0he buffer is also important because significant buffer swapping reduces performance/ Lunder Swaps for red entries/ Feularly check these entries to establish trends and et a feel for buffer beha%ior/

n the Command field enter transaction ST%2 and choose nter 6or from the SAP standard menu choose

0ools $7 Administration $7O5onitor $7OPerformance -3 7Setup/8uffers -3S09-8uffers&.

*utput +

207623304doc 30!01!201



Bu''er types +

0hese are the important buffer types>

0his buffer contains table and field definitions of the A,AP dictionary/ 0he database acceaents of a &orkprocess consult the repository buffer before accessin a specific databastable to detect &hether the contents of the table are buffered/ 0he repository buffer is alsokno&n as nametab and consists of the four shared buffers 00A, =0A, FC and shortnametab/

0able buffers 0hese buffers store the content of database tables/ 0here are t&o types of table buffers>

partial and eneric/ Partial table buffers store sinle table records or keys/ :eneric tablebuffers hold seGuences of records or e%en all records of sinle tables/

8rogram buffer 0his buffer stores the compiled and thus eecutable %ersions of A,AP prorams/ As the&hole business loic and application processin of the SAP F@3 modules is based on A,prorams this buffer is very important / 0here is a least recently used 6LF'8 alorithmimplemented for reusin the proram buffer/

SAPui buffers 0here are t&o buffers that store SAPui obJects >

Presentation buffer $ also kno&n as Screen or Dynpro buffer contains dynamically creatSAP :' screens/

5enu buffer $ contains :' elements such as menu and button definitions/

9 0here are some more buffers for specific services such as dispatcher5 message5 spool , and enBueue and for thadministration of the different SAP F@3 memory areas such as roll pain and tended 5emory/

Bu''er attri!utes +

,uffer Guality 0his %alue describes the buffer hit rate in terms of database reBuests/ An applicationreGuest can demand se%eral sinle database reGuests/ 0he buffer Guality is the ratiobet&een the number of avoided database reBuests and the number of all

database reBuests. 0he buffer Guality is more important than the hit rate because thebenefit from the buffer is calculated &ith &eihted reGuests/

Allocated size 0his %alue specifies the amount of shared memory in , that is allocated by the buffer/0he allocated size is independent of the current usae of the buffer because the bufferallocates the &hole amount of memory accordin to its confiured size durin the startof the instance/

=ree space 0his %alue pro%ides the current free buffer space in , and percentae of the &holebuffer size/ t does not consider framentation/

Eumber of directories A directory entry is reGuired for e%ery buffered obJect that points to the memoryaddress &here the obJect is stored/ 0his %alue specifies the o%erall number and

number of a%ailable directory entries for the buffer/

207623304doc 30!01!201



Analysis (ST02) :

,efore a buffer can be tuned it has to be monitored for a sufficiently long period of time during normal operatio0he buffer monitor does not pro%ide meaninful %alues until after this period of time/ A ood %alue for the buffer Gualitdepends on the buffer type/

<it atio

0his %alue is the ratio bet&een the number of application reGuests that &ere successfully ser%ed out of the buffer andnumber of all reGuests/ 0he target value is E' percent and higher / Soon after startin the system this %alue is typiclo& because buffers are empty/ Restarting an instance should be avoided5 as all buffer contents are destroyed0hey are initialized and it &ill take a considerable time until they contain the same data aain/ 0he hit ratio &ill increaas the system is used and the buffers are loaded/ t usually takes a day to load the buffers that are normally used/

S.aps0his %alue represents the number of obJects that ha%e been s&apped out of the buffer in order to pro%ide space for neobJects since the start of the instance/ #e can %erify the s&aps incurred in one day by checkin on the istory/ Swapoccur when the necessary data is not in the buffer . he system has to retrieve the data from the data'ase. he swvalue is reset to :ero %0& when the system is restarted. ;hen 2/6 is restarted, the 'uffers are refreshed. his processmeans that the first person who accesses the 'uffered o'<ect will have a long response 'ecause the system must gethe data from dis and load it into the 'uffer. he second person will have a normal %uic& response time. his procerepeats until all normally used o'<ects are loaded into the 'uffer, which usually takes up to a day to accomplish.

0he aim is to a%oid s&appin and ha%e a ood buffer Guality/ 2 other columns to look at in S0+2 are the Free #ir entand Free space4

e'ragment system memory A computer<s memory beha%es similar to a hard disk/ As different prorams eecute they are loaded into and laterdeleted out of memory/ ;%er time like a hard disk the usae of the computer<s memory becomes framented &ithunused spaces scattered throuhout/ At a certain point you may ha%e sufficient -free memory. 6that is the total of allunused spaces8 but not a contiuous 6sinle8 piece of memory lare enouh to allo& certain prorams to eecute/ Atpoint those types of prorams attemptin to run that need contiuous memory &ill fail because they cannot be loadedmemory/

0his step reGuires stoppin restartin F@3 on all application and database ser%ers/

ara!eter Settin"s for SA ,uffers -

• ;uffer configuration

0he size of the indi%idual buffers can be tuned throuh the modification of instance profile parameters 1t6n RC0he sapp'par too- can be used to check the buffer confiuration for an instance/ ,est to run this &hen SAP isstopped to et a realistic info/ As user ?sid7adm you can issue the follo&in command specifyin the full path toinstance profile>

sappfpar pfQ@sapmnt@?SD7@profile@?nstanceKProfile7 check

207623304doc 30!01!201



. Analyzin" of A,A du!ps (ST22)

An A,AP dump 6also kno&n as a short dump8 is generated when a report or transaction terminates as the resultserious error. 0he system records the error in the system lo 6transaction SM9=8 and &rites a snapshot 6dump8 of thproram termination to a special table 6SNP8/ 0his transaction can also be called from the system lo 6transactionSM9=8/ An A,AP dump is used to analy>e and determine why the error occurred and take corrective action.

1/ n the Command field enter transaction ST22 and choose nter 6or from the S!P standard menu choose ools 7O !dministration 7OMonitor 7S99-)ump analysis&/

0here are t&o selection methods to display the list of dumps>? =or a simple selection oday or $esterday 6proceed to step 28? =or a free selection 6proceed to step "8

2/ 'nder *o. of short dumps if you see a %alue other than zero 6+8 in oday or $esterday dumps ha%e occurred thatneed to be eamined/

3/ Select oday /

4/ Press =!

6Proceed to step !/8

, Choose (election

207623304doc 30!01!201





207623304doc 30!01!201





( PRAKE;K=FKSPAC • Proram buffer size problem/ F@3 tried to load a proram but there &as no a%ailable

free space/ 0he user should &ait a fe& moments and try aain/ ;%er time F@3 &illrelease prorams to be cleared from the buffer/

• 0ry to increase the parameters A,AP@,'==FSH and @ or

A,AP@,'==FSHKPAF01/

* FASKRCP0;E • many reasons/

• Check SAP:' patches@%ersion

• ception condition TUV??W6XYZ[\W]V^?X\T raised/

! SEAPKE;KE#KE0FI • short dump could not be found in the database/

• may be caused by the follo&in>

$ 0able SEAP is full $ short dump &as not &ritten due to database problems $ if the SEAP 0able is full> Feoranize the table %ia

transaction S022 $7 :o to $7Feoranize

SIS05 CAECLLD • someone kill a process manually

1+ 05K;'0 • Feflects that the process that are bein runned by the users ha%e timed out/ A

protection for lon runnin dialog process/ / A proram may ha%e eceeded the maimum permitted runtime and has therefbeen terminated/

• ncrease the timeout %alue for rdisp/ma6GwprunGtime or simply assign 0 to this

parameters/

• 0ry to run in backround

• 0he proram THP=+12K#AKC;'E0IKFP;F0 T has eceeded the maimum

permitted runtime and has therefore been terminated/ 0ime limit eceeded/

D,=KFSMLKEALDKFSML FSML error 13 &hen accessin table TPA++++ T

C;E0KE;KE'5,F • 'nable to interpret T KT as a number

• 'nable to interpret TP T as a number

SIS05KCAECLD 0he proram TSAPD,PC T &as terminated manually/ 0he current proram TSAPD,PC T has been terminated by another mode

•

Documents

Basis administrator guide