ibm-information-center/dist/eclipse/plugins/i5OS.ic.rzahy_5.4.0.1/rzahytsh-po.htm

87 lines
5.7 KiB
HTML

<?xml version="1.0" encoding="utf-8"?>
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN"
"http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
<html xmlns="http://www.w3.org/1999/xhtml" lang="en-US" xml:lang="en-us">
<head>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8" />
<meta name="dc.language" scheme="rfc1766" content="en-us" />
<!-- All rights reserved. Licensed Materials Property of IBM -->
<!-- US Government Users Restricted Rights -->
<!-- Use, duplication or disclosure restricted by -->
<!-- GSA ADP Schedule Contract with IBM Corp. -->
<meta name="dc.date" scheme="iso8601" content="2005-09-06" />
<meta name="copyright" content="(C) Copyright IBM Corporation 1998, 2006" />
<meta name="security" content="public" />
<meta name="Robots" content="index,follow"/>
<meta http-equiv="PICS-Label" content='(PICS-1.1 "http://www.icra.org/ratingsv02.html" l gen true r (cz 1 lz 1 nz 1 oz 1 vz 1) "http://www.rsac.org/ratingsv01.html" l gen true r (n 0 s 0 v 0 l 0) "http://www.classify.org/safesurf/" l gen true r (SS~~000 1))' />
<title>Directory Server (LDAP) - Troubleshoot Directory Server</title>
<link rel="stylesheet" type="text/css" href="ibmidwb.css" />
<link rel="stylesheet" type="text/css" href="ic.css" />
</head>
<body>
<a id="Top_Of_Page" name="Top_Of_Page"></a><!-- Java sync-link -->
<script language = "Javascript" src = "../rzahg/synch.js" type="text/javascript"></script>
<a name="rzahytsh-po"></a>
<h1 id="rzahytsh-po">Troubleshoot Directory Server</h1>
<p>Unfortunately, even reliable servers such as the Directory Server sometimes have
problems. When your Directory Server has problems, the following information
can help you figure out what is wrong and how to fix the trouble.</p>
<p>You can find return codes for LDAP errors in the ldap.h file, which is
located on your system in QSYSINC/H.LDAP.</p><blockquote>
<p><span class="bold"><a href="rzahyvjl-pi.htm#rzahyvjl-pi">Monitor errors and access with the Directory Server job log</a></span>
<br />When
you get an error on your Directory Server and want more details, another action
to take is to view the QDIRSRV job log.</p>
<p><span class="bold"><a href="rzahytrctcpapp.htm#rzahytrctcpapp">Use TRCTCPAPP to help find problems</a></span>
<br /> For
reproducible errors, you can use Trace TCP/IP Application (TRCTCPAPP APP(*DIRSRV))
command to run a trace of the errors.</p>
<p><span class="bold"><a href="rzahydebugoption.htm#rzahydebugoption">Use the LDAP_OPT_DEBUG option to trace errors</a></span>
<br /> Trace
problems with clients that are using the LDAP C APIs.</p>
<p><span class="bold"><a href="rzahytcl-rf.htm#rzahytcl-rf">Common LDAP client errors</a></span>
<br /> Knowing the causes of common
LDAP client errors can help you to solve problems with your server.</p>
<p><img src="delta.gif" alt="Start of change" /><span class="bold"><a href="rzahypwderrors.htm#rzahypwderrors">Password policy-related errors</a></span>
<br />Enabling
a password policy can sometimes cause unexpected errors.<img src="deltaend.gif" alt="End of change" /></p>
<p><img src="delta.gif" alt="Start of change" /><span class="bold"><a href="rzahyqgldcpyvl_api.htm#rzahyqgldcpyvl_api">Troubleshooting the QGLDCPYVL API</a></span>
<br />Using
the User Trace facility may explain the error or determine if service is needed.<img src="deltaend.gif" alt="End of change" /></p></blockquote>
<p>For additional information about common Directory Server problems, see the <a href=" http://www.ibm.com/servers/eserver/iseries/ldap" target="_blank">Directory Server home page</a>
<img src="www.gif" alt="Link outside the Information Center" /> (www.iseries.ibm.com/ldap).</p>
<p>Directory Server uses several Structured Query Language (SQL) servers which are
iSeries QSQSRVR jobs. When an SQL error occurs, the QDIRSRV job log will usually
contain the following message:</p>
<pre class="xmp">SQL error -1 occurred</pre><p class="indatacontent">In these instances
the QDIRSRV job log will refer you to the SQL server job logs. However, in
some cases QDIRSRV might not contain this message and this referral, even
if an SQL server is the cause of the problem. In these instances, it will
help you to know what SQL server jobs the server started, so that you know
in which QSQSRVR job logs to look for additional errors.</p>
<p>When the Directory Server starts normally, it generates messages similar
to the following:</p>
<pre class="xmp"> System: MYISERIES
Job . . : QDIRSRV User . . : QDIRSRV Number . . . : 174440
>> CALL PGM(QSYS/QGLDSVR)
Job 057448/QUSER/QSQSRVR used for SQL server mode processing.
Job 057340/QUSER/QSQSRVR used for SQL server mode processing.
Job 057448/QUSER/QSQSRVR used for SQL server mode processing.
Job 057166/QUSER/QSQSRVR used for SQL server mode processing.
Job 057279/QUSER/QSQSRVR used for SQL server mode processing.
Job 057288/QUSER/QSQSRVR used for SQL server mode processing.
Directory Server started successfully.</pre><p class="indatacontent">The messages refer to the
QSQSRVR jobs that were started for the server. The number of messages might
differ on your server depending on the configuration and the number of QSQSRVR
jobs needed to accomplish server startup.</p>
<p>On the directory servers <span class="bold">Database/Suffixes</span> Properties
page in iSeries Navigator you specify the total number of SQL servers that Directory Server uses
for directory operations after server startup. Additional SQL servers are
started for replication.</p>
<a id="Bot_Of_Page" name="Bot_Of_Page"></a>
</body>
</html>