SAP System Performance Analysis Tcode

Reproduced in the original http://blog.chinaunix.net/uid-20607558-id-1916144.html thank the original author's summary and induction.

/nsmlt
Language management
Overview SAP Support Language

==for Manage Database
Http://help.sap.com/saphelp_47x200/helpdata/en/d0/1057cd20d96a43bde5d59291e8290f/frameset.htm

/nst04
Database Performance Analysis Overview

=======for role
/nsu01
Create User ID.
How to define a GOUNP?
What privilege does the username in a group include?
Group and role?

/npfcg
Create role
What are profile?

/nsu53
Check the unsuccessful privilege of last login

/nsuim
User Information System

========for System Analyze
/nst01
Trace system Internal activity

/nst03
Workload in System

/nst06
Operationg System Monitor

/nrz10
Maintain the parameter file
Instance profile
Default profile
Startup profile

/nsm36
Define Job

/nse01
Transport Manage

/nssaa
System manage Assistant. It shows all the Tcode's activity about system.

/nsa38
The interface of clear the log

/nsm02
Send a message to all user

/nsm12
Show the table lock

/nsqvi
SAP QUERY is a sinple the report develop tool. It does not need to program.

==========================================

One, SAP system management common to the transaction code
1. SM51 SAP Servers System Monitoring
2. SM21 SAP System Log
3. Srzl SAP Computer Center management System (CCMS) recommends that beginners focus on learning.
4. RZ20 Alert Monitor. Workload Alarm Monitor. (Under the CCMS)
5. ST06 Operating System Monitor for analyzing the performance of the entire SAP technology stack.
6. st03n Workload moniter, load Monitor, for drilling online and bulk loads, "40 most commonly used" transactions, peak load details, and transactions performed over a certain period of time.
7. SSAA is used to perform regular day, week, and month system management functions.
8. SMLG is used to monitor the balance of SAP login load, and F5 can drill down to the performance data for a specific user group.
9. AL08 is used to check for end users logged on to an SAP application server and to display the transactions they are performing.
ST07 is used to check the end-users who are logged into the entire system, and system users can classify them according to functional areas (such as SAP ECC,FI,MM,PM,PS,SD, etc.).
SM66 is used to view system-level performance related to the process execution of each application and batch server in the SAP system.
The ST22 is used to view the ABAP dump so that the program error can be identified. This helps to give feedback to the relevant department or development team.
Attached: SAP Online help.http://help.sap.com

Second, performance management-related CCMS transactions

(1) User and Application server distribution ST07 and AL08
ST07 lets you see how many users in the entire system, including all application servers, are logged in. You can also refine the numbers based on functional partitioning and view historical data.
The AL08 can show the total number of logged-in end users and can be divided according to the application server to which the user is logged on, so the application server load balancing of a system can be analyzed. The transactions performed by each end user can be displayed, allowing the system load types to be analyzed in real time.

(2) Managing load Balancing SMLG
Can be used to see how a login load balancing mechanism works. This transaction can be used to set up a logon group and to monitor the performance of each login group. Press F5 to view the statistics for each login group response. (Smlg can supplement the AL08 feature, showing the number of logged-in users, when each login group's response is displayed.)

(3) Database overview and performance DB02 and ST04
DB02 can track how the database grows over time, as well as track the number of indexes and their size, number, and historical trends.
ST04 (Database performance analysis) provides a real-time analysis of cache hit ratios, logical reads versus physical reads, critical "buffer busy waits (buffer Busy Waits)" values, and much more.
Note that if you need to determine the impact of a recent change on database performance, the statistics for these real-time data can be reset. With detail Analysis menu, you can drill down to the entire activity, exception events, based on specific SQL requirements or table access. Resource consumption and more historical data.

(4) Upgrade, lock and disk subsystem performance SM12 and SM13
If you want to know if the application of the upgrade is "committed" to the database if there is a lock entry, you want to pass SM12 (data lock entry, database lock entries and SM13 (Administrator update record, Administrator Update Records) to complete.
Use SM12 to browse for locked items associated with a database table, user, or customer.
Use SM13 to track and monitor real-time data upgrades.

(5) Memory management and optimization statistics ST02
Optimization statistics (Tune Summary) for real-time visibility into the memory of each SAP application server and the operation of multiple buffers. In the case of a load, if the buffer is not properly configured or is not optimized, then the swaps column will show that the value of the buffer is larger and highlighted in red, This makes it easy to identify the area where the problem lies.
ST02 not only manages the cache, it also keeps track of the memory usage of each application server. Pay particular attention to the current usage of extended memory (as compared to peak times). Again, it is often important to check whether the use of heap memory is minimized.
Heap memory is specific to the work process. When the program uses shared memory for the work process, it must take the PRIV mode of maintaining the memory independently. At this point, the executing program is unable to switch to another work process, it will be blocked until the program execution is finished. After the program is finished, the system restarts the work process. Everything is back to normal (where the program enters and exits the memory depends on the needs of the SAP system).
(6) Response time and load performance ST03 and st03n
Monitoring your own load is one of the most important components of performance management. The ST03 and st03n can execute the load monitor (workload monitor). It can show you the overall workload, or you can split the display based on conversations, batches, upgrades, and other task types. Click Transication The profile button sorts the results of each type according to the response. Here, you can analyze which work consumes the most database time (DB request time), CPU time, and the response time of other core components of the transaction program. You can also view the totals in different time periods, The time period can range from 15 minutes to 1 months. View and track the total number of conversations that are processed every hour of the day, so you can see the workload per hour of the day.
In addition, st03n can track the direct reading of data, sequence reads and changes (database updates or commits). In addition, it can obtain the average number of bytes per transaction request. This allows you to determine the disk load currently supported by a system.
In addition to purely response-time metrics, ST03 's "Time Pfofile" and "Transaction Profile" buttons also support quantifying the system load over a specific period, or determining which transactions are most commonly used based on a specific workload, and what related hardware loads are generated .
Transaction ST03G enables you to view and analyze the load associated with external systems, as well as the system performance analysis of business processes across multiple systems. This is a powerful addition to ST03.
In general, when the database is running correctly, the following parameter values should be met:
(1) Data buffer quality is at least 94%. After the system restarts, the Buffer value is generally not read immediately, at this time the qulity value is also very low, so by waiting until reads more than 20 000 000 to calculate the value of qulity.
(2) Time/user call<20ms
(3) SQL area pinratio>97%.

(7) OS Monitor ST06
OS Monitor (ST06) is another SAP transaction that can display a large amount of real-time performance data. It includes CPU utilization based on user, system, and idle time, CPU process queue (also known as CPU load count).
Memory OS monitoring also supports checking of short-term historical data; Click on "Datail Analysis menu, detailed analyzing tea list" can access to the main hardware subsystem and Application Server division of historical data information.
With these historical data, you can manage the disk performance metrics that are collected on the OS and the database in an SAP-visible way. You can also view the CPU load per hour over the last 24 hours, which makes it easy to determine the peak load and monitor and analyze the throughput performance of the CPU ( such as executing sp03n to see the number of conversations for a specific period of time). Similarly, deep SAP performance databases also enable OS Monitor It's easy to get a performance analysis of other general-purpose servers or a specific server. You can compare or correlate these numbers with the results you collect from your hardware-or OS-based performance tools.
OS Monitor or transaction ST06 provides real-time performance snapshots and access to historical data.
It can comprehensively analyze the CPU, swap space, and memory usage, and summarize the performance of the operating system.

(8) Monitor the activity work process SM50 and SM66
They can all view the activity of the working process in the system. SM50 shows all the work that is configured for a particular application server (which is actually the one you are currently logged into), while SM66 shows all the active work processes on all the application servers. In particular, SM66, it can get the number of active users or conversations on a server platform; Generally speaking, The faster the platform, the less the process will be in a certain period of time.
SM50: Work process Management, an application server typically has DIA,UPD,ENQ,BTC,SPO five types of worker processes.
Dia: for the foreground work process, a instance must have at least two dia, otherwise do not get up at all.
UPD,UPD2 is an immediate update process (some systems are vb1,vb2 processes), where the upd

Report:
%PC can help us to load the original SAP GUI output into Excel (in many other formats as well).

Third, other

Sbit Menu
SBTA test Background processing background processing tests
SBTU Background processing for user background processing
SM36 Define Background Job definition background jobs
SM37 Background Job Overview Background Job overview
SM39 Job Analysis
SM49 execute external OS commands execute external OS command
SM61 Menu
SM62 Menu
SM63 display/maintain Operating Mode sets display/Hold operation mode settings
SM64 release of an event
SM65 Background Processing analysis tool background processing tools
Job scheduling for SM67 job scheduling
SM68 Job Administration Jobs management
SM69 maintain external OS commands maintaining external OS commands
SMX Display Own jobs shows his homework
SPBM monitoring parallel background tasks monitor similar background tasks
SPBT Test:parallel Background Tasks text: matching background tasks
DB16 db System Check (TRIGGER/BROWSE) DB system Check (TRIGGER/BROWSE)
DB17 DB System Check (configure) DB system check (configure)
DB20 no.of Table Tupels acc. to stat. no.of Table Tupels Acc. to Stat.
DB21 Maintenance Control Table DBSTATC Maintenance Control Table DBSTATC
RZ01 Job scheduling Monitor Job schedule monitors
RZ02 Network Graphics for SAP Instances networks diagram SAP
RZ04 Maintain SAP Instances keep SAP instances
RZ06 Alerts Thresholds Maintenance alarm threshold maintenance
RZ08 SAP Alert Monitor SAP alarm Monitors
RZ12 maintain RFC server group assignment maintaining RFC-specified server groups
SM66 systemwide Work Process Overview System Working procedure Overview
SMLG Maintain logon Group maintenance
Srzl Menu
SM02 System Messages Message
SM04 User Overview Users Overview
SM13 Display Update Records displays updated records
SM50 Work Process Overview overview
SM51 List of SAP Servers SAP servers
SM54 txcom Maintenance txcom Maintenance
SM55 thost Maintenance Thost Maintenance
SM56 number range buffer Digital ranges buffers
SMGW Gateway Monitor
ST07 Application Monitor Application monitors
AL01 SAP Alert Monitor SAP alarm Monitors
AL02 Database Alert monitor DB alarm Monitor
AL03 Operating System alert monitor OS warning monitors
AL04 Monitor call distribution monitoring calls assignment
AL05 Monitor current workload monitors the workload
AL06 performance:upload/download Execution: Upload/install
AL07 Earlywatch Report Initial review
AL08 Users logged on login
AL09 data for database expertise expert databases
AL10 Download to Early watch download early watch
AL11 Display SAP directories show SAP Catalog
AL12 Display table buffer (EXP. session)
AL13 Display Shared memory (Expert mode) shows the share RAM (output mode)
AL15 Customize saposcol Destination Custom Saposcol destination
AL16 Local Alert Monitor for Operat.syst. Local alarm monitor for the operating system
AL17 Remote Alert Monitor F.operat. Syst. Remote Alarm monitor for the operating system
AL18 local File System Monitor
AL19 Remote File System Monitor
AL20 earlywatch data Collector list Earlywatch
AL21 ABAP Program An analysis of ABAP program
AL22 Dependent Objects Display Dependent objects display
DB01 Analyze exclusive Lockwaits analysis Mutex lock wait
DB02 Analyze tables and indexes analysis tables and indexes
DB03 Parameter changes in database parameter changes in databases
DB05 Analysis of a table Acc. to index analysis of a table Acc. to index
DB11 Early Watch Profile Maintenance Initial view description file maintenance
DB12 Overview of Backup Logs Backups log overview
DB13 Database Administration Calendar
DB14 Show SAPDBA Action Logs display SAPDBA behavior record
DB15 Ccms-document Archiving Ccms-document archiving
OS01 LAN check with ping checks lan by pinging
OS02 Operating System Configuration
OS03 O/S Parameter Changes O/S parameter change
OS04 Local System Configuration
OS05 Remote system cconfiguration Configuration
OS06 local Operating system activity native OS jobs
OS07 Remote Operating system activity
OSS1 Logon to online service system registration
SDBE Explain An SQL statement matching code object (test)
ST02 Setups/tune buffers set/tune buffer
ST03 Performance,sap Statistics, Workload performance, SAP statistics, workloads
ST04 Select DB Activities activity in the selected database
ST05 Trace for SQL, Enqueue, RFC, Memory SQL Trace
ST06 Operating System Monitor OS Monitors
ST08 Network Monitor
ST09 Network Alert Monitor internet Guardian
ST10 Table Call statistics tables invocation statistics
ST4A database:shared Cursor Cache (ST04) database:shared cursor cache (ST04)
Stat local transaction Statistics domestic transaction statistics
STP4 Select DB Activities Select DB Activities
STUN Menu Performance Monitor menus Performance Monitor
Tkof Turn off Oracle trace off Oracle Tracking
Tkon Turn off Oracle trace off Oracle Tracking
TKPR Display trace file displays trace files
TU01 Call Statistics Invoke statistics
TU02 Parameter Changes parameter change
SP00 Spool and related areas spool and related areas
SP01 Output controller Outputs control
SP02 Display output Requests
SP03 spool:load Formats spool: Load format
SP1T output Control (test)
SPAD Spool Administration Offline management
Spat Spool Administration (test) spooling management (testing)
SPCC Spool Consistency Check spool conformance checks
SPIC Spool Installation Check spool installation checks
SPTP Text elem. Maint. For print formats text element maintenance for printing formats
SP11 Temse Directory Temse Catalog
SP12 Temse Administration Temse Management
SE92 Maintain system log Messages maintaining Syslog messages
SM20 System Audit Log Systems audit logs
SM21 System Log Syslog
S001 Case Tool Menu Case Tool Menu
S002 Menu Administration Menus Management
SDW0 ABAP/4 Development WB Initial Screens ABAP/4 Development Workbench splash Screen
Syst Menu
SDMO dynamic menu (old)
Smen Session Manager Menus Conversation Management menu
SU55 Call the Session Manager menus invokes the Conversation Management menu
RE_GGREPO1 Test Report 1 1
RE_GGREPO2 Test Report 1 1
SU24 Auth. obj. Check under Transactions the permission object checks in a transaction
SU25 Upgrade Tool for profile Generator configuration file Builder upgrade Tools
SU26 Upgrade Tool for profile Generator configuration file Builder upgrade Tools
SUPC Profiles for Activity Groups Job Group parameter file
SUPN number range Maint.: Prof_varis Encoding Range Maintenance: Prof_varis
SUPO maintain Org. levels maintain initial levels
SM0 work Process overview Working process overview
SU02 Maintain Authorization Profiles maintenance permissions parameter file
SU03 Maintain authorizations maintenance rights
SU10 Mass changes to user master Records a large number of changes to your master record
SU12 Mass changes to user master Records extensive changes to user master records
SU2 maintain user parameter maintenance parameters
SU20 maintain Authorization fields maintain permissions field
SU21 maintain Authorization Objects maintaining permission objects
SU22 Auth. Object usage in Transactions transaction use of Permission objects
SU23 load Tables in tautl loaded in Tautl table
SU52 maintain user Parameters maintenance parameters
SU53 Display Check Values
SU54 Session Manager Conversation Manager
SU56 Analyze User Buffer analysis
SU80 Archive User Change documents archive users
SU81 Archive user Password change doc. To archive users password changes document
SU82 Archive Profile Documents document
SU83 Archive Authorization Docs. Archive Authorization Documents
SU84 Read archived User change documents reading archived users modified document
SU85 read archived password change doc. Read the archived password modify document
SU86 read profile Changing documents reading parameter file change document
SU87 read Authorization change documents reading authorization changes
SU96 table Maint.: Change Sukria maintenance: Modify Sukria
SU97 table Maint.: Display Sukria Watch maintenance: Show Sukria
SU98 Call Reports RSUSR008 Invoke report RSUSR008
SU99 Call Reports RSUSR008 Invoke report RSUSR008
Suim Call AUTH reporting tree (Info sys) calls AUTH report tree (Information System)
SU01 User Maintenance Maintenance
Su01_nav User Maint. To include in navigation user maintenance included in navigation
su01d User Display users
SU3 Maintain users OWN data maintains user-
SE01 Transport Organizer Transfer organizer
SE03 Workbench organizer:tools table Builder: Tools
SE06 set up Workbench organizer Setting Workbench Builder
SE07 Transport System Status Display transmission
SE09 Workbench Organizer Work Platform organizer
SE10 Customizing organizer Custom Organizer
SE17 General Table Display
STDR Tadir Consistency Check Tadir consistency checking
Suim User Rights Background configuration
STMS Transmission Management System

SAP System Performance Analysis Tcode