27.04.2013 Views

SAP Basis

Create successful ePaper yourself

Turn your PDF publications into a flip-book with our unique Google optimized e-Paper software.

Unit 15: Structured Troubleshooting ADM100<br />

• Call transaction ST22. Choose Goto → Reorganize. You can now<br />

specify that all short dumps older than n days old (default 7) are to be<br />

deleted. If a very large number of records are deleted at once during<br />

the reorganization, ORACLE error ora1562, failed to extend rollback<br />

segment ..., can occur. In this case, see <strong>SAP</strong> Note 6328.<br />

• Dropping and recreating table SNAP with the database utility<br />

(transaction SE14): you can use this transaction to drop and recreate<br />

the table SNAP. This means that all short dumps are deleted.<br />

• The reorganization program RSSNAPDL deletes old short dumps in<br />

pieces (to avoid database problems) from table SNAP. It deletes short<br />

dumps that are not flagged for retention and are older than seven<br />

days old. Schedule this program at a time of low workload, as large<br />

changes in the database are to be expected. The program RSNAPJOB<br />

performs a standard scheduling: it starts the program RSSNAPDL<br />

every day at 1:00 a.m..<br />

• Table SNAP is also automatically reorganized.Ateveryshortdump<br />

that occurs in dialog (the dump is displayed immediately after it is<br />

created), a maximum of 20 short dumps that are older than 7 days<br />

old are deleted from SNAP. This reorganization should be sufficient<br />

in normal production operation.<br />

At this point, you can demonstrate transaction ST22. Execute a function<br />

module that can be used for remote connections in the Function Builder<br />

(transaction SE37), such as RFC_READ_TABLE for table T000, or<br />

RFC_SYSTEM_INFO as described in the exercise. Use the RFC connection<br />

TRACES_ST22. A short dump is generated. You can analyze this in<br />

transaction ST22. Show the short dump and the options for reorganization<br />

and retention of messages.<br />

<strong>SAP</strong> System Trace<br />

You can use the system trace to record internal system activities. The<br />

system trace is primarily used if an authorization trace is to be created. We<br />

recommend that you use the system log or the developer trace for system<br />

monitoring and problem analysis. You can call the <strong>SAP</strong> System Trace using<br />

transaction ST01 or by choosing the menu path Tools → Administration →<br />

Monitor → Traces → System Trace. YoucanalsousetransactionST01to<br />

display the inactive trace file.<br />

You can use the <strong>SAP</strong> system trace to monitor the following components:<br />

540 © 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!