SAP Basis Tutorials

Hi..In this blog am covering SAP Basis/netweaver concepts, monitoring, administration, performance
tuning, SAP implementations, sample BASIS CVs and FAQs. Please join as followers and please
subscribe to get an update on new articles published. For SAP Training,
alexander.durgaprasad@gmail.com or contact Keylabs Bangalore(+'91-8861770545') and Keylabs
Hyderabad (+91-9550645679) and USA Contact 908-366-7933: Training
Link:http://sapbasisdurgaprasad.blogspot.com/2011/09/sap-basis-training.html

Home Aut horisat ion Administ rat ion Dat abase Performance Tuning FAQs Implement at ions

SAP BASIS/NETWEAVER/SECURITY TRAINING

Keylabs Training
Like 189 SAP BASIS Dem o - Key labs Hy derabad: 11-July -2013 at 6 pM (Contact
Hy derabad: +91-955064567 9)
SAP Netweaver Demo in Keylabs Hyderabad : 19-July-2013 at 8 AM
by Durga prasad (Contact Hy derabad: +91-955064567 9)

SAP BASIS/Netweav er/Security /GRC 10 T raining in Key labs Bangalore: +91-

88617 7 0545, sindhu@ key labstraining.com - SAP BASIS Batch in Bangalore
from Aug 7 th.

SAP BASIS/Netweav er/Security /GRC 10 T raining in Key labs Hy derabad:+91-

9550645679 , hyd@keylabstraining.com
For SAP Online T raining - All m odules:
+1-908-366-7 933(USA) - Click here to register.

Training Related Link :

http://sapbasisdurgaprasad.blogspot.com/201 1 /09/sap-basis-training.html

Please also check SA P basis forum to post/answer technical questions :

http://sapbasisdurgaprasad.freeforums.org

For BA SIS course content, V isit our website:

http://www.key labstraining.com/sap-basis-online-training

Friday, 20 May 2011

Search This Blog

SAP Basis Daily Monitoring Tcodes

Loa din g ...

Key labs SAP TRAINING

SAP BASIS/Netweav er
T raining in Bangalore: Proactive monitoring of the SAP systems, will help to understand issues
Key labs Bangalore : in advance & helps us to take corrective actions and thus will lead to
+91 -8861 7 7 0545 lesser downtime of the systems, improving profitability of the business

SAP BASIS/Netweav er
organisation.
T raining in Hy derabad:
Monitoring can be focused on ABAP stack(including database checks),
Key labs Hy derabad: +91 -
955064567 9 Java Stack and Oslevel checks.

SA P Online Training for A ll

modules
modules
ABAP Stack Checks :
USA : +1 -908-366-7 933

SM50 : (Process Overview)

FeedBurner FeedCount
Follow ers
Follow by Em ail
Email address...
This transaction code will be useful to view the processes that are
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
dispatcher queue leading to performance degradation. If you find that
there are no free workprocceses for maximum times that you may
consider, increasing the number of workprocesses.
Submit

How to increase the number of work processes

Subscribe To

Posts

Comments SM66 : (Global process overview)

liv e_stats
This transaction code will be useful to view the processes that are
Feedjit Liv e Blog Stats
running across all instances/application servers of a SAP system. Similar
to SM50 checks can be done in this transaction as well.
Recent Posts

SM51 : (Application servers status)

Popular Posts

SA P Basis Daily Monitoring Tcodes

Proactiv e monitoring of the SA P
sy stems, will help to understand
issues in adv ance & helps us to take
correctiv e actions and thus wil...
SA P Basis Training
Dear Followers, A s per request
from some of my followers, hav e
taken an initiativ e to start i)
SA P Basis Training(Coac...
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 the respective servers.
SM12 : (Lock entry list)

How to configure Early Watch A lert

report
To configure Early watch alert This transaction code will be useful to view all the sap locks that are
some specific settings to be done at
managing sy stem (Solution present in the system. As part of monitoring, we need to look for any
manager sy stem) and satellite
old sap locks that are more than 1 day. If any such locks, we need to
sy stem( or manag...
analyse the reason for that lock for such longer duration and take
SA P Jav a monitoring actions accordingly. A lock can be set for such a long duration due to a
Check list
This article answers long running background job or a lock is not released due to an
the following queries : application error or a program terminated abruptly but lock not released
Ø How to
perform daily etc.
monitoring of Jav a stack in SA P ? Ø
What are the daily checks...

How to troubleshoot a background How to delete a sap lock?

job running for long duration in
sap?
This article answers how to
troubleshoot a background job
running for a long duration ----------
-------------------------------------------
...
 ST22 : (ABAP Dumps )
How to check
transactional
RFC(tRFC) related
errors?
This article answers This transaction code will be useful to view all the abap dumps that have
the following queries : occured in the system on a given day. As part of daily monitoring, it is
ü How to check transactional RFC
(tRFC) related errors? ü How to the responsibility of the basis administrator to analyse the dumps and
find out status of transac... take necessary actions to avoid issues.
SA P Basis sample CV - 1
Hi Friends, Thought of sharing y ou Some of the examples of abap dumps are timeout issue, database space
some SA P Basis CV s with y ou which
issue, spool overflow issue etc
will be helpful for y ou. Iam sure,
y ou can shape y our CV based on
th... SM21 : (System log)
what is spool ov erflow
? How to troubleshoot
spool ov erflow issue ?
This transaction is useful to view the log of the sap system for various
This article answers
the following queries : operations. This log will be very useful to identify various issue in
What is spool
ov erflow ? How to troubleshoot
advance and to take necessary measures. System log is the place to
spool ov erflow ? How to delete check out for any timeout, network issues, database space issues,
old spool requ...
message server issues, spool overflow, locktable overflow etc issues.
How to create an RFC
Connection in SA P ? Additional details :
This article answers
the following queries :
How to create an RFC SAP System log
connection ? How to
test RFC connection ? How to
delete an RFC ? ... SM13 : (Update Requests overview)

How to find out who

are all hav ing access
to a particular tcode This transaction is useful to figure the status of update system. Incase
in SA P sy stem?
This article answers an update is inactive we can figure out the same from this transaction
the following queries and necessary action can be taken and update can be activated again.
ü How to find out who are all
hav ing access to a particular tcode
in SA P sy stem? ü How to fi...
Update got deactivated. what is the reason for update deactivation? How

Blog Archiv e
to activate the update ?

► 201 3 (1 9)
► 201 2 (1 9)
SM14 transaction can be called internally from SM13. These both
▼ 201 1 (1 02)
transactions are useful for update administration.
► 1 1 /27 - 1 2/04 (1 )
► 1 0/02 - 1 0/09 (1 ) In SM13, you can select status (canceled, to be updated, v1 executed,
► 09/25 - 1 0/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/1 1 - 09/1 8 (5) and time interval selected.

► 09/04 - 09/1 1 (5)

In case of canceled updates, analysis to be done whether to repeat
► 08/28 - 09/04 (5)
update.
► 08/21 - 08/28 (8)
► 08/07 - 08/1 4 (5) ST02 : (Tune summary )
► 07 /31 - 08/07 (2)
► 07 /24 - 07 /31 (6)
This transaction will be used to monitor
► 07 /1 7 - 07 /24 (3)

► 07 /1 0 - 07 /1 7 (2)
► 07 /1 0 - 07 /1 7 (2)
Buffer statistics like hitratio, swaps, db access details, size of
► 07 /03 - 07 /1 0 (6)
buffer and free size of buffer etc
► 06/26 - 07 /03 (1 7 )
► 06/1 9 - 06/26 (1 0)
Important statistics related to Roll area, Page area, Extended
► 06/1 2 - 06/1 9 (1 4) memory and heap memory
► 06/05 - 06/1 2 (4)
▼ 05/1 5 - 05/22 (1 )
Call statistics like select, insert, update and delete
SA P Basis Daily Monitoring
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 useful 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 status of following :

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 jobs are successful.

SM37 ( Job 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 or warnings related to database like
MISSING_STATISTICS, STATS_TOO_OLD, 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 stats 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 on the same.

SP01 ( Check 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 requests between a given interval.

In the list generated, you can check out the status of spool requests
and findout any errors by drilling down 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 spool 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 Checks
1Check process overview(SM50)
2Check overall system process overview(SM66)
3Check application servers status(SM51)
4Check for any pending locks (SM12)
5Check for Dumps in the system(ST 22)
6Check System log for any errors(SM21)
7Check for any hanged updates or update status(SM13)
8Check for excessive swapping (ST 02)
Check for critical job status like backup,updatestats,checkdb
9
etc(DB13)
10Check for longrunning/failed jobs status(SM37)
11Check database alertlogs and performance(ST 04)
12Check spool job status (SP01)
13Check cache status (sxi_cache) for PI System
14Check SLD functionality(SLDCHECK)
15Check SXI_MONIT OR for PI system
16Check for Database locks(DB01)
Java Stack Checks
1Check java portal accessibility using link
2Check server0 log for java system for critical errors
 3Check accessibility of management console
4Check server node status
5Check default trace for critical 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 1 7 :50

Reactions:

29 comments:
Eric 24 Nov ember 201 1 1 9:1 3
sublime!
Reply

Replies

DurgaPrasad 20 June 201 3 1 7 :38

Thanks Eric

Reply

Anony m ous 20 December 201 1 1 4:54

nice ..
Reply

Anony m ous 9 March 201 2 06:34

Thanks its v ery nice..
Reply

Anony m ous 8 A ugust 201 2 03:01

Superb....
Reply

Anony m ous 6 October 201 2 22:57

Good Job Durga !
Reply

Replies

DurgaPrasad 20 June 201 3 1 7 :55

Thanks dude

Reply

Anony m ous 30 October 201 2 1 9:51

can u giv e full monitoring of st03 step by step , would be thankful if y ou giv e
step by step
Reply

Prashant 3 December 201 2 09:04

This is v ery ex cellent article. V ery well documented and ex plained. A job
well done.
Reply

Replies

DurgaPrasad 20 June 201 3 1 7 :46

Thank U Prashant

Reply

Anony m ous 1 4 December 201 2 01 :58

Superb ex planation. durga prasad! can y ou please ex plain what is the
difference between SM50 and SM66
Reply

Replies

Anony m ous 25 February 201 3 1 5:34

Sm50 is the process ov erv iew of the particular serv er,and sm66 is
the process ov erv iew of all instances or serv ers...........

DurgaPrasad 20 June 201 3 1 7 :40

Hi...SM50 will giv e y ou local workprocess ov erv iew where as
SM66 will giv e y ou global workprocess ov erv iew.

It means, if y ou hav e multiple application serv ers installed in an

sap sy stem, for a particular serv er y ou can v iew workprocess
ov erv iew through SM50 and if y ou want to v iew workprocess
ov erv iew of all application serv ers at one place, y ou can use
SM66.
 Reply

Anony m ous 6 February 201 3 1 6:59

I´m sap basis administrator and I found this blog y esterday and I hav e to
giv e all the support and congrat y ou for this, all the effort that y ou put here
is v ery useful for all of us, for all the people who, like me, want to read and
search for credible information about sap basis activ ity !
Go ahead! Hugs
Reply

Replies

DurgaPrasad 20 June 201 3 1 7 :41

Thanks much friend...y our words are really motiv ates for me to
spend more time on blog

Reply

Unknown 7 February 201 3 1 3:52

god bless y ou sir
Reply

Replies

DurgaPrasad 20 June 201 3 1 7 :47

Thanks my friend

Reply

Pradip Mishra 8 February 201 3 1 4:41

Really great... marv elous work sir....this blog is really need / A sset for
fresher as well as Ex perience candidates
Reply

Replies

DurgaPrasad 20 June 201 3 1 7 :51

Thanks much Pradip

Reply

google 1 March 201 3 00:32

I started to take notes from the entire blog for my interv iew
Thank y ou so much,
Rathish
Reply

Replies

DurgaPrasad 20 June 201 3 1 7 :41

Thanks Dude..It sounds music to my ears
 Reply

cireddy krishna reddy 31 March 201 3 00:31

How many updates can be activ e per instance?
Reply

Replies

DurgaPrasad 20 June 201 3 1 7 :49

Hi krishna,

we can configure max imum 1 00 V 1 updates and 1 00 V 2 updates

per instance. Howev er in real life these many are not required and
y ou can configure much lesser v alues.

Reply

rajkum ar 23 A pril 201 3 22:47

v ery useful sir..
Reply

Anony m ous 28 May 201 3 1 7 :36

What can we do if SA P sy stem is not working
Reply

Replies

DurgaPrasad 20 June 201 3 1 7 :50

So many checks to be done...I hope it demands to write a separate
article on this!1

Reply

elum alai jay aram an 1 8 June 201 3 1 6:1 0

v ery useful the abov e monitoring t code
Reply

elum alai jay aram an 1 8 June 201 3 1 6:1 1

v ery usefull
Reply

Replies

DurgaPrasad 20 June 201 3 1 7 :49

Thanks Elumalai

Reply

Add com m ent

 Newer Post Home

Subscribe to: Post Comments (A tom)

SAP Basis/Netw eav er Tutorials, Monitoring, Adm inistration(Certification) and FAQs Headline Anim ator

↑ Gra b th i s Headl i n e A n i m a tor

SAP Basis/Netw ev er Training

key labs Training

Total Pagev iew s

Contributors

LoadRunner Training

DurgaPrasad

Copy right @201 1 http://sapbasisdurgaprasad.blogspot.com. A ll rights reserv ed. Watermark template. Powered by Blogger.