Dealing with Stress

Your own stress can be the biggest detriment to getting a problem resolved. Stress creates an environment that is not conducive to clear thinking, and being able to think clearly about what you are seeing and reason through the problem is absolutely critical to resolving a problem.

The following are some techniques you can use to clear your head and perform a type of mental "soft reset":

• Take a walk while DSRepair (or some other automated process) is doing its job.

• Close your eyes and count to 10 when you are in front of the server that is exhibiting the problem.

• Laugh. This one sometimes brings on strange looks from co-workers , but it really works. Laughter is one of the best stress relievers there is. (Sometimes, having a few copies of Dilbert books around comes in handy.)

• Stretch. Stretching helps work out the tension you can get in your neck and shoulders. It often helps you relax, and you can think more clearly and effectively when relaxed .

Other people use other techniques. The important thing is to find out what works for you. When in a crisis situation, it is important that the stress relief method you use is something that can be applied quickly and works quickly. Going on a five-mile jog might be a great stress reliever for you, but when in a crisis situation, this is not likely to be a viable option.

Summary

When you are calm and in control of the situation, you can begin to address the problem, starting with understanding eDirectory processes and error codes. These are discussed in the chapters that follow.

Part II: Understanding the Error Codes and eDirectory Processes

Chapter 5. eDirectory/NDS Error Codes Explained

DS errors occur during the processing of a directory services (DS) request or the execution of a DS background process. These errors can happen as a result of a hardware or software failure, data inconsistency, or unexpected responses received; therefore, when you're troubleshooting a problem, it is essential that you know where the error originated, the condition that caused the error, and what the error code or message means. Unfortunately, computer-generated error messages are notoriously cryptic at best and frequently don't easily provide the source of the error. For example, a DS error can be generated from one of three possible sources:

• The DS service running on the server

• The client application (workstation based or server based)

• The DS agent (DSA) running on the server.

It gets even more frustrating if multiple causes can result in the same error code.

NOTE

Each DS -capable server runs both DS service (which processes DS requests locally) and the DSA service. The DSA tree-walks and queries other DS servers on behalf of the requesting client ”which can be either a workstation or another server ”if the local server doesn't have the requested information.

http://nimbus.ocis.temple.edu/ldap/error.htm#1915315

http://help.netscape.com/kb/corporate/19970303-9.html

www.opus1.com/www/iii/SDK/errors.html