101 lines
7.7 KiB
HTML
101 lines
7.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 lang="en-us" xml:lang="en-us">
|
||
|
|
<head>
|
||
|
|
<meta http-equiv="Content-Type" content="text/html; charset=utf-8" />
|
||
|
|
<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))' />
|
||
|
|
<meta name="DC.Type" content="concept" />
|
||
|
|
<meta name="DC.Title" content="Troubleshooting" />
|
||
|
|
<meta name="abstract" content="When a problem occurs accessing a distributed relational database, it is the job of the administrator to determine the nature of the problem and whether it is a problem with the application or a problem with the local or remote system." />
|
||
|
|
<meta name="description" content="When a problem occurs accessing a distributed relational database, it is the job of the administrator to determine the nature of the problem and whether it is a problem with the application or a problem with the local or remote system." />
|
||
|
|
<meta name="DC.subject" content="handling DRDB problems, problems, handling" />
|
||
|
|
<meta name="keywords" content="handling DRDB problems, problems, handling" />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="rbal1kickoff.htm" />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="rbal1probover.htm" />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="rbal1prbiso.htm" />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="rbal1wwu.htm" />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="rbal1appprob.htm" />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="rbal1scprob.htm" />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="rbal1gdrf.htm" />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="rbal1firstfail.htm" />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="rbal1stsrvjb.htm" />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="rbal1perform.htm" />
|
||
|
|
<meta name="copyright" content="(C) Copyright IBM Corporation 1998, 2006" />
|
||
|
|
<meta name="DC.Rights.Owner" content="(C) Copyright IBM Corporation 1998, 2006" />
|
||
|
|
<meta name="DC.Format" content="XHTML" />
|
||
|
|
<meta name="DC.Identifier" content="rbal1problem" />
|
||
|
|
<meta name="DC.Language" 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. -->
|
||
|
|
<link rel="stylesheet" type="text/css" href="./ibmdita.css" />
|
||
|
|
<link rel="stylesheet" type="text/css" href="./ic.css" />
|
||
|
|
<title>Troubleshooting</title>
|
||
|
|
</head>
|
||
|
|
<body id="rbal1problem"><a name="rbal1problem"><!-- --></a>
|
||
|
|
<!-- Java sync-link --><script language="Javascript" src="../rzahg/synch.js" type="text/javascript"></script>
|
||
|
|
<h1 class="topictitle1">Troubleshooting</h1>
|
||
|
|
<div><p>When a problem occurs accessing a distributed relational database,
|
||
|
|
it is the job of the administrator to determine the nature of the problem
|
||
|
|
and whether it is a problem with the application or a problem with the local
|
||
|
|
or remote system.</p>
|
||
|
|
<p>You must then resolve the problem or obtain customer support assistance
|
||
|
|
to resolve the problem. To do this, you need:</p>
|
||
|
|
<ul><li>An understanding of the <span class="keyword">i5/OS™</span> licensed
|
||
|
|
program support.</li>
|
||
|
|
<li>A good idea of how to decide if a problem is on an application requester
|
||
|
|
(AR) or an application server (AS).</li>
|
||
|
|
<li>Familiarity with using <span class="keyword">i5/OS</span> problem
|
||
|
|
management functions.</li>
|
||
|
|
</ul>
|
||
|
|
<p>For more information about diagnosing problems in a distributed relational
|
||
|
|
database, see the <em>Distributed Relational Database Problem Determination
|
||
|
|
Guide</em>, SC26-4782.</p>
|
||
|
|
</div>
|
||
|
|
<div>
|
||
|
|
<ul class="ullinks">
|
||
|
|
<li class="ulchildlink"><strong><a href="rbal1probover.htm">iSeries problem handling overview</a></strong><br />
|
||
|
|
The <span class="keyword">i5/OS</span> licensed
|
||
|
|
program helps you manage problems for both user- and system-detected problems
|
||
|
|
that occur on local and remote <span class="keyword">iSeries™ server</span>s. </li>
|
||
|
|
<li class="ulchildlink"><strong><a href="rbal1prbiso.htm">Isolate distributed relational database problems</a></strong><br />
|
||
|
|
A problem you encounter when running a distributed relational database application can exhibit two general symptoms: incorrect output or the application does not complete in the expected time.</li>
|
||
|
|
<li class="ulchildlink"><strong><a href="rbal1wwu.htm">Work with distributed relational database users</a></strong><br />
|
||
|
|
Investigating a problem usually begins with the user. Users might not be getting the results they expect when running a program or they might get a message indicating a problem. Sometimes the best way to diagnose and solve a problem is to go through the procedure with a user.</li>
|
||
|
|
<li class="ulchildlink"><strong><a href="rbal1appprob.htm">Application problems</a></strong><br />
|
||
|
|
The best time to handle a problem with an application is before it goes into production. However, it is impossible to anticipate all the conditions that will exist for an application when it gets into general use.</li>
|
||
|
|
<li class="ulchildlink"><strong><a href="rbal1scprob.htm">System and communications problems</a></strong><br />
|
||
|
|
When a problem with a system or its communications occurs, a message is generated. System-detected problems are automatically entered into the problem log, where they can be viewed and analyzed.</li>
|
||
|
|
<li class="ulchildlink"><strong><a href="rbal1gdrf.htm">Get data to report a failure</a></strong><br />
|
||
|
|
This topic collection describes the kinds of data that you can
|
||
|
|
print to help you diagnose a problem in a distributed relational database
|
||
|
|
on <span class="keyword">iSeries™ server</span>s.</li>
|
||
|
|
<li class="ulchildlink"><strong><a href="rbal1firstfail.htm">Find first-failure data capture data</a></strong><br />
|
||
|
|
This topic describes tips on how to locate first-failure data capture
|
||
|
|
(FFDC) data on an <span class="keyword">iSeries™ server</span>.
|
||
|
|
The information is most useful if the failure causing the FFDC data output
|
||
|
|
occurred on the application server (AS). The FFDC data for an application
|
||
|
|
requester (AR) can usually be found in one of the spooled files associated
|
||
|
|
with the job running the application program.</li>
|
||
|
|
<li class="ulchildlink"><strong><a href="rbal1stsrvjb.htm">Start a service job to diagnose application server problems</a></strong><br />
|
||
|
|
When an application uses Distributed
|
||
|
|
Relational Database Architecture™ (DRDA<sup>®</sup>), the SQL statements are run in the
|
||
|
|
application server job. Because of this, you might need to start debug or
|
||
|
|
a job trace for the application server job that is running on the <span class="keyword">i5/OS</span> operating system. The technique
|
||
|
|
for doing this differs based on the use of either Advanced Program-to-Program
|
||
|
|
Communication (APPC) or TCP/IP.</li>
|
||
|
|
</ul>
|
||
|
|
|
||
|
|
<div class="familylinks">
|
||
|
|
<div class="parentlink"><strong>Parent topic:</strong> <a href="rbal1kickoff.htm" title="Distributed database programming describes the distributed relational database management portion of the i5/OS licensed program. Distributed relational database management provides applications with access to data that is external to the applications and typically located across a network of computers.">Distributed database programming</a></div>
|
||
|
|
</div>
|
||
|
|
<div class="relconcepts"><strong>Related concepts</strong><br />
|
||
|
|
<div><a href="rbal1perform.htm" title="No matter what kind of application programs you are running on a server, performance can always be a concern. For a distributed relational database, network, server, and application performance are all crucial.">Performance</a></div>
|
||
|
|
</div>
|
||
|
|
</div>
|
||
|
|
</body>
|
||
|
|
</html>
|