An analysis of a system is required (BW, SRM, ERP, CRM etc)
You require to know what transactions are available to analyze general performance problems in the system. You need a breakdown of possible transactions and how they may help in gathering sufficient data for further analysis. The transactions may look different depending on SAP release, Operating System and Database type
The following is a list of the most important performance analysis transactions and brief explanation of their purpose:
1) ST02 SAP Memory Configuration monitor checks the SAP Buffers and SAP Memory areas for problems such as swapping. It is a snapshot about the utilization of SAP shared buffers. High water marks of utilization for example extended, roll, paging and heap memory can be obtained from the SAP memory configuration monitor
2) ST03N: General performance statistics such as response time. This workload monitor can show response times daily/weekly/monthly and is the primary tool for checking dialog/background/update/spool/rfc response times
3) ST04: A snapshot of databuffer/cache quality, SQL cache catalog/pin ratio. For further detailed analysis click button 'Detail Analysis Menu' ST06: The Operating System Monitor is used as a snapshot of CPU utilization, RAM, Swap space. For further detailed analysis click button 'Detail Analysis Menu'
4) SM66: The main tool used for monitoring current system activity via the Global Work Process Overview
5) ST22: Store for ABAP Dumps such as - All dumps beginning with TSV_TNEW -DBIF_RSQL_SQL_ERROR - DBIF_RSQL_INVALID_SQL_ERROR - TSV_INDEX_INDEX_NO_ROLL_MEMORY - SYSTEM_NO_ROLL - SYSTEM_ROLL_IN_ERROR - TABLE_HASH_NO_MEMORY - STORAGE_HASH_NO_MEMORY - STORAGE_PARAMETERS_WRONG_SET - SAPSQL_ARRAY_INSERT_DUPREC SM21: Look for messages like : - Printer problems - Signal 11 - Short dumps - Time-outs - Matchcode problems - Aborted postings
6) SM04: Active Users and number of modes of same. Also check memory, page, roll, priv usage via goto->memory
7) AL08: The number of active users can be otained from the Global User Monitor
8) SARFC: An overview of server resources and under column description whether there is a problem AL11: List of SAP directories
9) DB01: Is a snapshot about exclusive wait situations using the Database Lock Monitor
10) DB02: Check database growth, freespace in tablespaces, critical objects, extents of tables and indexes
11) DB12: Check backup/restore situation DB16: On Oracle check for search for messages with the "SEVERITY" type "E" (error) that occurred in the last 4 weeks.
12) DB24: Check administration tasks such as backup/recovery, archive frequency, administration tasks
13) Report /SDF/MON: The tool allows for the collection of data on CPU Utilization, Memory Management, Database Performance, Work
Process Utilization, Workload, STAD, RFC etc.
The information linked with each of the above areas is stored in the database for further usage. The data can be collected for predefined periods of time and for a set frequency of seconds
14) STAD: Used to check the response time of programs/transactions and provides various levels of detail which can be tailored.
15) ST14: The ST14 application monitor is mainly used during SAP GoingLive session. Analysis batch jobs collect performance-relevant key figures such as document statistics and customizing settings, the analysis results can be viewed as a tree and downloaded to a service session. See SAP Note 69455.
16) ST05: ST05 traces every action of a user on a server. SQL trace needs to be switched off and the ST05 writes trace files into the local filesystem and overwrites them circularly.
17) ST12: ST12 combines ABAP and performance (SQL) trace into one transaction, with major functional enhancements especially for the ABAP trace part. In a joint switch on/off with the performance trace, ST12 allows to activate the ABAP trace for another user. See 755977. The ST12 can also be used for tracing work process, program/transaction or a user. At a click of a button, you can view the SQL and ABAP trace information.
The following provides information on the DBAcockpit DBAcockpit Monitoring System Landscapes Using the DBA Cockpit
- www.sdn.sap.com/irj/sdn/go/portal/prtroot /docs/library/uuid/107aa3f5-2302-2a10-f990-b4d2af1aaca0
SDN Article The SAP DBA Cockpit for Microsoft SQL Server https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs /library/uuid/1062428c-f1df-2910-b08f-c322feddcd10
Other databases: SDN Article 'What's New in the DBA Cockpit with SAP NetWeaver 7.0 (DB2 LUW)' www.sdn.sap.com/irj/sdn/go/portal/prtroot /docs/library/uuid/a0dc0752-2502-2a10-2a93-94823467ca79)
SDN Article DBA Cockpit the new look and feel for database monitoring and administration (DB2/zOS) ( www.sdn.sap.com/irj/sdn/go/portal/prt root/docs/library/uuid/90e27c26-24fb-2910-e8a5-c477cef80 d91)
SDN Article DBA Cockpit for Oracle Database Admin www.sdn.sap.com/irj/sdn/ora or www.sdn.sap.com/irj/sdn /go/portal/prtroot/docs/library/uuid/ f0e1921b-32e2-2910-d38a-bce867339dc9)
Downport to 7.00 transactions that can be used depending on the current information about the retrofit of the DBA Cockpit for SAP systems based on 7.10 kernel to SAP NetWeaver 7.0, read SAP 1027146.
Other useful transactions that can be used depending on circumstances: SM58 SM59
SMQ1 SMQ2 SMGW SDCCN SM37 SM51 SM50 RZ04 RZ10 RZ20 SE16 SE12 TU02 DB03 SMQS DB21 SMQR SM13:
In the event that you cannot get a satisfactory performance for a transaction/program try searching for notes using the keywords performance and the name of the transaction causing problems to see if anything exists to help. Discuss with your developers/programmers if performance improvements are possible.
For performance problems caused by customer programs SAP offers SAP Customer Program Optimization (http://service.sap.com/cpo) by eliminating costly performance bottlenecks by tuning critical customer programs.
You profit from optimized response times and throughput. - Optimal use of your hardware resources - Increased productivity - Higher acceptance by end-users Also ensure you have setup Earlywatch Alert as per SAP 207223. A good starting point for performance documentation is:
- http://service.sap.com/performance http://service.sap.com/earlywatch http://service.sap.com/goinglivecheck
- http://service.sap.com/safeguarding