We can help. Together we learn....

Logs and Traces - transactions

by vinaysingh | Wednesday, August 19, 2009 in |

The major transactions for Trace Options in SAP are :-


1) System Log (SM21).
2)Dump Analysis(ST22).
3)System Trace(ST01).
4)Performance Trace(ST05).
5)Developer Trace(ST11).


SYSTEM LOG(SM21):-

a) Can be used to detect and correct errors in our SAP system and its Environment.
b)SAP application servers record events and problem in system logs.
c)Every SAP application Server has a local log that contains the messages output by this server.

Local System Log :- /usr/sap//D*/log/SLOG

Central System Log:- /usr/sap//SYS/global/SLOGJ

central system log feature - Available in Unix ,not possible in Windows and Iseries.

profile parameter (RZ10) :-

rslg/local/file :- local log file
rslg/central/file:-Central file

Invoked by tools-->Administration-->Monitor -->System Log or Call transaction SM21.


2)Dump Analysis(ST22)

a)If unpredictable errors occurs during runtime when you call an ABAP program , a runtime error that generates a short dump can occurs.
b)By default ,short dump are stored in the system for 14 days.
c)You can delete short dumps in accordance with a time specification using the reorganize function ,which you call by choosing Goto -->Reogranize .

d) one can save a short dump without a time limit using the KEEP function ,which one can choose from detail view under short Dump -->KEEP/RELEASE.

Characteristics of Dump Analysis:-

1) If a runtime error occurs ,a short dump is generated.You can use tranaction ST22 to analyzer this short dump.
2)Dump data is stored in the database.
3)Dump data can be reorganized.
4)Individual short dump can be flagged for retantion.

System Trace (ST01)

to record the internal SAP activities ,such as authorization checks,database access ,kernel functions and RFC calls.

The system trace is used for analyzing:
a)Authorization checks
b)Kernel functions
c)Kernel modules
d)DB accesses (SQL Trace)
e)Accesses to table buffers
f)Lock operations (client-side).

PERFORMANCE TRACE(ST05)

The Performance trace is used for analyzing:

a)Database calls
b)Lockmanagement calls
c)Accesses to table buffers
d)Remote calls of reports and transactions
e)Individual trace records
f)SQL statements.

DEVELOPER TRACE(ST11)

Developer traces are recordings that contain technical information and that
are used if errors occur.

a)Can be read by using Transaction AL11.
b)Browse to directory usr/sap//d*/work.
c)Developer trace can be viwed at dev_* files.
d)Can be accessed in Transaction: SM50.
Process → Trace → Display File.






2 comments:

  1. Dinesh Kumar on April 27, 2016 at 2:09 PM

    Thanks for sharing this Informative content. Well explained. Got to learn new things from your Blog on SAP SD

     
  2. Bhavya Kumar on September 23, 2016 at 1:28 PM

    Great place to learn about the new things and got great knowledgeSAP MM Training in Chennai

     

Categories