System Health Check Training

19th March 2015

By: Aslaily Abd Manan

Agenda
Introduction
SAP Monitoring
DB Monitoring
OS Monitoring
Conclusion

Confidential

2015 ABeam Consulting Ltd.

Introduction
SAP Monitoring:
Why? It provides the windows of things to happen
What? SAP application, Database health and OS health checks
Who? System Administrator
When? Subjective but in a nutshell, its supposed to be a daily routine job by
the system administrator. For example: What time is supposed to complete? If it
failed what would be the next action plan.

Confidential

2015 ABeam Consulting Ltd.

SAP Monitoring
First thing first:
1. Are you able to login?
2. If not please check the normal scenarios below;
a) Correct information in the SAP GUI
b) Network connectivity
c) SAP services are up and running

3. By right we should be seeing this:

Confidential

2015 ABeam Consulting Ltd.

SAP Monitoring
Once login, we are able to do the normal monitoring:
Listed here are the general t-codes we used to do system monitoring:

SM51
SM50
SM12
SM13
ST22
SM21
SM37
DB12
DB13
SP01
ST03N
SP12
ST06
DBACOCKPIT
SA38

Whatever listed here should only be seen as guided reference.

5

Confidential

2015 ABeam Consulting Ltd.

SAP Monitoring (SM51)

SM51 - List of SAP Servers

display list of active application servers that have registered in the SAP message
server.
manage & display the status, users, work process in all application servers belonging
to the SAP System.

Confidential

2015 ABeam Consulting Ltd.

SAP Monitoring (SM50)

SM50 - Work Process Overview

used to monitor and manage work processes.

a) DIA: Work process for executing dialog steps in user transactions.
b) UPD: Update process for making U1 (time-critical) database changes.
c) UP2: Update process for executing U2 (not time-critical) database changes.
d) ENQ: For locking or releasing SAP lock objects.
e) BTC: For processing background jobs.
f) SPO: For spool formatting processes.

Process ID of the
work process (on the
operating system)

Running (executing a request)

Waiting (idle and waiting for work)
Hold (held for one user) is not an
abnormal state, but a work process can
only serve a single user.
Stopped (aborted with Restart set to No)

Confidential

2015 ABeam Consulting Ltd.

SAP Monitoring (SM12)

SM12 - Display and Delete Locks

SAP System is equipped with a special lock mechanism that synchronizes access to
data on the database.
The purpose of the lock mechanism is to prevent two transactions from changing the
same data on the database simultaneously
Lock entries are usually set and deleted automatically when user programs access a
data object & release it again.
If any outdated entry found, go to AL08 or SM04 to get the transaction code that been
use by the user. Release the table from lock by deleting the lock.

Confidential

2015 ABeam Consulting Ltd.

SAP Monitoring (SM13)

SM13 - Display Update Records

With update management, we can perform following tasks:

a) Display update requests
b) Analyze problems relating to the update
c) Test and clean up canceled update requests
d) Display and reset the status of update requests
e) Delete update requests
f) Display statistics on the update

Confidential

2015 ABeam Consulting Ltd.

SAP Monitoring (ST22) 1 of 2

ST22 - ABAP Runtime Error

10

list the ABAP runtime errors that have occurred in an ABAP system as well as the
relevant short dumps.
To allow clearer processing, the runtime errors are divided into categories. The category
of the runtime error returns hints on cause of the error and troubleshooting.
Categories

Description

Internal Kernel Error

Error in ABAP Kernel.

Recommendation Sending an error
message to SAP.

Errors in the ABAP runtime

Errors in the screen runtime
Errors in the database interface

The system was able to roughly

determine the area in which the error
occurred. Next, clarify whether it was
triggered by an internal error or by a
programming error.

Resource bottleneck

Example: SYSTEM_NO_ROLL: The

application does not have enough
memory available.

Confidential

2015 ABeam Consulting Ltd.

SAP Monitoring (ST22) 2 of 2

11

Confidential

2015 ABeam Consulting Ltd.

SAP Monitoring (SM21)

SM21 - System Log

12

can use the log to pinpoint and correct errors occurring in your system and its
environment.

Confidential

2015 ABeam Consulting Ltd.

SAP Monitoring (SM37)

SM37 - Background Job Overview

13

SAP background processing allows the automation of routine tasks.

Confidential

2015 ABeam Consulting Ltd.

SAP Monitoring (SP01)

SP01 - Output Controller

14

user can manage the spool and output requests in the Output Controller.
In the output controller, we can:
a) Specify selection criteria for displaying spool and output requests. A list of spool or
output requests that match these criteria appears.
b) Output spool requests, that is, print them.
c) Display detailed data about a spool or output request and change certain attributes,
such as destination printer and number of copies
d) Display the data to be printed and export it in different formats.
e) Delete requests.

Confidential

2015 ABeam Consulting Ltd.

SAP Monitoring (SP12)

SP12 TemSe Administration

15

to display and manage TemSe objects.

TemSe is a store for temporary sequential data; that is, objects that are not normally
permanently held in the system are stored in the TemSe.
The spool system uses the TemSe to store output data temporarily.
We can set whether the spool data is to be stored by TemSe in the SAP database or in
the file system

Confidential

2015 ABeam Consulting Ltd.

AOB

16

Confidential

2015 ABeam Consulting Ltd.

Confidential

2015 ABeam Consulting Ltd.