SAP Basis Tutorials Hi..In this th is blog am covering SAP Basis/netweaver concepts, mon itoring, administration, administration, performance tuning, SAP implementations, sample BASIS CVs an d FAQs. Please join as followers and please subscribe to get an updat u pdatee on new articles published. For SAP Training, alexander.durgaprasad@ gmail.com or contact Keylabs Bangalore(+'91-8861770545') Banga lore(+'91-8861770545') and Keylabs Hyderabad (+91-9550645679) and USA Contact Co ntact 908-366-7933: Training Link:http://sapbasisd Li nk:http://sapbasisdurgaprasad urgaprasad.blogspot.com/2011/09 .blogspot.com/2011/09/sap-basis-tr /sap-basis-training.html aining.html Hom e
A u t ho hor i sa t i on
A dm i n i st ra ra t io ion
Da t ab aba se
Per for m a n ce T u n i n g
FA Qs
Im pl em en t a t i on s
SAP BASIS/NETWEA VER/SECURI VER/SECURITY TY TRAINING TRAINING
Keylabs Trainin Like
189
SAP BASIS BASIS Demo - Keylabs Hy derabad derabad:: 11 11-July-20 -July-20 13 at 6 pM (Contact Hyderabad: +91-9550645679)
SAP Netweaver Demo in Keylabs Hyderabad : 19-July-2013 at 8 AM by Durga Durga prasad (Contact Hyderabad: +91-9550645679) SAP BASIS/N BASIS/Netweav etweav er/ er/Security Security /GR /GRC C 10 T raining in Keylabs Bangalore: +918861770545,
[email protected] - SAP BASIS Batch in Bangalore from fr om Aug 7 th. SAP BASIS/N BASIS/Netweav etweav er/ er/Security Security /GR /GRC C 10 T raining in Keylabs Hyderabad:+ Hyderabad:+91-
9550645679 9550645679 , h yd@keylabstra yd@ keylabstraining.com ining.com For SAP SAP Online T raining - All modu les: +1-908-366-7933(USA) +1-908-366-7933(USA) - C lick here lick here to register.
Training Related Link : http://sapbasisdurgaprasad.blogspot.com/2011/09/sap-basis-training.html Please also chec k SAP basis forum forum to po st/answer technical que stions : http://sapbasisdurgaprasad.freeforums.org For BASIS BASIS course c ontent, Visit our website: http://www.keylabstraining.com http://www.keylabstraining .com /sap-basis/sap-basis-online-trai online-training ning
Friday, 20 May 2011 Search This Blog Loading...
SAP Basis Daily Monitoring Tcodes
Key labs SAP TRAINING TRAINING
SAP BASIS/Netweaver Training in Bangalore: Keylabs Bangalore : +91-8861770545 SAP BASIS/Netweaver Training in Hyderabad: Keylabs Hyderabad: +919550645679 SAP Online Online Training for A ll
Proactive monitoring of the SAP systems, will help to understand issues in advance advance & helps us to take corrective actions and
thus wil willl lead to
lesser downtime of the systems, improving profitability of the business organisation. Monitoring can be focused on ABAP stack(including database checks), Java Stack and Oslevel checks.
ABA P Stack Checks :
USA: +1-908-366-7 933
SM50 : (Process Overview)
This transaction code will be useful to view the processes that are
FeedBurner FeedCount
running currently in an sap insance. In this view you can check whether there are free workprocesses to execute the processes. If all the workprocesses are in running state and no work process is idle it means that wait times will increase for the processes that are waiting in the
Followers
dispatcher queue leading to performance degradation. If you find that there are no free workprocceses for maximum times that you may
Follow by Ema il Email address...
Submit
consider, increasing the number of workprocesses. How to increase the number of work processes
Subscribe To
Posts Comments
live_stats
Feedjit Live Blog Stats
Recent Posts
Popula r Posts
SAP Basis Daily Monitoring Tcodes Proactiv e monitoring of the SAP systems, will help to understand issues in advance & helps us to take cor rectiv e actions and thus wil... SAP Basis Training Dear Followers, As pe r request from some of my followers, have taken an initiative to start i) SAP Basis Training(Coac.. . How to co nfigure Early Watch Alert report To configure Early watch alert some spec ific settings to be done at managing sy stem (Solution manager system) and satellite system( or manag...
SM66 : (Global process overview)
This transaction code will be useful to view the processes that are running across all instances/application servers of a SAP system. Similar to SM50 checks can be done in this transaction as well. SM51 : (Application servers status)
This transaction code will be useful to view all the hostnames and application servers status. If any application server is down, the same can be identified using status of the server column. We can also figure out different Message types (Dialog, Batch, Update, Upd2, Spool, ICM etc) configured for t he respective servers. SM12 : (Lock entry list)
This transaction code will be useful to view all the sap locks that are present in the system. As part of monitoring, we need to look for any old sap locks that are more than 1 day. If any such locks, we need to analyse the reason for that lock for such longer duration and take
SAP Java monitoring Check list This article answers the following queries : Ø How to perform daily monitoring of Java stack in SAP ? Ø What are the daily chec ks...
actions accordingly. A lock can be set for such a long duration due to a
How to troubleshoot a background job runn ing for l ong d urat ion in sap? This article answers how to troubleshoot a background job running for a lo ng duratio n ---------------------------------------------------...
How to delete a sap lock?
long running background job or a lock is not released due to an application error or a program terminated abruptly but lock not released etc.
How to check transactional RFC(tRFC) r elate d errors? This article answers the following queries : ü How to check transactional RFC (tRFC) relate d erro rs? ü How to find out status of transac... SAP Basis sample CV - 1 Hi Friends, Thought of sharing y ou some SAP Basis CVs with y ou which will b e he lpful for y ou . Iam s ure , y ou c an shap e y our CV ba sed o n th... what is s poo l ov erflo w ? How to tro ubleshoot spool ov erflow issue ? This article answers the following queries : What is spo ol ov erflow ? How to troubleshoo t spool ov erflow ? How to delete old spool requ... How to cre ate an RFC Connection in SAP ? This article answers the following queries : How to cre ate an RFC connec tion ? How to test RFC connection ? How to dele te an RFC ? ... How to find out who are all having acc ess to a particular tcode in SAP sy stem? This article answers the following queries ü How to find out who are all having access to a particular tcode in SAP sy stem? ü How to fi...
ST22 : (ABAP Dumps )
This transaction code will be useful to view all the abap dumps that have occured in the system on a given day. As part of daily monitoring, it is the responsibility of the basis administrator to analyse the dumps and take necessary actions to avoid issues. Some of the examples of abap dumps are timeout issue, database sp ace issue, spool overflow issue etc SM21 : (System log)
This transaction is useful to view the log of the sap system for various operations. This log will be very useful to identify various issue in advance and to take necessary measures. System log is the place to check out for any timeout, network issues, database space issues, message server issues, spo ol overflow, locktable overflow etc issues. Additional details : SAP System log SM13 : (Update Requests overview)
This transaction is useful to figure the status of update system. Incase an update is inactive we can figure out the same from this transaction and necessary action can be taken and update can be activated again.
Update got deactivated. what is the reason for update deactivation? How to activate the update ?
Blog Archive ►
2013 (19)
►
2012 (19)
▼
2011 (102)
SM14 transaction can be called internally from SM13. These both transactions are us eful for upd ate administration.
►
11/27 - 12/04 (1 )
►
10/02 - 10/09 (1 )
In SM13, you can select status (canceled, to be updated, v1 executed,
►
09/25 - 10/02 (1 )
v2 executed, all ) and time interval during which you would like to view
►
09/1 8 - 09/25 (6)
the status execute to check the overview of updates as per the status
►
09/11 - 09/18 (5)
and time interval selected.
►
09/04 - 09/11 (5)
►
08/28 - 09/04 (5)
►
08/21 - 08/28 (8)
►
08/07 - 08/14 (5)
►
07 /31 - 08/07 (2)
►
07 /24 - 07 /31 (6)
►
0 7 / 1 7 - 0 7 / 2 4 (3) -
In case of canceled updates, analysis to be done whether to repeat update. ST02 : (Tune summary )
This transaction will be used to monitor
Buffer statistics like hitratio, swaps, db access details, size of ►
07 /03 - 07 /10 (6)
►
06/26 - 07 /03 ( 1 7 )
►
06/19 - 06/26 (10)
►
06/12 - 06/19 (14)
►
06/05 - 06/12 (4)
▼
05/15 - 05/22 (1 )
buffer and free size of b uffer etc
Important st atistics related to Roll area, Page area, Ext ended memory and heap memory
Call statistics like select, insert, update and delete
SAP Basis Daily Mo nitoring Tcodes
As a basis administrator, it is our responsibility to ensure there is more hit ratio for the buffers and less swaps to ensure efficient performance of the sap system. In case you see there are more swaps and less hit ratios for most of the buffers, then tuning buffers to be carried out to ensure optimal performance. DB12 (Backup logs) : This transaction is us eful to check the details of
last successful backup overview of database backups ( Success / failure of backup with log details) Archiving directory status (Free space of oraarch ) Overview of redolog files ( Number of redologs that are not yet backed up) overview of redolog backups (Success / failure of backup with log details)
DB13 (DBA Planning calender) :
This transaction will be useful to schedule various database backups & clean up jobs like ( whole database backup offline/online, Full backup online/offline, incremental backup offline/online, redolog backup, update statistics, check db, cleanup logs, compress database, verify database, initialize tape and validate structure jobs). In this transaction, you can also check the status of every job that was scheduled and can reschedule in case of failures.
DB14 (DBA operations log) :
This transaction will be useful to check the s tatus of fo llowing :
Database backup Redolog backup BRSPACE log (extend tablespace issues etc) BRCONNECT operations (Update optimiser statistics , database check etc) As an sap basis administrator it is our responsibility to check and ensure backups and other cleanup jobs are successful everyday. Incase
of failures, should figure out root cause and take actions like rescheduling and ensure these jo bs are successful.
SM37 ( Jo b status overview) : This transaction will be useful to have an overview of jobs with different statuses. As part of daily monitoring, SAP basis administrator should use this transaction to findout canceled jobs and active jobs(for eg: long running - more than 24hrs etc). Incase of canceled jobs, root cause for the failure to be figured out from the logs of the respective job and to be actioned by rescheduling etc. Incase of long running jobs, we need to figure out the reason for long running and action them accordingly. In SM37, using extended job selection option, we can even select the jobs based on start condition, steps (like abap program, external command or external program), period etc How to identify long running jobs in sap ?
How to troubleshoot a background job running for long duration in sap?
ST04 (Database alert logs and performance) :
This transaction will be useful for (oracle) database administration. In this screen, goto Alerts and drill down further. Click on "Database Check" to
find
out
any
errors
MISSING_STATISTICS,
or
warnings
related
STATS_TOO_OLD,
to
database
like
LAST_BACKUP_FAILED,
LAST_ARCHIVE_FAILED etc. After going through the error or warning in details take necessary corrective actions based on the error like running update st ats again, re-triggering backup etc Under Alerts, you can view Alert monitor which will summarize status of the database under different heads like
Space Management Performance Backup/restore SAP Consistency Health Drill down on each of these to find out potential problems. These are color coded for ease of administrator (Red for errors, yellow for
Warnings and Green for OK status) For Eg: If PSAPSR3 tablespace is >90%, you can see Space management in red color. Then it is the responsibility of Basis administrator to take necessary actions o n the same. SP01 ( C heck Spool status ) :
This transaction is useful to find out the status of spool request and output request. In SP01 transcation, you can list the spool requests or output request s b etween a given interval. In the list generated, you can check out the status of spool requests and findout any errors by drilling do wn further. For eg: if so many spools are in waiting status, find out whether output device is available or not. If many spool are in error status , figure out if there is any network issue and take necessary actions. What are the different Spool statuses and their significance? If customers complain that they are not able print anything from SAP, check out whether there is any sp ool overflow. What is spool overflow ? How to troubleshoot spool overflow issue ? SXI_Cache : This Tcode is specific to XI or PI system. This Tcode is used to findout whether cache refresh is happening or not. Incase if cache refresh is happening successfully, it will indicate the same in green color. Otherwise it will be in red indicating a problem with cache refresh. If there is a problem with cache refresh then basis administrator has to troubleshoot the same.
SLDCHECK : This Tcode will be useful to figure out whether connection to the SLD system from the system on which you are testing is fine or not. In case the connection is fine, all checks will appear in green. Incase of any issues, it will appear in red or yellow and then basis administator has to troubleshoot it and make sure SLDCHECK is working fine. Ensuring SLDCHECK is working fine is important to keep all systems in the landscape in sync.
SXI_MONITOR : This TCode is specific to XI or PI system. This transaction will be useful to figure out any errors or warnings in the processing of XI or PI messages. In case of any issues, this needs to be informed to functional team and should be troubleshooted accordingly
with the functional team inputs.
DBO1 : This transaction code is useful to findout the database locks that are present in the SAP system. As part of daily monitoring, SAP Basis administrator has to figure out if there are any long pending locks more than 1 day etc and analyse reasons for the same. Sometimes if programs/jobs got terminated abruptly without removing the database locks set, this will lead to performance issues as other programs which needs that lock cannot set etc and they have to wait indefinitely as these locks won't get released automatically. In case of any long pending locks, Basis administrators should contact DBA team if any an dfigure out the reason for these locks and action accordingly Jack Stack Checks : Please refer below links to understand Daily Java monitoring of SAP Landscape: SAP Java monitoring check list 1 SAP Java monitoring check list 2 To monitor live Cache system, please refer below link : Live Cache Monitoring in SAP
Please find below table which summarizes daily monitoring tasks that are to be performed by the SAP Basis Administrator :
Sno
T ask ABAP Stack Chec ks 1Check process overv iew(SM50) 2Check ov erall system process ov erview(SM66) 3Check application servers status(SM51) 4Check fo r any pending locks (SM12) 5Check fo r Dumps in the system(ST22) 6Check System log for any errors(SM21) 7Check for any hanged updates or update status(SM13) 8Check for ex cessive swapping (ST02) 9
Check for critical job status like backup,updatestats,checkdb etc(DB13)
10Check for longrunning/failed jobs status(SM37) 11 Check database alertlogs and performance(ST04 ) 12Check spool job status (SP01) 13Check cac he status (sxi_cache) for PI System 14Check SLD functionality(SLDCHECK) 15Check SXI_MONITOR for PI system 16Check f or Database lock s(DB01) Java Stack Checks 1Check java portal accessibility using link 2Check server0 log for java system for c ritical errors
3Check accessibility of management console 4Check serv er node status 5Check default trace for c ritical java errors 6Check java reports for memoryconsumption/swapping Os level checks 1Check filesystems usage (shouldb be <80%) 2Check for swap space using topas etc 3Check for work directory log files at oslevel for errors
Useful Links :
How to change SAP parameter ?
Posted by DurgaPrasad at 17:50 Reactions:
29 comments: Eric 24 November 2011 19:13 sublime! Reply Replies DurgaPrasad
20 June 2013 1 7 :38
Thanks Eric Reply
An on y m ou s 20 December 2011 14:54 nice .. Reply
An on y m ou s 9 March 2012 06:34 Thanks its very nic e.. Reply
An on y m ou s 8 August 2012 03:01
Superb.... Reply
An on y m ou s 6 October 2012 22:57 Good Job Durga ! Reply Replies DurgaPrasad
20 June 2013 1 7 :55
Thanks dude Reply
An on y m ou s 30 October 2012 19:51 can u give full monitoring of st03 step by step , would be thankful if you giv e step by step Reply
Prashant 3 December 2012 09:04 This is very excellent article. Very well documented and explained. A job well d one . Reply Replies DurgaPrasad
20 June 2013 1 7 :46
Thank U Prashant Reply
An on y m ou s 14 December 2012 01 :58 Superb explanation. durga prasad! can you please explain what is the difference b etween SM50 and SM66 Reply Replies An on y m ou s 25 February 2013 1 5:34 Sm50 is the process overview of the particular server,and sm66 is the process ov erview of all instances or serv ers...........
DurgaPrasad
20 June 2013 1 7 :40
Hi...SM50 will give you local workprocess overview where as SM66 will give you global workprocess overview. It means, if you have multiple application servers installed in an sap system, for a particular server you can view workprocess overview through SM50 and if you want to view workprocess overview of all application servers at one place, you can use SM66.
Reply
An on y m ou s 6 February 201 3 16:59 I´m sap basis administrator and I found this blog yesterday and I have to give all the support and co ngrat you for this, all the effort that y ou put here is very useful for all of us, for all the people who, like me, want to read and search for cre dible information about sap basis activity! Go ahead! Hugs Reply Replies DurgaPrasad
20 June 2013 1 7 :41
Thanks much friend...your words are really motivates for me to spend more time on blog Reply
Unknown 7 February 2013 13:52 god bless you sir Reply Replies DurgaPrasad
20 June 2013 1 7 :47
Thanks my friend Reply
Pradip Mishra 8 February 201 3 14:41 Really great... marve lous wo rk sir....this blog is really need / A sset for fresher as well as Experienc e candidates Reply Replies DurgaPrasad
20 June 2013 1 7 :51
Thanks much Pradip Reply
google 1 March 2013 00:32 I started to take notes from the entire blog for my interv iew Thank yo u so much, Rathish Reply Replies DurgaPrasad
20 June 2013 1 7 :41
Thanks Dude..It so unds music to my ears
Reply
cireddy krishn a reddy 31 March 2013 00:31 How many updates c an be active per instance? Reply Replies DurgaPrasad
20 June 2013 1 7 :49
Hi krishna, we ca n co nfigure max imum 1 00 V 1 upd ate s and 1 00 V 2 upda tes per instance. However in real life these many are not req uired and y ou c an c onfigu re m uc h les ser v alue s. Reply
rajkumar 23 April 2013 22:47 v er y use ful sir. . Reply
An on y m ou s 28 May 2013 1 7 :36 What ca n we do if SAP sy ste m is no t wor king Reply Replies DurgaPrasad
20 June 2013 1 7 :50
So many chec ks to be done...I hope it demands to write a separate article o n this!1 Reply
elumalai jay araman 18 June 2013 1 6:10 v er y use ful the abo v e mo nito ring t c ode Reply
elumalai jay araman 18 June 2013 1 6:11 v er y use full Reply Replies DurgaPrasad Thanks Elumalai Reply
Ad d co m m ent
20 June 2013 1 7 :49
Newer Post
Home
Subscribe to: Post Comments (Atom)
SAP Basis/Netweav er Tutorials, Monitoring , Admini strati on(Certifica tion) and FAQs Headline Anima tor ↑ Grab
this Headline A nim ator
SAP Basis/Netwever Training
keylabs Training
Total Pageviews
Contributors
LoadRunner Training DurgaPrasad
Copyright @201 1 http://sapbasisdurgaprasad.blogspot.com. A ll rights reserv ed. Watermark template. Powered by Blogger.
