8/17/2019 948066 - Performance Analysis_ Transactions to Use

http://slidepdf.com/reader/full/948066-performance-analysis-transactions-to-use 1/4

SAP Note

  948066 - Performance Analysis: Transactions to use  

Version  7 Validity:22.10.2012 - active

Language  English (Master)

Header Data

Released On   12.02.2014 11:36:50

Release Status Released for Customer 

Component   SV-PERF Performance Messages

Priority   Recommendations / Additional Info

Category   Performance

Symptom

An analysis of a system is required (BI, SRM, ERP, CRM etc)

Other Terms

DBACOCKPIT, ST22, SM21, ST02, ST04, ST06N, ST03, Database, Performance, Transactions

Reason and Prerequisites

You require to know what transactions are available to analyze general performance problemsin the system. You need a breakdown of possible transactions and how they may help ingathering sufficient data for futher analysis. The transactions may look different dependingon SAP release, Operating System and Database type.

Solution

The following is a list of the most important performance analysis transactions and briefexplanation of their purpose. ST02 SAP Memory Configuration monitor checks the SAP Buffersand SAP Memory areas for problems such as swapping.

It is a snapshot about the utilization of SAP shared buffers. High water marks of utilizationfor example extended, roll, paging and heap memory can be obtained from the SAP memoryconfiguration monitor ST03N: General performance statistics such as response time. Thisworkload monitor can show response times daily/weekly/monthly and is the primary tool forchecking dialog/background/update/spool/rfc response times.

ST04 or DBACOCKPIT: A snapshot of databuffer/cache quality, SQL cache catalog/pin ratio. Forfurther detailed analysis click button 'Detail Analysis Menu'

ST06/ST06N/OS07: The Operating System Monitor is used as a snapshot of CPU utilization, RAM,Swap space. For further detailed analysis click button 'Detail Analysis Menu'.

8/17/2019 948066 - Performance Analysis_ Transactions to Use

http://slidepdf.com/reader/full/948066-performance-analysis-transactions-to-use 2/4

SM66: The main tool used for monitoring current system activity via the Global Work ProcessOverview

ST22: Store for ABAP Dumps such as - For example the following would be critical dumpsbeginning with TSV_TNEW -DBIF_RSQL_SQL_ERROR - DBIF_RSQL_INVALID_SQL_ERROR - SYSTEM_NO_ROLL -SYSTEM_ROLL_IN_ERROR - TABLE_HASH_NO_MEMORY - STORAGE_HASH_NO_MEMORY -STORAGE_PARAMETERS_WRONG_SET - SAPSQL_ARRAY_INSERT_DUPREC

SM21: Typical messages like : - Printer problems - Signal 11 - Short dumps - Time-outs -Matchcode problems - Aborted postings - ORA errors

SM04: Active Users and number of modes of same. Also check memory, page, roll, priv usage viagoto->memory

AL08: The number of active users can be obtained from the Global User Monitor SARFC: Anoverview of server resources and under column description whether there is a problem

AL11: List of SAP directories

DB01: Is a snapshot about exclusive wait situations using the Database Lock MonitorDB02: Check database growth, freespace in tablespaces, critical objects, extents of tablesand indexesDB12: Check backup/restore situationDB16: On Oracle check for search for messages with the "SEVERITY" type "E" (error) thatoccurred in the last 4 weeks

DB24: Check administration tasks such as backup/recovery, archive frequency, administrationtasks Report/SDF/MON: The tool allows for the collection of data on CPU Utilization ,Memory Management,Database Performance, WorkProcess Utilization, Workload, STAD, RFC etc. The informationlinked with each o f the above areas is stored in the database for further usage. The datacan be collected for predefined periods of time and for a set frequency of seconds STAD: Usedto check response time of programs/transactions and provides various levels of detail whichcan be tailored.ST14: The ST14 application monitor is mainly used during SAP GoingLive session. Analysisbatch jobs collect performance-relevant key figures such as document statistics andcustomizing settings, the analysis results can be viewed as a tree and downloaded to aservice session. See SAP Note 69455. ST05: ST05 traces every action of a user on a server.SQL trace needs to be switched off and theST05 writes trace files into the local filesystem and overwrites them circularily.

ST12 combines ABAP and performance (SQL) trace into one transaction, with major functionalenhancements especially for the ABAP trace part. In a joint switch on/off with theperformance trace, ST12 allows to activate the ABAP trace for another user. See Note 755977.ST12 can also be used for tracing workprocess, program/transaction or a user. At a click of abutton you can view the SQL and ABAP trace information.

Other useful transactions that can be used depending on circumstances: SM58 SM59,SMQ1 SMQ2SMGW SDCCN SM37 SM51 SM50 RZ04 RZ10 RZ20 SE16 SE12 TU02 DB03 SMQS DB21 SMQR SM13:

List of useful notes that may help

146289 Parameter Recommendations for 64-Bit SAP Kernel825653 Oracle: Common Errors806554 FAQ: I/O-intensive database operations

805934 FAQ: Database time797629 FAQ: Oracle histograms793113 FAQ: Oracle I/O configuration386605 SAP Memory Management for Linux724713 Parameter settings for Solaris 10195471 SAP Banking performance192658 Setting basis parameters for BW systems146528 Configuration of R/3 on large RAM127715 CBO: Optimum parameters for performance123366 Maximum addressable memory for the Oracle SGA

172747 HP-UX Operating System kernel parameter recommendations1077887 SAP on HP-UX:mount & filesystem options for best performance1075118 SAP on HP-UX: FAQ

941735 LINUX parameters

1048686 Recommended AIX settings for SAP143646 AIX patches for new memory management856848 AIX extended memory disclaiming and note973227 AIX Virtural memory management parameter.323816 AIX user limits

8/17/2019 948066 - Performance Analysis_ Transactions to Use

http://slidepdf.com/reader/full/948066-performance-analysis-transactions-to-use 3/4

78498 AIX pag ng rates789477 Large extended memory on AIX (64-bit) as of Kernel912425 AIX: Unexplained high memory consumption1121904 SAP on AIX: Recommendations for paging space

1085937 Wait Event Analysis For SQL Server111291 FAQ: SQL server analysis and avoiding deadlocks1152848 FAQ: SQL Server Wait Events1237682 Configuration Parameters for SQL Server 2008555223 FAQ: Microsoft SQL Server62988 Service packs for Microsoft SQL Server806342 FAQ: Analyzing exclusive database locks on SQL Server

846890 FAQ: MaxDB Administration912905 FAQ: storage systems used with MaxDB822239 FAQ: MaxDB Interfaces832544 FAQ: MaxDB Hints819324 FAQ: MaxDB SQL optimization952783 FAQ: MaxDB high availability928037 FAQ: MaxDB Indexes

1692571 14 48 DB6: DB2 10.1 Standard Parameter Settings

899322 DB6: DB2 V9.1 Standard Parameter Settings1086130 DB6: DB2 V9.5 Standard Parameter Settings1329179 DB6: DB2 V9.7 Standard Parameter Settings101809 DB6: Supported Fix Packs IBM DB2 for Linux, UNIX and Windows

In the event that you cannot get a satisfactory performance for a transaction/program trysearching for notes using the keywords performance and the name of the transaction causingproblems to see if anything exists to help.

You can also open a message on SV-BO component. Ensure connection to system is open and thatuser has authorization for transactions [see point 5 in note 160777]. If issue isreproducible include a full example with screenshots if necessary.

Discuss with your developers/programmers if performance improvements are possible. Forperformance problems caused by customer programs SAP offers SAP Customer Program Optimization(http://service.sap.com/cpo) by eliminating costly performance bottlenecks by tuning criticalcustomer programs. Ensure you have setup Earlywatch Alert as per SAP Note 207223.

A good starting point for performance documentation is: http://service.sap.com/performancehttp://service.sap.com/earlywatch

http://service.sap.com/goinglivecheck

http://service.sap.com/safeguardingHANA:http://service.sap.com/hana

Validity

This document is not restricted to a software component or software component version

References

This document refers to:

SAP Notes

1266771 SRM 7.0 Performance Guide1169088 SRM 6.0 Performance Guide

618868 FAQ: Oracle performance

91488 SAP Support Services - Central preparatory note

8/17/2019 948066 - Performance Analysis_ Transactions to Use

http://slidepdf.com/reader/full/948066-performance-analysis-transactions-to-use 4/4

This document is referenced by:

SAP Notes (4)

91488 SAP Support Services - Central preparatory note

1266771 SRM 7.0 Performance Guide

1169088 SRM 6.0 Performance Guide

618868 FAQ: Oracle performance