SAP Performance Tuning

SAP Performance Tuning

One needs to understand OS, Networking, Hardware, RDBMS and clustering to troubleshoot the performance issues of any ERP Application. SAP  provides very good transaction codes for monitoring and troubleshooting the performance issues in all the layers. 

During the process of analyzing the root cause of performance issue, one has to make sure the CPU is not close to 100% usage, if

– CPU is not close to 100%, then any monitoring tools like Toad, foglight, and Grid control will help in resolving the performance issue. If CPU is 100%, the use of above tools will not help because 

1. It is a very time consuming process or
2. CPU may block these tools from connecting 

In that case, use of native tools like SQL plus, NIping, Netstat, sar, vmstat, mpstat, top, ps, iostat, msprot, ensmon, dbmon, msmon etc will help.

Even though Oracle provides some features like ADDM and SQL Tuning Advisor for Performance tuning, it would be better to understand the functionality of Optimizer technology.In real time ADDM and SQL Tuning Advisor helped me to tune optimize the performance of Database Batch jobs (which reduced the time from 14 hours to 3 hours).But further manual tuning (using MV and SQL hints) reduced the time to 30 min.

Certain Database (like in Tele industry) is very sensitive and need immediate attention in case of any critical performance issues.This situation can be related to table buffer/lock issue (SAP) or latch/lock/Bad queries (Oracle) or Disk IO queue issue (Operating system > 30%) or message server is not coming up in MSCS environment after the MSCS resource switch over (because message server port not released from the old Active host , netstat -a would help) or MSCS cluster freezing at shared disk level (cluster level – quorum disks). 

In general use the given sequence below to start with any troubleshooting issue.

Level 1 –> OS
Level 2 –> Network
Level 3 –> Oracle 
Level 4 –> SAP 

Level 1 (OS)

AL11 – SAP Directories
OS02 – OS configuration
OS06/ST06 – OS monitor 
SM50 – Process Overview

Level 2 (Network)

OS01 – LAN Check via ping

Level 3 (Oracle)

DBA CockPit – Configuration and Maintenance (Wonderful Tcode)
DB01 – Oracle Lock monitor
DB02 – Database Performance
DB03 – Parameter changes at the database level
DB12 – Backup logs
DB17 – Database check condition
DBCO – Database connections
ST04N – Database Performance Monitor
DB20 – Table statistics
DB16 – Databse checks
DB14 – DBA log display

Level 4 (SAP)

AL12 – Buffer monitoring
ST01 – System Trace
ST02 – SAP Memory Monitor
ST03N – System Load monitor
ST05 – Performance Analysis
ST07 – Application Monitor
ST10 – Table Access Statistics
SM50 – Process Overview
SM12 – Lock entries
SM59 – RFC Connections
SMICM – ICM Monitor
SMMS – Message server monitor
Finally CCMS

Hope this helps.


Leave a Reply

Fill in your details below or click an icon to log in: Logo

You are commenting using your account. Log Out /  Change )

Google+ photo

You are commenting using your Google+ account. Log Out /  Change )

Twitter picture

You are commenting using your Twitter account. Log Out /  Change )

Facebook photo

You are commenting using your Facebook account. Log Out /  Change )


Connecting to %s