This wiki describes the /SDF/MON report and how this can help the troubleshooting process.
Some SAP troubleshooting process require a clear picture about the system behavior with information about the infrastructure like OS and SAP resources. This clear picture should not be cluttered information or just single point information. This analysis should engage the resources situation ahead of the time of the issue and throughout the course of the problem. For this purpose the /SDF/MON report helps to collect all of these details.
The main purpose of this report is to collect snapshots of monitoring detail and store these details for later analysis. There are available SAP specific data like work process status, dispatcher queue, sessions, RFCs, Enqueue and also OS specific details like process at OS level, memory and CPU consumption by process.
The first step required is to schedule the execution of the report, for this purpose is it required to run the transaction /SDF/MON or over SE38 with the same name.
In the following screen, choose the option “Schedule New Monitoring”
In the next window, it is time to define what are the options collected in each snapshot triggered:
List of work process (SM50) = output of SM50;
CPU time per workprocess = corresponding CPU consumption is collected;
SQL statements = information about running SQL statements is collected if this is a ORACLE DB. This option can consume a large amount of data;
Store Reference to ABAP Source = the corresponding ABAP source will be collected for SQL Statements. Supported by ORACLE;
Dispatcher Queue = Information about the queues of dispatcher (DIA, UPD, etc). Data from SM51 -> Goto -> Information -> Queue Information;
CPU and Paging Activity = Data from SAPOSCOL about the hardware resources consumption from OS level;
Top CPU Processes = CPU consumption from OS process level. Data from SAPOSCOL;
Ext. and Heap Mem = Memory areas from SAP level. Data from ST02;
Memory per Modes = Memory overview from user sessions. Data from SM04;
Free RFC WPs = the sum of dialog work processes that are available for RFC Server group processing. Data from SARFC;
Statistical Records = This information is not available to SAP BASIS releases > 7.0.
Enqueue Entries = Store Enqueue table data. This is the same information available in SM12 list of locks.
Enqueue Statistics = Same information from SM12 -> Extras -> Statistics;
Inbound queues = Collect statistical information from table TRFCQIN;
Outbound queues = Collect statistical information from table TRFCQOUT;
SAPOSCOL destination = A destination for which ST06 related data can be collected (CPU and Paging Activity &Top CPU Processes) from an external server.
In the main window of the program, it is possible to search by a specific Analysis or list all analysis clicking in Execute. In the list, you do find all recorded analysis.
By double-click on the selected analysis a new window is open with all snapshots defined in the time interval.
Each column available may forward you to specific details about the data collected. Click in specific columns a new window is open with the specified details:
To analyze Enqueue specific details or Inbound or outbound queues it is required to open the option in the menu Goto -> Choose “Enqueue Entries”, “Enqueue statistics”, “Outbound queue” or “Inbound queue” by selection a “Global Data” in the grid that is only record every time configured on setting “Every N time(s)”.
/SDF/MON_START: Start the analysis with a set of parameters
/SDF/MON: Display and delete analyses
/SDF/MON_REORG: Delete obsolete analyses when expiration date is exceeded – to be scheduled as background job
/SDF/MON_STOP: Stop running analyses immediately
/SDF/MON_START_CM: Schedule a continuous monitoring Report
There are predefined charts using the option “Choose Layout” a graph from the monitoring time is created as per the choose layout
This is an example of CPU profile graph where the “user CPU” vs “System CPU” is created.
It is also possible to create customized charts. To create charts it is required to select the desired information in the Monitor Data window: