Landscape Information:

Products and component information:

Product
SID

SAP Product

Product Version

EP1

SAP ERP ENHANCE PACKAGE

6.04

Main Instances (ABAP or Java based)

SID

Main Instance

EP1

SAP ECC Server

Databases
SID Database System

Database Version

EP1 DB2 for Linux UNIX and Windows

9.7

Servers in current Landscape

SAP Application Servers
SID

Host

Instance Name

Logical Host

EP1

wg0118

wg0118_EP1_63

wg0118

EP1

wg0119

wg0119_EP1_63

wg0119

EP1

wg0120

wg0120_EP1_63

wg0120

EP1

wg0121

wg0121_EP1_63

wg0121

EP1

wg0122

wg0122_EP1_63

wg0122

EP1

wg0194

wg0194_EP1_63

wg0194

DB Servers:
SID

Host

Logical Host (SAPDBHOST)

EP1

wg0117

wg0117

ABAP

Hardware Configuration
Host Overview
Hardwar
e
Host
Model
Manufact
urer

Intel(R)
Xeon(R) CPU
E7- 2850 @
2.00GHz

wg01 VMware,
17
Inc.

wg01 VMware,
18
Inc.

wg01 VMware,
19
Inc.

wg01 VMware,
20
Inc.

wg01 VMware,
21
Inc.

CPU Type

VMware
Virtual
Platform

VMware
Virtual
Platform

VMware
Virtual
Platform

VMware
Virtual
Platform

Xeon E7- 2850

Xeon E7- 2850

Xeon E7- 2850

Xeon E7- 2850

Opera
CPU Virtualiz ting
MHz ation
Syste
m

No.
of
Memory
CPU in MB
s

Red
Hat
Enterp
rise
8
Linux 5
(x86_6
4)

129002

VMWARE

Red
Hat
Enterp
rise
8
Linux 5
(x86_6
4)

32187

VMWARE

Red
Hat
Enterp
rise
4
Linux 5
(x86_6
4)

32187

VMWARE

Red
Hat
Enterp
rise
4
Linux 5
(x86_6
4)

32187

VMWARE

Red
Hat
Enterp
rise
4
Linux 5
(x86_6
4)

32187

1997

Host Overview
Hardwar
e
Host
Model
Manufact
urer

wg01 VMware,
22
Inc.

wg01 VMware,
94
Inc.

VMware
Virtual
Platform

VMware
Virtual
Platform

CPU Type

Xeon E7- 2850

Xeon E7- 2850

Opera
CPU Virtualiz ting
MHz ation
Syste
m

No.
of
Memory
CPU in MB
s

VMWARE

Red
Hat
Enterp
rise
4
Linux 5
(x86_6
4)

32187

VMWARE

Red
Hat
Enterp
rise
4
Linux 5
(x86_6
4)

32187

EP1 Daily Monitoring Checks:

SM51

Checking number of instances with status will display the SAP servers and you can select
the particular server and check the work process running on that application server on
clicking on any application server to check work process status.

Work Process monitor, We can able to see almost everything that is currently running in Net Weaver
system. We can also see detailed information on a particular running process

AL08

Check number of active users. If it exceeds the threshold limit, take action

It shows the list of all the users who are logged on to the system globally or for all the
instances in the system which are active

SM12

List of number of lock entries. Long pending lock entry by user > 24 hrs except for
system jobs.
In a system whenever a user performs any update on any table for that period of time a
lock on that particular field of that table is created so that no other user can update that
table as user one is doing update on that table. And suppose during the update user
session get terminated due to some error then this lock entry remains on that field.

Change the User name to * because we have to report for all users and click on
list button from top or press F8.

SM13

Total number of Error updates/ Updates, Please immediately intimate to user about
update termination
If number of updates exceeds the limit, take action
Check:

Is the update active? If not, was it deactivated by the system or by a user?

Have any updates been cancelled (with status Error)? (Make sure that you enter
"*" in the user field.)

Is there a long queue of pending updates older than 10 minutes?

SM21

Check System log. Specify problems/action taken

Go to tcode SM21. In the menu,
System Log ---> Choose---> All remote system logs.

We need to take care when locks are holding for a long time, and when it leads to a
deadlock situation.

SM37

Total numbers of active jobs & check any ready status job, if anything found take action
and monitor the delay jobs and take action. Once you create a job via SM36 or via some
programs, the jobs will be coming under Scheduled job. If you submit a job via program,
the job will be released automatically. but if you schedule a job then SM36 , it'll be under
scheduled and u have to release that job to run--you can see release button
Once you release that job , it'll go to active state and then finished or if any issues come ,
it'll be under cancelled..
Scheduled- Released- Ready- Active- Finished- Cancelled
these are all for users to see the job, I mean the Job status. This whole cycle will be run
automatically. You need to release the Job that's it.

SPAD

Total No. of Spool request > Threshold take action spool errors if any check reasons
check for spool waiting for printing
The SAP spool system manages its own output devices. This includes mostly printers, but
also fax and archiving devices. In order for you to use output devices defined in your
operating system from the SAP System, you must define these devices in the SAP spool
system.

SP01
Take action for spool errors / spool waiting for printing

SMQ1 qRFC Monitor Outbound Queue

SMQ1 - Queue name: TIF_UPDATE_AUDIT_FILE

Checking the Vertex TIF_UPDATE_AUDIT_FILE queue as part of the Daily Monitoring is that
get alerted if there are more than a few records.

If we found more than 5 entries, we are updating to Steve

SMQ2 qRFC Monitor Inbound queue

Check if any qRFC inbound queues

SM58 Transactional RFCs

As a part of daily monitoring, Needs to check what are failed transactional entries list

SMLG Logon Groups / load balancing

List the name of the Server having Response time> 2 Sec

Go to transaction SMLG, and then go to -> load distribution.
There you will see a response time of the individual application
servers.

SM66 Global Work process Overview

Global Work Process Overview

This transaction code gives you the detail of the work process which are not local or just
say its for the whole system or the active instances in the system.
Check the CPICIPJSR and CPICIPPUN user, if any user got stuck more than 500 ms check
the jobs and take necessary action
Check for NRIV table.
Check that processes should not stuck on particular table, if yes; mention Table Name
and the number of processes. Check Number of queries running > 1500 sec

SCOT SAPconnect Administration

Mail alerts, execute SAPCONNECT ALL SEND job and the requests to move from EP1

SCC4 Clients Overview

This is a cross-client transaction; any changes made will affect all the clients in the SAP
system. This is a controlled transaction which is to be authorized user id only.

ST03 / ST03N Work Load Monitor

Workload Overview is mostly used as a starting point when carrying out the root cause
analysis process of a bottleneck in the system. In this part of the tool, the different Task
Types are explained in detail, such as the Number of Steps, Avg. Response Time, Avg.
CPU Time, Avg. Database Time, Avg. Wait Time and more. The goal here is to try spot a
particular task, the overall response time and if the current value for a particular period
of time exceeds the allowed threshold (as a rule of thumb, for task type Dialog the Avg.
Response Time should stand below 1000ms).

ST02 - Tune Buffer Monitor

A buffer is a memory segment in which the data is temporarily stored. The buffer allows
the information to be manipulated by processes more quickly and the main goal is to
avoid that data be read from a slow medium like a disk drive. Instead, the information
already located in the buffer is accessed much faster.
In Net Weaver, there are several different buffers. Each one of them allows a specific type
of data to be stored and the objective is to reduce the number of database accesses to a
minimum. These buffers are individually placed locally in every Application Server and
are implemented as shared memory segments in one or more shared memory pools
depending on the operating system. These buffers are:
- Program buffer: This buffer stores the compiled executable version of the ABAP
programs, also known as program loads.
- CUA buffer: This buffer stores menu data, buttons and related SAPGui functionality.
- Screen buffer: This buffer stores the screens that are already generated.
- Calendar buffer: This buffer stores the factory and user defined holiday calendars.
- Generic key table buffer: This buffer stores table entries and can also store the
entire table, which is then called full table buffering.
- Single record key buffer: This buffer stores only a single entry for a particular table
with its corresponding fields.
- Export and Import buffer: This buffer is used to store data that needs to be available
to several processes using the ABAP sentence EXPORT/IMPORT TO/FROM MEMORY in the
ABAP program code.
Others are the name table buffers which contain fields and table definitions that are
active in the Data Dictionary. The name table is implemented in two different database
tables; DDNTT for table definition entries and DDNTF for file description entries. The

associated buffers are:

- Table definition buffer: Memory segment for table DDNTT.
- Field description buffer: Memory segment for table DDNTF.
- Short NTAB buffer: This is a summary for Table and Field description buffers.
- Initial records buffer: Depending on the field type it stores the layout.
With the help of this monitoring tool, you will be able to tune all memory buffer parameters individually.
Every single buffer is divided into two parts, the Buffer Size and Buffer Entries.
Buffer Size: This is actually the size of the memory segment. By using the correct profile parameter,
you will have the option to change this value for every buffer. This is also divided into allocated space
and free space.
Buffer Entries: The number of buffer entries controls how many objects can be stored in the buffer. You
can have sufficient free space but if you run out of directory entries, new objects will not be placed in the
buffer and the free space will not be used.
The quality of a buffer and how often it is accessed is measured by the %Hit Ratio. This value will
indicate if the information stored in the buffers, such as table entries, programs and screens, is being hit
directly from the buffer itself or, on the other hand, if the system needs to bring that data from the
database since it was not found in the buffer.
The %Hit Ratio can have several values. For instance, when you start the system the %Hit Ratio will be
below the recommended value until you have some activity in the system and the buffer starts to fill up
with data. A good performing buffer will have a %Hit Ratio of 95% and above (99%-100% is
excellent). Keep in mind though that a value lower to 95% not always shows that you have a problem.
This can lead you to pinpoint and start performing an analysis. However, other factors can also affect
buffer quality decreasing %Hit Ratio values.
Another important piece is Buffer Swapping. This is a completely different story. When high swapping
in a buffer occurs, performance is degraded. Since the information needed by a work process is read
from the database and then put into the buffer, the old information that was previously in the buffer
needs to be removed (swapped out) allowing the new information to come into it.
There are two different factors that will play here, Buffer Size and Buffer Entries (well-known as
Directory Entries). If one of them runs out of space, swapping occurs. We also need to keep in mind that
some sort of swapping is sometimes normal and doesnt hurt the system. As a rule of thumb, you dont
need to worry below 1000 swaps in a particular buffer. But also always check the %Free Space and
%Free Directory Entries. Good values are up to 85% used space.

ST06 Operating System Monitor

Provides all the operating system values related with CPU utilization, Disk drive
information, Network, OS Swapping and others by means of the OS Collector (saposcol)
service.
We can observe if for a particular drive the response time is excessively high or, on the
other hand, if disk drives are performing well.
In the menu Detail analysis menu -> Daily averages -last 30 days -> Display within
server you see the average workload of the server.

Check: CPU utilization, Memory utilization, Swap space utilization

ST10 Table Call Statistics

With this Table Call Statistics transaction, we can able to see detailed information regarding the table
and the table buffer status. There are several different buffers. In this application will work directly with
the Table Buffers. As you should already know, when a table is buffered its contents are located in a
memory segment in the shared memory pool locally under the application server and that table
information is read much faster from the buffer. The overall goal is to reduce database accesses and disk
times as much as possible. Read operation over a buffered table is around 80 times faster than accessing
the table directly from the database

RZ10 Profile parameters

We will be able to change the below system parameters related performance increase
Program buffer
abap/buffersize
CUA buffer
rsdb/cua/buffersize
Screen buffer
zcsa/presentation_buffer_area
sap/bufdir_entries
Generic key table buffer
zcsa/table_buffer_area
zcsa/db_max_buftab
Single record table buffer
rtbb/buffer_length
rtbb/max_tables
Export/import buffer
rsdb/obj/buffersize
rsdb/obj/max_objects
rsdb/obj/large_object_size
OTR buffer
rsdb/otr/buffersize_kb
rsdb/otr/max_objects
Exp/Imp SHM buffer
rsdb/esm/buffersize_kb
rsdb/esm/max_objects
rsdb/esm/large_object_size

Table definition buffer

rsdb/ntab/entrycount
Field description buffer
rsdb/ntab/ftabsize
rsdb/ntab/entrycount
Initial record buffer
rsdb/ntab/irbdsize
rsdb/ntab/entrycount
Short nametab (NTAB)
rsdb/ntab/sntabsize
rsdb/ntab/entrycount
Calendar buffer
zcsa/calendar_area
zcsa/calendar_ids
Roll, extended and heap memory
ztta/roll_area
ztta/roll_first
rdisp/ROLL_SHM
rdisp/PG_SHM
rdisp/PG_LOCAL
em/initial_size_MB
em/blocksize_KB
em/address_space_MB
ztta/roll_extension
abap/heap_area_dia
abap/heap_area_nondia
abap/heap_area_total
abap/heaplimit
Workprocess Distribution
rdisp/wp_no_dia
rdisp/wp_no_btc
rdisp/wp_no_vb
rdisp/wp_no_vb2

ST22 ABAP Dumps

Try to solve recurring ABAP dumps. Apply SAP notes if necessary

DB02

Tables and Indexes

Table space monitor:

Number of deadlock along with Table Name if any deadlock for more that 600 sec then
remove the deadlock
DB01 shows Exclusive HOLDs and Exclusive WAITs situations.
HOLD & WAIT situation occur when a resource is held by a user/process exclusively which
is called a HOLD, and another process is trying to access it and goes to a WAIT situation.