27.04.2013 Views

SAP Basis

You also want an ePaper? Increase the reach of your titles

YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.

Unit 15: Structured Troubleshooting ADM100<br />

If unpredictable errors occur during runtime when you call an ABAP<br />

program, a runtime error that generates a short dump can occur<br />

(transaction ST22).<br />

If you want to record the internal <strong>SAP</strong> system activities, such as<br />

authorization checks, database accesses, kernel functions, and RFC calls,<br />

use the System Trace function (transaction: ST01).<br />

The Performance Trace(transaction ST05) allows you to record database<br />

calls, lock management calls, and remote calls of reports and transactions<br />

in a trace file and to display the logged measurement results as lists. The<br />

Performance Trace also offers extensive support for a detailed analysis<br />

of individual trace records.<br />

Technical information about internal <strong>SAP</strong> problems is logged in developer<br />

traces.<br />

System Log<br />

Events and problems are recorded locally on each application server and<br />

displayed in the system log in the <strong>SAP</strong> system.<br />

Figure 169: System Log (SM21)<br />

If you are using the UNIX operating system, you can also work with<br />

central logging. In this case, each application server copies its local logs to<br />

a central log. Central logging is not possible on Microsoft Windows NT<br />

536 © 2003 <strong>SAP</strong> AG. All rights reserved. 2003/Q3

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!