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

100 lines
5.7 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="CPI432C - All access paths were considered for file &amp;1" />
<meta name="DC.Relation" scheme="URI" content="pimes.htm" />
<meta name="DC.Relation" scheme="URI" content="cpi432d.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="cpi432c" />
<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>CPI432C - All access paths were considered for file &amp;1</title>
</head>
<body id="cpi432c"><a name="cpi432c"><!-- --></a>
<!-- Java sync-link --><script language="Javascript" src="../rzahg/synch.js" type="text/javascript"></script>
<h1 class="topictitle1">CPI432C - All access paths were considered for file &amp;1</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="d0e19">CPI432C</th>
</tr>
</thead>
<tbody><tr valign="middle"><td valign="middle" width="26.02040816326531%" headers="d0e19 ">Message Text:</td>
<td valign="middle" width="73.9795918367347%" headers="d0e19 ">All access paths were considered for file &amp;1.</td>
</tr>
<tr valign="middle"><td valign="middle" width="26.02040816326531%" headers="d0e19 ">Cause Text:</td>
<td valign="middle" width="73.9795918367347%" headers="d0e19 ">The query optimizer considered all access paths built over member &amp;3
of file &amp;1 in library &amp;2. <p></p>
The list below shows the access
paths considered. If file &amp;1 in library &amp;2 is a logical file then
the access paths specified are actually built over member &amp;9 of physical
file &amp;7 in library &amp;8. <p></p>
Following each access path name
in the list is a reason code which explains why the access path was not used.
A reason code of 0 indicates that the access path was used to implement the
query. <p></p>
The reason codes and their meanings follow: <ol><li>Access path was not in a valid state. The system invalidated the access
path.</li>
<li>Access path was not in a valid state. The user requested that the access
path be rebuilt.</li>
<li>Access path is a temporary access path (resides in library QTEMP) and
was not specified as the file to be queried.</li>
<li>The cost to use this access path, as determined by the optimizer, was
higher than the cost associated with the chosen access method.</li>
<li>The keys of the access path did not match the fields specified for the
ordering/grouping criteria. For distributed file queries, the access path
keys must exactly match the ordering fields if the access path is to be used
when ALWCPYDTA(*YES or *NO) is specified.</li>
<li>The keys of the access path did not match the fields specified for the
join criteria.</li>
<li>Use of this access path would not minimize delays when reading records
from the file. The user requested to minimize delays when reading records
from the file.</li>
<li>The access path cannot be used for a secondary file of the join query
because it contains static select/omit selection criteria. The join-type of
the query does not allow the use of select/omit access paths for secondary
files.</li>
<li>File &amp;1 contains record ID selection. The join-type of the query forces
a temporary access path to be built to process the record ID selection.</li>
<li>and greater - View the second level message text of the next message issued
(CPI432D) for an explanation of these reason codes.</li>
</ol>
</td>
</tr>
<tr valign="middle"><td valign="middle" width="26.02040816326531%" headers="d0e19 ">Recovery Text:</td>
<td valign="middle" width="73.9795918367347%" headers="d0e19 ">The user may want to delete any access paths no longer needed.</td>
</tr>
</tbody>
</table>
</div>
<div class="section"><p>The optimizer considered all indexes built over the specified
table. Since the optimizer examined all indexes for the table, it determined
the current best access to the table.</p>
</div>
<div class="section"><p>The message help contains a list of the indexes. With each index
a reason code is added. The reason code explains why the index was or was
not used.</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 class="relref"><strong>Related reference</strong><br />
<div><a href="cpi432d.htm">CPI432D - Additional access path reason codes were used</a></div>
</div>
</div>
</body>
</html>