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

67 lines
4.5 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="Other methods to avoid rebuilding access paths" />
<meta name="abstract" content="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." />
<meta name="description" content="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." />
<meta name="DC.Relation" scheme="URI" content="rbaforzahfpro.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="rbaforzahfprr" />
<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>Other methods to avoid rebuilding access paths</title>
</head>
<body id="rbaforzahfprr"><a name="rbaforzahfprr"><!-- --></a>
<!-- Java sync-link --><script language="Javascript" src="../rzahg/synch.js" type="text/javascript"></script>
<h1 class="topictitle1">Other methods to avoid rebuilding access paths</h1>
<div><p>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. </p>
<p>The system uses a file synchronization indicator to determine if an access
path needs to be rebuilt. Normally, the synchronization indicator is on, indicating
the synchronization of the access path and its associated data. When a job
changes a file that affects an access path, the system turns off the synchronization
indicator in the file. If the system ends abnormally, it must rebuild any
access path whose file has its synchronization indicator off.</p>
<p>You need to periodically synchronize the data with its access path to reduce
the number of access paths you must rebuild. There are several methods to
synchronize a file with its access path:</p>
<ul><li>Full file close. The last full (that is, not shared) system-wide close
performed against a file will synchronize the access path and the data.</li>
<li>Force access path. Specify the force-access-path (FRCACCPTH) parameter
on the create, change, or override database file commands.</li>
<li>Force write ratio of 2 or greater. Specify the force-write-ratio (FRCRATIO)
parameter on the create, change, or override database file commands.</li>
<li>Force end of data. Running the force-end-of-data operation in your program
can synchronize the file's data and its access path. (Some high-level languages
do not have a force-end-of-data operation. See your high-level language topic collection
for further details.)</li>
</ul>
<p>Performing one of the methods mentioned previously synchronizes the access
path and the data. However, the next change to the data in the file can turn
the synchronization indicator off again. </p>
<p>Note that each of the methods can be costly in terms of performance; therefore,
use them with caution. Consider journaling access paths along with saving
access paths or using SMAPP as the primary means of protecting access paths.</p>
</div>
<div>
<div class="familylinks">
<div class="parentlink"><strong>Parent topic:</strong> <a href="rbaforzahfpro.htm" title="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.">Rebuild access paths</a></div>
</div>
</div>
</body>
</html>