Few useful transaction codes for SAP Basis beginners.
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.
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.
ST04: A snapshot of databuffer/cache quality, SQL cache catalog/pin ratio.
For further detailed analysis click button 'Detail Analysis Menu'
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
circularily.
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'.
SM66: The main tool used for monitoring current system activity via the Global
Work Process Overview.
ST22: We can see here all runtime errors and detail information s
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: system log information, what ever happend in system level
we can see here.
Look for messages like :
- Printer problems
- Signal 11
- Short dumps
- Time-outs
- Matchcode problems
- Aborted postings
SM04: Active Users and number of modes of same. Also check memory, page, roll,
priv usage via goto->memory
AL08: The number of active users can be otained from the Global User Monitor
SARFC: An overview 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
Monitor
DB02: Check database growth, freespace in tablespaces, critical objects, extents
of tables and indexes
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.
DB24:Check administration tasks such as backup/recovery, archive frequency,
administration tasks.
STAD:Used to check response time of programs/transactions and provides various
levels of detail which can be tailored.
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
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.
The ST12 can also be used for tracing workprocess, program/transaction or a
user. A the click of a button you can view the SQL and ABAP trace
information.
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.
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.
ST04: A snapshot of databuffer/cache quality, SQL cache catalog/pin ratio.
For further detailed analysis click button 'Detail Analysis Menu'
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
circularily.
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'.
SM66: The main tool used for monitoring current system activity via the Global
Work Process Overview.
ST22: We can see here all runtime errors and detail information s
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: system log information, what ever happend in system level
we can see here.
Look for messages like :
- Printer problems
- Signal 11
- Short dumps
- Time-outs
- Matchcode problems
- Aborted postings
SM04: Active Users and number of modes of same. Also check memory, page, roll,
priv usage via goto->memory
AL08: The number of active users can be otained from the Global User Monitor
SARFC: An overview 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
Monitor
DB02: Check database growth, freespace in tablespaces, critical objects, extents
of tables and indexes
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.
DB24:Check administration tasks such as backup/recovery, archive frequency,
administration tasks.
STAD:Used to check response time of programs/transactions and provides various
levels of detail which can be tailored.
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
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.
The ST12 can also be used for tracing workprocess, program/transaction or a
user. A the click of a button you can view the SQL and ABAP trace
information.
No comments:
Post a Comment