Professional Documents
Culture Documents
This to be very handy when we have a situation where we require troubleshooting in terms of
performance as you can see exactly what was running when, how much memory/cpu utilization etc.
To start the collection, run transaction /n/SDF/MON or go to SA38 and execute job /SDF/MON.
Click on SCHEDULE NEW MONITORING
Fill in the desired parameters like the duration of the analysis and the interval for the snapshot and
execute
On this page you can double click on the DIA/CPU/FREE MEM etc. to get and overview of what
was running on the system at that exact time.
From Figure 2, you know that SM50 snapshots were collected at the interval of 60 seconds.
1.3 Display /SDF/MON monitoring data for the specific entry
Assume that I would like to know historical work process information for the job on Mar 11
(highlighted in figure 2) , double click it, I had following screen
I clicked execution button after my input, data set is reduced. Please refer to Figure 5.
You can see snapshot is showed every half hour and only for specific servers in Figure 5.
1.5 Display all work process snapshots related to specific job using restricted WP list feature
First I clicked the button
to select all entries, see Figure-5 to know where the button is. Selected
enter restriction criteria. Here I enter the job name ZFXXIO_ANALYSIS_NORMAL. Please refer
to Figure -6.
Then I clicked the execution after my input, I got SAP work process overview screen which contains
work process for the specific job. Please refer to screen 7.
Figure 7 /SDF/MON single jobs historical work process overview for every half hour w/I 10 hours
Based on Figure 7, you can know that the job seems stuck at reading table COAS based on workflow
status took every half hour during a 10-hours window. How about every 5 minutes for one hour?
Following the same fashion, I got following work process overview data:
Figure 8 /SDF/MON Single jobs historical work process overview for every five minutes in one hour
So based on Figure 7 and 8, we know that the job are spending time on reading COAS (view) and
corresponding SQL is very expensive and the root-cause of slowness for the running period so far.
Analysis SQL access path is not focus of this post. However, I found the execution plan for the above
SQL ( See Figure 9). It is using AUFK~E index to access AUFK table, but none of SQL fields in the
where-clause matches the index that is the issue.
Here, I demonstrated how to use job name to find and display all SM50 snapshots for a single job in
click. You can use UserID , process id and process types etc. ( see figure 6) to restrict the work
process display as well. You can display SM50 snapshots for several jobs as well, so on.
2 Summary
UP to now, you should know how to display all snapshots of work process overview for specific
jobs, processes and users in one screen. This would help you to verify where time is spent by a
process during trouble-shooting. I have several postings on /SDF/MON in this website, you can
search them via key word /SDF/MON.