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

69 lines
5.2 KiB
HTML
Raw Permalink 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="Reduce time in access path recovery" />
<meta name="abstract" content="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." />
<meta name="description" content="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." />
<meta name="DC.Relation" scheme="URI" content="rbaforzahfpra.htm" />
<meta name="DC.Relation" scheme="URI" content="rbaforzahfprj.htm" />
<meta name="DC.Relation" scheme="URI" content="rbaforzahfprk.htm" />
<meta name="DC.Relation" scheme="URI" content="rbaforzahfprl.htm" />
<meta name="DC.Relation" scheme="URI" content="rbaforzahfprn.htm" />
<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="rbaforzahfpri" />
<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>Reduce time in access path recovery</title>
</head>
<body id="rbaforzahfpri"><a name="rbaforzahfpri"><!-- --></a>
<!-- Java sync-link --><script language="Javascript" src="../rzahg/synch.js" type="text/javascript"></script>
<h1 class="topictitle1">Reduce time in access path recovery</h1>
<div><p>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.</p>
<p>Access path recovery can take a long time, especially if you have large
access paths or many access paths to be rebuilt. You can reduce this recovery
time in several ways.</p>
<p>Journaling access paths is often faster than rebuilding access paths. With
the System-managed access path protection (SMAPP) support, you do not have
to use the journaling commands, such as the Start Journal Access Path (STRJRNAP)
command, to get the benefits of access path journaling. SMAPP support recovers
access paths after an abnormal system end rather than rebuilding them during
IPL.</p>
</div>
<div>
<ul class="ullinks">
<li class="ulchildlink"><strong><a href="rbaforzahfprj.htm">Save access paths</a></strong><br />
You can reduce the recovery time of access paths by saving access paths. The access path (ACCPTH) parameter on the Save Changed Objects (SAVCHGOBJ), Save Library (SAVLIB), and Save Object (SAVOBJ) commands allows you to save access paths.</li>
<li class="ulchildlink"><strong><a href="rbaforzahfprk.htm">Restore access paths</a></strong><br />
The system has the ability to restore access paths and it usually restores an access path faster than it rebuilds it.</li>
<li class="ulchildlink"><strong><a href="rbaforzahfprl.htm">Journal access paths</a></strong><br />
Journaling access paths can significantly reduce recovery time by reducing the number of access paths that need to be rebuilt after an abnormal system end. It is recommended that you journal access paths because larger access paths require more time to rebuild.</li>
<li class="ulchildlink"><strong><a href="rbaforzahfprn.htm">System-managed access-path protection</a></strong><br />
System-managed access-path protection (SMAPP) provides automatic protection for access paths. With SMAPP support, you do not have to use the journaling commands, such as the Start Journal Access Path (STRJRNAP) command, to get the benefits of access path journaling.</li>
<li class="ulchildlink"><strong><a href="rbaforzahfpro.htm">Rebuild access paths</a></strong><br />
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.</li>
</ul>
<div class="familylinks">
<div class="parentlink"><strong>Parent topic:</strong> <a href="rbaforzahfpra.htm" title="These topics discuss the iSeries functions of recovering or restoring your database after the system loses data.">Recover and restore your database</a></div>
</div>
</div>
</body>
</html>