Entering content frame

Component documentation Techniques for Problem Analysis Locate the document in its SAP Library structure

Purpose

If a problem occurs and an alarm occurs, a problem analysis has to be carried out. Then the administrator or support has to look deeper into the programs and processes, so he or she looks at the traces.

This graphic is explained in the accompanying text

Traces have to be switched on only when they are required since each action of a certain process covered by the trace will be written to a file. This of course makes the system performance slow down. The traces have to be switched off again immediately once the problem analysis is finished and the problem is solved.

The types of traces the administrator has to use to test for errors depends on the problem:

·        Performance Trace

·        Application Trace

·        Session Trace

·        Single Activity Trace

·        Java Application Response Time Measurement

·        Open SQL Monitoring

 

Leaving content frame