&KDSWHU  7URXEOHVKRRWLQJ

&RQWHQWV
Overview ................................................................................................................182 Basic Troubleshooting Techniques ....................................................................182

System Administration Made Easy

181

Chapter 18: Troubleshooting Overview

2YHUYLHZ
This chapter is a basic problem solving chapter. We will present you with some of the tools and techniques to help you solve the problem yourself. We will not be going into advanced troubleshooting techniques. Troubleshooting is learned by doing; the more experience you have, the better you become. The next chapter is on performance tuning. Performance tuning is a specialized troubleshooting, so troubleshooting techniques are also relevant for performance tuning.

%DVLF 7URXEOHVKRRWLQJ 7HFKQLTXHV

The general procedure when working on troubleshooting is not new. It is the standard problem solving procedure that has been in use for years by many professions. Your auto mechanic would follow the same procedure when repairing your car: < < < < < < Gather data Analyze the problem Evaluate the alternatives Make a change Remember to make only one change at a time. Document the changes Evaluate the results

*DWKHU 'DWD < Ask the following questions: What is the problem? What error messages, dumps, or other diagnostic aids are available from the problem? What conditions caused the problem? Is the problem repeatable? To analyze the problem, use your available tools, such as: System Log (SM21) Update Failure (SM13) ABAP Dump (SM22) Spool (SP01)

<

182

Release 4.6A/B

Chapter 18: Troubleshooting Basic Troubleshooting Techniques

$QDO\]H WKH 3UREOHP < What are the resources you have to help solve the problem: Online documentation Reference books SAP notes Other customers (this is your network) Call for assistance: Consultants SAPNet help desk

<

(YDOXDWH WKH $OWHUQDWLYHV 0DNH RQO\ 2QH &KDQJH DW D 7LPH < < If there is a problem, and you made several changes at once, you will not know which change caused or fixed a problem. There are times where several changes need to be made, to fix a problem. Unless they must be done together, such as related program changes, make the changes separately. 'RFXPHQW WKH &KDQJHV < If a change causes a problem, you need to undo the change. To do that you need to know what the configuration was before the change and what you did. < If the change needs to be applied to multiple systems, you need to know exactly what changes to make and how to do it. This process must be repeated exactly the same on all systems.

System Administration Made Easy

183

Chapter 18: Troubleshooting Basic Troubleshooting Techniques

*HW WKH &RPSOHWH (UURU 0HVVDJH

*XLGHG 7RXU

When you get an error message in an R/3 transaction, you need all the information on the error to forward to SAP. To get the complete error message, do the following: 1. When an error occurs, the field with the error is highlighted. 2. Double-click on the error message.

3. The error message appears in the dialog box. 4. Record the relevant information from the screen to send to SAP.
3

184

Release 4.6A/B

Chapter 18: Troubleshooting Basic Troubleshooting Techniques

*HW WKH 6$3 3DWFK /HYHO

:KDW

This level is the R/3 kernel patch level that is being used.
:K\

This patch level is needed when submitting problem messages to SAP. It tells the hot line personnel on what kernel patch level you are. Different problems are fixed in different patch levels. ([DPSOH You are on patch level 50 and have a particular problem. The fix to your problem may have been done in patch level 61. This level identifies that the problem is an older kernel that contains the problem. The solution is to upgrade to the current kernel, at least patch level 61.
+RZ

*XLGHG 7RXU

1. In the Command field, enter transaction SM51 and choose Enter (or from the SAP standard menu, choose Tools Administration Monitor System monitoring SM51-Servers). 2. Select the central instance (for example, pa100767_SAS_00). 3. Choose Release notes.
3 2

System Administration Made Easy

185

Chapter 18: Troubleshooting Basic Troubleshooting Techniques

4. Record the Patch level (for our example, we chose Patch level 55).

'HWHUPLQLQJ :KDW 6XSSRUW 3DFNDJHV +DYH %HHQ $SSOLHG

:KDW

A support package is an SAP-provided R/3 fix and is similar to an NT Service Pack.

:K\

As with the SAP Patch level, problems you have may be related to the level of the applied support package.

186

Release 4.6A/B

Chapter 18: Troubleshooting Basic Troubleshooting Techniques

+RZ

*XLGHG 7RXU

1. From the menu bar, choose System Status. 2. Choose .

3. Choose the Patches tab.

3

System Administration Made Easy

187

Chapter 18: Troubleshooting Basic Troubleshooting Techniques

4. In this example, the following patches have been applied: < SPAM update 17-Sept-99 < Support Package 01 for 4.6A Patch Status values are: < N The patch has not yet been applied < < I Patch has been successfully applied ? Patch application has been aborted

The name of a Support Package is interpreted as follows: < SAPKH<release><sequence_number> < SAPKH46A01 is interpreted as SAPKH / 46A / 01, and is for Release 4.6A and is the first Support Package.

188

Release 4.6A/B