Question:
Hi Experts
I know the critical transaction which are use to monitor performances in SAP system, I have been working in basis in Security side and transport management, spool administration but not at very high level, but I have good idea about that all stuff. Can you please tell me how should I start looking performance analysis transactions, as I know what is ST02, ST03 db02, 3,4,5,12 and Os collector programs and transaction to see operating systems os01, 2,3,4,5. But one have to have good idea to see what are the bottle necks and on which basis one must decide, should I follow the standard help and there parameters? Or there is any rule. I badly need assistance.
Answer:
There is a lot of information available in this forum itself on perfromance bottlenecks. Just do a search for performance monitoring, tuning, bottlenecks etc.. and you should find a great deal of information. Since you are already familair with the transactions and programs, it would very helpful.
Answer:
There follow some notes I made about 5 years ago.
They are really a check list.
The indentation was important to the meaning but this web-site removes tabs and leading spaces so you are stuck with >s.
These notes may not mean anything to anyone but me - ho hum.
They are more than you deserve.
Problem Analysis
1. Hardware Bottlenecks
>Operating System monitor OS07 to choose a server; ST06/OS06 for a current server
>>CPU idle should be > 20% preferably > 35%
>>>Look at Detail Analysis -> Top CPU processes
>>>>See if any using large % can be stopped
>>>>For R/3 (disp+work) find PID in SM50/SM66
>>>>For Oracle find Oracle PID in ST04->Detailed Analysis-> Oracle Session - find corresponding R/3 PID in SM50/SM66
>>>>For external see if process can be stopped
>>Load average should be < number of processors(count)-1
>>Note memory in physical memory available
>>>Double click pages in/s to get pages in/h
>>>>Paging should be <20% of physical memory available
>>>Identify high memory consumption
>>>>ST02 -> Detailed Analysis -> SAP memory -> Mode List
>>>>SM66 -> Process List -> Display -> Memory usage
>>>>>Look for high memory programs
>>>>SM04 -> Goto -> Memory
>>>>>Look for high memory and high paging users
>Workload Monitor ST03 (ST03N is available after 4.6)
>>Average response time should be < 1 sec
>>>General performance problem - check components of response time
>>Wait time should be < 10% of response time
>>>10% is SAP recommendation - we would hope it is minimal.
>>>General performance problem - possible shortage of work processes
>>Database time should be < 40% (response time - wait time)
>>>Analyse database
>>Processing time = response-wait-DB-roll-load should be < (CPU time X 2)
>>>Hardware bottleneck - OS07/ST06/OS06
>>Load Time should be < 50ms
>>>Program buffer too small - ST02 look for swaps
>>Roll in/Roll out should be < 20ms
>>>Check extended memory/roll area - ST02->Detail Analysis->SAP memory->Mode List
>>>Could kill any excessive use of extended memory
2. Expensive SQL
>Workload Monitor ST03 -> Transaction Profile -> Sort on Response time
>>CPU time should be < 40% (response time - wait time)
>>>ABAP trace SE30
>>DB request time should be < 40% (response time - wait time)
>>>SQL trace - ST05
>>SM50 - look for reports and tables with long time
>>>Check with ST04 & DB01
>Database Process Monitor ST04 (ST04N available after 4.6C)
>>Detailed Analysis menu -> Oracle Session
>>>Shared SQLarea - identify program SM66 & ST04
>>>>Buffer gets gives the database load (sort to find maximum)
>>>>Bufgets/record - highest could be tuned
>>Database Lock Monitor
>>>Check process in ST04 - delete lock if necessary
>SQL Trace ST05
>>FETCH <5ms per record or <100ms per FETCH or bufgets per record <5
>>>means lots of records accessed efficiently - tune ABAP
>>FETCH >500ms or bufgets per record >5 means inefficient search strategy - tune SQL
>EXPLAIN from ST05 or ST04 Oracle session or ST04 Detailed Analysis
>>Double click table to find indexes and refresh data
>>>DB20 update stats for one table
>Tune ABAP
>>System -> Utilities -> Runtime Analysis -> Execute -> Tips & Tricks
3. Table Buffering Monitoring ST10
>Question buffering for tables at top of list after various sorts
>>Sort by invalidations
>>Sort by buffer size
>>Sort by rows affected under DB activity
>>Sort by total under ABAP processor requests
4. Workload Balancing
>Check server dispatcher queues
>>Queue usage
>>>SM51 -> Select a server -> Goto -> Server information -> Queue Information
>Compare workload
>>ST03 Detailed Analysis menu -> Compare all servers -> Graphics
>>>Can only check Total response time & Dialog steps (not dialog)
>Check work process CPU usage
>>SM66/SM50 -> CPU
>>>Last work process of each type should have CPU=0:00
>>>>Too few work processes or a blockage
>Check for even user distribution
>>SMLG -> Goto -> User List or AL08
>Check for even load distribution
>>SMLG -> Goto -> Load Distribution
>Update Monitoring
>>SM51 check maximum request wait is close to zero
>>SM51 -> Select a server -> Goto -> Queue Information
>>>Check update work process queues
>>SM13
>>>check number of updates status INIT should be small say < 10
>>SM12 Number of lock entries
>>>ensure updates are not disabled
>>>usually a few hundred, occasionally tens of thousands
5. D/B performance problems
>Check Oracle stats
>>DB14 to ensure update job ran correctly
>>DB02 to check stats for a specific table
>Oracle Performance Overview ST04
>>Data buffer hit ratio should be > 94%
>>>Ensure no poorly qualified SQL before increasing the size of the buffer
>>Efficiency of shared pool
>>>User/recursive calls should be > 2
>>>Data dictionary cache quality should be > 80%
>>>Pin ratio > 95%
>>>>Increase the pool size if any problems
>Look for Exclusive lock waits - DB01
>Unnecessary SQL statements
>>ST04 -> detailed analysis -> SQL request
>Sort by buffer gets - look for high total executions with high bufgets/record
>>To find statement
>>>SE12 where-used list or
>>>SM66 or
>>>ST04 ->detailed analysis -> oracle session
>Expensive SQL
>>Bufgets of one statement (ST04 -> detailed analysis -> SQL request)/ Total reads of all SQL (ST04) should be > 5%
>>>Run explain
>Look for missing Indexes - DB02
>Check for IO contention
>>ST04 -> Detailed analysis -> File system requests
>>>If reads & writes low then no contention
>>>Else if read time > 30ms or write time > 50ms
>>>Else if values > 20% of average read & write times
>Check for fragmented indexes
>>DB02 -> Detailed analysis???
>>>Look for fill level < 50% for frequently used indexes
Answer:
Hi Bonzo
You make my life easeir , thanks a lot , i am in USA , Nj and u ?
If you have still anything which can be useful in the context of performance please send me at sap_abap_basis@yahoo.com
Take cares Bye
Answer:
I think you misunderstand our relationship.
You need knowledge.
I have an irresistible desire to show off.
This forum is the maximum opportunity for us both to find satisfaction.
Bonzo, a Scouser - if it matters
Answer:
I have gone through different performance transactions which have mentioned and also which I know reading SAP performance. I also see the SAP help , and also keep in mind what are the standard things which SAP set , that after that you should worry about %ages in different area of performance.
I also match with you above given list , if I see my server per transaction , its looks like everything is ok , and its memory , its tables spaces , and idle time , response time is ok.
This is the system which is actually handover to me and I still have to prepare some document which shows that there is something missing , or need to be look and work . only know the system goes busy on Monday and Tuesday .
I also see there are no bath jobs like OS_colloctor and the standard list of programs which SAP recommends run on daily on monthly basis .
Should I also configure them into my system? Please assist me as per your experience .
Job Name ABAP Program RequiredVariant How Often?
SAP_REORG_JOBSDeletes old background jobs. RSBTCDEL You must create a variant. Daily
SAP_REORG_SPOOLDeletes old spool requests. RSPO0041 You must create a variant. Daily
SAP_REORG_BATCHINPUTDeletes old batch input sessions.This job may not run at the same time as normal batch input activity. Schedule this job for periods during which no batch input sessions are run. RSBDCREO You must create a variant. Daily
SAP_REORG_ABAPDUMPSDeletes old dumps produced by ABAP abnormal terminations.Alternative: To keep from needing to schedule this job, run the ABAP report RSNAPJOB from the ABAP editor instead. This schedules RSSNAPDL as follows:Job name: RSSNAPDLVariant name: DEFAULT (you must create this variant)Start time: 0100 AMRepeat interval: Daily RSSNAPDL You must create a variant. Daily
SAP_REORG_JOBSTATISTICDeletes job statistics for jobs not run since the specified date (statistics no longer needed since job was a one-time occurrence or is no longer run) RSBPSTDE You must create a variant. Monthly
SAP_REORG_UPDATERECORDSDeletes old completed update records (automatic delete deactivated); deletes incomplete update records (automatic delete deactivated) Run this job ONLY if: · You have deactivated the default automatic deletion of update records once they have been processed. This function is controlled by the system profile parameter rdisp/vb_delete_after_execution· You have deactivated the default automatic deletion of incomplete update records (records that are partially created when an update header is created and saved but the generating transaction then ends abnormally). This function is controlled by system profile parameter rdisp/vbreorg· You have deactivated processing of V2 update components after the processing of the associated V1 updates. This function is controlled by system profile parameter rdisp/vb_v2_start. RSM13002 None. Daily
SAP_COLLECTOR_FOR_JOBSTATISTICGenerates runtime statistics for background jobs RSBPCOLL None. Daily
SAP_COLLECTOR_FOR_PERFMONITORCollects system performance statistics This job was previously called COLLECTOR_FOR_PERFORMANCE_MONITOR. When scheduling this job, be sure to use the new name. RSCOLL00 schedules all reports that need to run for the performance monitor using table TCOLL to determine what to run. See the CCMS Guide for more information on setting up RSCOLL00. RSCOLL00 None. Hourly
a
Thanks
Bye
Answer:
Run SM36
Press button Standard jobs
etc.
Answer:
think you misunderstand the list of questions, i know this how to set jobs and other stuff in sm36 as i am ABAPer too:) , any way i want to ask you that our prod server is running fine , the SAP programs which i mentioned are not in the batch jobs should i schedule them ? and 2nd thing i cross check with your given %ages and SAP recommended % ages , system is running smooth , there is no problem in it .
Now question is that what i want, actually the guy left the company and they handover me the system so i can give them some feedback about them and i cant say them in Single word that system is running fine, i have to come up with some analysis so i can present them and convince them, so i am asking how i can do that? i have bigger context , i know the symptom’s but still i am lost help me
Bye
Answer:
Yes you must run standard jobs.
If you do not know this and can not answer the question 'is the system running efficiently?' then maybe you have the wrong job.
I know it's a bit harsh, but you have details of what is acceptable performance and you say your system matches it.
Isn't that the detail you provide them with.
... or perhaps you should run a SAP Earlywatch report and give them that.
Answer:
well you are saying right but when you are on project and you are hire for something else they are asking you to do it also after giving 2 hours crash course ... so you have no way out ..
Any way can you give me some of the reports name of SAP Earlywatch.
so i can execute and see , like i analyze the system , i excute the transdactions but some how i want that i have to be good enough to answer all of the question, i know its take time and effort and i am ready for that .
Becuz every time you have to start from somewhere Right ?
bye
Answer:
Biting my tongue...
Earlywatch is a service SAP provide.
You run jobs to collect data on your system.
Weekly it is sent over the internet to SAP.
SAP automatically produce a report on your system.
SDCC is a transaction you need but I think you need to look up Earlywatch on SAPNET.
You are right that everyone needs to start somewhere - I just don't think it is here.
Answer:
Thanks and i`ll let you know how good i am after month or so
Quote " First beliver then Achiver " ,
but thanks for your help .
Bye
Answer:
Hey Mr. Performance,
This might help u setup EWA:-
1) Check SAP Note 207223 - Activating the SAP EarlyWatch Alert (EWA)
2) Schedule background Automatic Session Manager to collect & sending of data to SAP by:
SM36
Job Name: AUTO_SESSION_MANAGER
ABAP Program: BDLATRUN
Periodic: Once a week.
Date: set it few days before EWA date.
Also just a comment, i think you can convince your management guys with some graphical representations of the servers CPU + Disks utilizations.
Cheers,
Thaiboy.