ibm-information-center/dist/eclipse/plugins/i5OS.ic.rzajq_5.4.0.1/cpi4326.htm

91 lines
5.2 KiB
HTML
Raw Normal View History

2024-04-02 14:02:31 +00:00
<?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="reference" />
<meta name="DC.Title" content="CPI4326 - &amp;12 &amp;13 processed in join position &amp;10" />
<meta name="DC.Relation" scheme="URI" content="pimes.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="cpi4326" />
<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>CPI4326 - &amp;12 &amp;13 processed in join position &amp;10</title>
</head>
<body id="cpi4326"><a name="cpi4326"><!-- --></a>
<!-- Java sync-link --><script language="Javascript" src="../rzahg/synch.js" type="text/javascript"></script>
<h1 class="topictitle1">CPI4326 - &amp;12 &amp;13 processed in join position &amp;10</h1>
<div>
<div class="tablenoborder"><table cellpadding="4" cellspacing="0" summary="" frame="border" border="1" rules="all"><thead align="left"><tr><th colspan="2" align="center" valign="middle" id="d0e16">CPI4326</th>
</tr>
</thead>
<tbody><tr valign="middle"><td valign="middle" width="26.02040816326531%" headers="d0e16 ">Message Text:</td>
<td valign="middle" width="73.9795918367347%" headers="d0e16 ">&amp;12 &amp;13 processed in join position &amp;10.</td>
</tr>
<tr valign="middle"><td valign="middle" width="26.02040816326531%" headers="d0e16 ">Cause Text:</td>
<td valign="middle" width="73.9795918367347%" headers="d0e16 ">Access path for member &amp;5 of file &amp;3 in library &amp;4 was
used to access records in member &amp;2 of file &amp;13 in library &amp;1
for reason code &amp;9. The reason codes and their meanings follow: <ol><li>Perform specified record selection.</li>
<li>Perform specified ordering/grouping criteria.</li>
<li>Record selection and ordering/grouping criteria.</li>
<li>Perform specified join criteria.</li>
</ol>
If file &amp;13 in library &amp;1 is a logical file then member &amp;8
of physical file &amp;6 in library &amp;7 is the actual file in join position &amp;10.
<p></p>
A file name starting with *TEMPX for the access path indicates
it is a temporary access path built over file &amp;6. <p></p>
A file name
starting with *N or *QUERY for the file indicates it is a temporary file.
<p></p>
Index only access was used for this file within the query: &amp;11.
<p></p>
A value of *YES for index only access processing indicates
that all of the fields used from this file for this query can be found within
the access path of file &amp;3. A value of *NO indicates that index only access
could not be performed for this access path.<p></p>
Index only
access is generally a performance advantage since all of the data can be extracted
from the access path and the data space does not have to be paged into active
memory.</td>
</tr>
<tr valign="middle"><td valign="middle" width="26.02040816326531%" headers="d0e16 ">Recovery Text:</td>
<td valign="middle" width="73.9795918367347%" headers="d0e16 ">Generally, to force a file to be processed in join position 1, specify
an order by field from that file only. <p></p>
If ordering is desired,
specifying ORDER BY fields over more than one file forces the creation of
a temporary file and allows the optimizer to optimize the join order of all
the files. No file is forced to be first. <p></p>
An access path can
only be considered for index only access if all of the fields used within
the query for this file are also key fields for that access path. <p></p>
Refer
to <a href="rzajqdta.htm#rzajqdta">Data access on DB2 UDB for iSeries: data access paths and methods</a> for additional tips on optimizing
a query's join order and index only access.</td>
</tr>
</tbody>
</table>
</div>
<div class="section"><p>This message provides the join position of the specified table
when an index is used to access the table's data. <strong>Join position</strong> pertains
to the order in which the tables are joined. </p>
</div>
</div>
<div>
<div class="familylinks">
<div class="parentlink"><strong>Parent topic:</strong> <a href="pimes.htm" title="You can evaluate the structure and performance of the given SQL statements in a program using informational messages put in the job log by the database manager.">Query optimization performance information messages</a></div>
</div>
</div>
</body>
</html>