SAP Basis Monitoring Document

Introduction
System monitoring is a daily routine activity and this document provides a
systematic step by step procedure for Server Monitoring. It gives an overview of
technical aspects and concepts for system monitoring.

Monitoring Tcodes

Checking Application Servers (SM51)

This transaction is used to check all the active application server.

Monitoring Work Processes for Individual Instances (SM50).

Displays all running, waiting, stopped and PRIV processes related to a
particular instance. Under this step we check all the process, the process status
should always be waiting or running. If any process is having status other then
waiting or running we need to check that particular process and report
accordingly.

Monitoring System wide Work Processes (SM66)

We can quickly investigate the potential cause of a system performance problem
by checking the work process load and can use the global work process
overview to:

• Monitor the work process load on all active instances across the system

• Identify locks in the database (lock waits).

Using the Global Work Process Overview screen, we can see at a glance:

• The status of each application server

• The reason why it is not running

• Whether it has been restarted

 • The CPU and request run time

• The user who has logged on and the client that they logged on to

• The report that is running

We record only those processes which are showing problems and not having
running status.

Monitoring Update Processes (SM13)

Execute Transaction SM13 and put * in the field USER.
This transaction is used to check the following activities:

1. Is the update active, if not , was it deactivated by system or by user.

2. Have any update been cancelled.
3. Is there a long queue of pending updates older than 10 minutes.

Monitoring Lock Entries (SM12)

Execute Transaction SM12 and put * in the field User Name
We can use lock statistics to monitor the locks that are set in the system. We
record only those lock entries which are having date time stamp of previous
day.

Monitoring System Log (SM21)

We can use the log to pinpoint and correct errors occurring in the system and its
environment. We check log for the previous day, and time is entered as shown in
the screen below. Then select Radio Button Problems and Warnings and press
Reread System Log.
We write total number of records, as shown in the screen below, in our log and
analyze the problems which are not displayed in ST22.

CPU Utilization (ST06)

In CPU Utilization we record User, System, Idle and Wait percentage utilization
from the above screen.

Available Space in Database (DB02)

Space statistics are taken from the below screen and we record Total Size in
GB and Total free space in percentage.

Checking Missing indexes (DB02)

At the same screen missing indexes statistics can also be checked
by pressing Missing Indexes button, below screen pops up. Record
primary and secondary missing indexes.

ABAP Dump Analysis (ST22)

Here we check for previous day’s dumps.
Open the details log of each and every dump by double clicking it and try to find
out any suitable notes, analyze them and propose suitable solution as per SAP
standards.

Spool Request Monitoring (SP01)

In spool request monitoring execute sp01 and put * in the field Created By and
press execute button.
Here we record only those requests which are terminated with problems.
Number of Print Requests (SPAD)
Execute SPAD and press Admin button.

Now select Print Request Overview button.

Record Total Print Requests from below screen.

Monitoring Batch Jobs (SM37)

Execute SM37 and put * in the field User Name record number of Scheduled,
Cancelled, Released and Finished requests.

Batch Input Session Lock (SM35)

Execute SM35 and press Locked Button. Record number of requests displayed.

Database Performance Monitor (ST04)

Record Quality %, if its is >=95 write 0 else write actual percentage displayed.