2. 2
E r r o r ! EU r o rn oU nnk n o w u m e n tu mre n te ptry p F otry i.n ta m nra EU r skrn oU nnk n o w u m e n tu mre n te ptry p e rmy .n a m e .
r nk ! w d o c n d o c p o p r o ne rm e n r rroe .! l runo e ! w
a Ee docn doc p op r o na t e
Error! Unknown document property name.
Error! Unkno wn docu ment property name.
Error! Unkno wn docu ment property name. 2 Error! Unknow n doc umen t proper ty name. 5
3. 2
E r r o r ! EU r o rn oU n k n o w u mdeonct u p re n te r tF o p e ntty .rn a rloe !sEU r o rn oU n k n o w u mdeonct u p re n te r tryo p e r t y
rnk ! wn doc n m o p p ry r a r e E r m u . er n k ! w n d o c n
n im na r m op p
name. name.
List of changes
VERSION DATE DESCRIPTION AUTHOR
11.08.04 Review Akshay
Kangle
Error! Unkno wn docu ment property name.
Error! Unkno wn docu ment property name. 3 Error! Unknow n doc umen t proper ty name.
5
4. 2
E r r o r ! EU r o rn oU n k n o w u mdeonct u p re n te r tF o p e ntty .rn a rloe !sEU r o rn oU n k n o w u mdeonct u p re n te r tryo p e r t y
rnk ! wn doc n m o p p ry r a r e E r m u . er n k ! w n d o c n
n im na r m op p
name. name.
2.3.10 BASIC PERFORMANCE MONITORING
Performance is one of the most complex aspects of a SAP system.
For the end user performance may be bad because of local PC problems, network
problems on the LAN the PC is connected to or other “local” problems.
The first thing that should be figured out is where a problem occurs.
Does the performance problem occur for one of more users? Try to imagine how the
different users/user types connect to the system and try to answer the question:
“is the performance problem on my SAP server or not?”
Generally spoken if ALL users (from Philips and Atos Origin) notice bad response
times it looks like the SAP server’s performance is bad.
On the SAP server performance is generally caused by application servers that
connect to database servers and finally to storage (discs).
pc
appl
db Server problem
discs
Local problem
pc appl
pc
The application servers connect to the database server.
The database server connects to the storage (discs) to store and retrieve information.
The servers run a HP-UX operating system. The server has 3 main resources that
influence performance:
• Cpu
• Memory
• I/o
Note that i/o is very general, but for SAP systems network i/o and disc i/o are most
important i/o categories.
The cpu load can be analyzed with unix commands/tools as
• Top
• Uptime
• Sam
• Sar
Error! Unkno wn docu ment property name.
Error! Unkno wn docu ment property name. 4 Error! Unknow n doc umen t proper ty name.
5
5. 2
E r r o r ! EU r o rn oU n k n o w u mdeonct u p re n te r tF o p e ntty .rn a rloe !sEU r o rn oU n k n o w u mdeonct u p re n te r tryo p e r t y
rnk ! wn doc n m o p p ry r a r e E r m u . er n k ! w n d o c n
n im na r m op p
name. name.
• Gpm (glance)
The cpu load can also be analyzed with transactions ST06 and OS06.
The memory load of a server can also be analyzed with SAP transactions ST06 and
OS06. The memory load can also be analyzed with unix tools as
• Vmstat
• Swapinfo
• Sar
• Gpm (glance)
The i/o load of servers can be checked with unix tools like
• Netstat
• Sar
• Gpm (glance)
Under SAP the general performance of a SAP system can be checked with
transaction SMLG. Run transaction SMLG and choose from the menu “Goto->Load
distribution (F5)”.
Transactions ST03 and ST03N can be used to analyze the SAP statistics of the
system.
Transaction ST02 can be used to check the SAP general performance.
Transaction ST04 can be used to check the Oracle general performance.
Error! Unkno wn docu ment property name.
Error! Unkno wn docu ment property name. 5 Error! Unknow n doc umen t proper ty name.
5
