System Health Check Training 19 March 2015: By: Aslaily Abd Manan
System Health Check Training 19 March 2015: By: Aslaily Abd Manan
System Health Check Training 19 March 2015: By: Aslaily Abd Manan
Agenda
Introduction
SAP Monitoring
DB Monitoring
OS Monitoring
Conclusion
Confidential
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
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
Confidential
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
Confidential
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
Process ID of the
work process (on the
operating system)
Confidential
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
Confidential
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
Resource bottleneck
Confidential
11
Confidential
12
can use the log to pinpoint and correct errors occurring in your system and its
environment.
Confidential
13
Confidential
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
15
Confidential
AOB
16
Confidential
Confidential