At the beginning of writing this page I better confess that the strategy I used is not always a recommended process but obviously my own learning. Besides SAP performance tuning is always a new chapter in any-ones learning diary.

Tuning of an SAP system is actually a a job of a team containing specialists from different IT functions e.g, OS, Database, Storage, Network and Collaboration, SAP – Basis, SAP – ABAP and overall the SAP – Functional. This  is not one man show at all, because it involves the hardware, operating system, clustering software if any, the database, SAP application, network and user behavior. Added to all of them you will have a lot of limitation on the supporting and non supporting mandates from different vendor including SAP, and non communicative attitude of the engineers and consultant working in a SAP setup is a free gift with the product.

Consider a landscape of open source operating system, and SAP with Oracle database, almost 5000 concurrent users across the globe and very strict SLA with max 2 hours schedule downtime a month. Let’s start from a very odd news, your system admin called you up at midnight asking you that CPU utilization of your database server went beyond 85 % and you need to act upon finding out the actual culprit and then act accordingly. This you need to accomplish, in a very short time span. Because a little extra pressure in the system may lead to a hung state and you need non other than a shutdown what you hate.

Consider this case where you will find that the even a standard SAP program is giving timeout or memory problem and this is happening at the right time, that is the busiest time – book closing time….Or consider a customised program is causing nuisance, i.e. your DBA reporting you that the generation of redolog increased 20 times which is not at all what you can expect and also effecting your current DR strategy.

Worst even you may find a transaction generating excessive locks and the whole system appearing to standstill do the peer users across the globe who is trying to use the same transaction or using transaction which is using same underlying object. This is quite obvious, that lot of similar other issues will add up in the list. I will try organising the same in different criteria like Database, SAP, OS etc and in the sub pages will go adding them.

Once again, this is not a directive, but a sharing of experience how I do it….Wherever possible I will go on citing the references of SAP notes, Oracle Metalink etc but this is purely my own way to do, I got success most of the cases, and if it can help you nothing like it…..

I will always wish to share my experience and understanding, and go on writing, because I like the idea of Indians, idea of utilisation of anything they posses till to its last end and thus utilising the value for money. Like news paper ends up in handmade packets and even a kite to child hand.

I have rewritten the portion of this page to provide the index link so that it can be easily referred.

***************** Index of Pages on the topic…. ****************************
1. SAP Tuning – Gather Symptoms.
2. ST04 – A Magic Transaction for SAP performance tuning – I
3. ST04 – A Magic Transaction for SAP performance tuning – II
4. ST02 – SAP Tuning – Another Magic transaction – I (Part 4)
5. ST02 – SAP Tuning – Important SAP Parameters – II
6. ST03n – The meter gauge for SAP tuning
7. A handy reference for SAP Memory

1 thought on “/SAPTUNE

Leave a Reply

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

WordPress.com Logo

You are commenting using your WordPress.com 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