ibm-information-center/dist/eclipse/plugins/i5OS.ic.dbp_5.4.0.1/rbaforzahfpro.htm

73 lines
4.9 KiB
HTML
Raw Blame History

This file contains invisible Unicode characters

This file contains invisible Unicode characters that are indistinguishable to humans but may be processed differently by a computer. If you think that this is intentional, you can safely ignore this warning. Use the Escape button to reveal them.

<?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="Rebuild access paths" />
<meta name="abstract" content="Rebuilding a database access path might take as much as one minute for every 10 000 records. But some factors might affect the time estimate for rebuilding access paths." />
<meta name="description" content="Rebuilding a database access path might take as much as one minute for every 10 000 records. But some factors might affect the time estimate for rebuilding access paths." />
<meta name="DC.Relation" scheme="URI" content="rbaforzahfpri.htm" />
<meta name="DC.Relation" scheme="URI" content="rbaforzahfprp.htm" />
<meta name="DC.Relation" scheme="URI" content="rbaforzahfprq.htm" />
<meta name="DC.Relation" scheme="URI" content="rbaforzahfprr.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="rbaforzahfpro" />
<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>Rebuild access paths</title>
</head>
<body id="rbaforzahfpro"><a name="rbaforzahfpro"><!-- --></a>
<!-- Java sync-link --><script language="Javascript" src="../rzahg/synch.js" type="text/javascript"></script>
<h1 class="topictitle1">Rebuild access paths</h1>
<div><p>Rebuilding a database access path might take as much as one minute
for every 10 000 records. But some factors might affect the time estimate
for rebuilding access paths.</p>
<p>The following factors affect the time estimate for rebuilding
access paths:</p>
<ul><li>Storage pool size. You can improve the rebuild time by running the job
in a larger storage pool.</li>
<li>The system model. The speed of the processing unit is a key factor.</li>
<li>Key length. A large key length slows rebuilding the access path because
the access path constructs and stores more key information. </li>
<li>Select/omit values. Select/omit processing slows the rebuilding of an
access path because the system compares each record to see if it meets the
select/omit values.</li>
<li>Record length. A large record length slows the rebuilding of an access
path because the system looks at more data. </li>
<li>Storage device that contains the data. The relative speed of the storage
device that contains the actual data and the device that stores the access
path affects the time needed to rebuild an access path.</li>
<li>The order of the records in the file. The system tries to rebuild an access
path so that it can find information quickly when using that access path.
The order of the records in a file has a small affect on how fast the system
builds the access path while trying to maintain an efficient access path.</li>
</ul>
</div>
<div>
<ul class="ullinks">
<li class="ulchildlink"><strong><a href="rbaforzahfprp.htm">Control when access paths are rebuilt</a></strong><br />
If the system ends abnormally, during the next initial program load (IPL), the system automatically lists those files that require access path recovery. You can control when access paths are rebuilt.</li>
<li class="ulchildlink"><strong><a href="rbaforzahfprq.htm">Design files to reduce access path rebuilding time</a></strong><br />
File design can help reduce access path recovery time.</li>
<li class="ulchildlink"><strong><a href="rbaforzahfprr.htm">Other methods to avoid rebuilding access paths</a></strong><br />
If you do not journal your access paths or do not take advantage of system-managed access-path protection (SMAPP), consider other system functions that reduce the chances of rebuilding access paths.</li>
</ul>
<div class="familylinks">
<div class="parentlink"><strong>Parent topic:</strong> <a href="rbaforzahfpri.htm" title="The system ensures the integrity of an access path before you can use it. If the system determines that the access path is unusable, the system attempts to recover it. You can control when to have the access path recovered.">Reduce time in access path recovery</a></div>
</div>
</div>
</body>
</html>