76 lines
4.6 KiB
HTML
76 lines
4.6 KiB
HTML
|
<?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="Reuse deleted records" />
|
||
|
|
<meta name="abstract" content="Sometimes you might want to reuse deleted records for your database files. In this case, you can use the REUSEDLT parameter." />
|
||
|
|
<meta name="description" content="Sometimes you might want to reuse deleted records for your database files. In this case, you can use the REUSEDLT parameter." />
|
||
|
|
<meta name="DC.subject" content="record, reusing deleted, deleted record, reusing" />
|
||
|
|
<meta name="keywords" content="record, reusing deleted, deleted record, reusing" />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="rbafoprocop.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="rbaforsdlt" />
|
||
|
|
<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>Reuse deleted records</title>
|
||
|
|
</head>
|
||
|
|
<body id="rbaforsdlt"><a name="rbaforsdlt"><!-- --></a>
|
||
|
|
<!-- Java sync-link --><script language="Javascript" src="../rzahg/synch.js" type="text/javascript"></script>
|
||
|
|
<h1 class="topictitle1">Reuse deleted records</h1>
|
||
|
|
<div><p>Sometimes you might want to reuse deleted records for your database
|
||
|
|
files. In this case, you can use the REUSEDLT parameter.</p>
|
||
|
|
<div class="p">When you specify REUSEDLT(*YES) on the Create Physical File (CRTPF) or
|
||
|
|
Change Physical File (CHGPF) command, the following operations might work
|
||
|
|
differently: <ul><li>Arrival order becomes meaningless for a file that reuses deleted record
|
||
|
|
space. Records might not be added at the end of the file.</li>
|
||
|
|
<li>End-of-file delay does not work for the files that reuse deleted record
|
||
|
|
space.</li>
|
||
|
|
<li>One hundred percent reuse of deleted record space is not guaranteed. A <em>file
|
||
|
|
full</em> condition might be reached or the file might be extended even though
|
||
|
|
deleted record space still exists in the file.</li>
|
||
|
|
</ul>
|
||
|
|
</div>
|
||
|
|
<div class="note"><span class="notetitle">Note:</span> Because of the way the system reuses deleted record space, the following
|
||
|
|
types of files should not be created or changed to reuse deleted record space:<ul><li>Files processed using relative record numbers, and files used by an application
|
||
|
|
to determine a relative record number that is used as a key into another file</li>
|
||
|
|
<li>Files used as queues</li>
|
||
|
|
<li>Any files used by applications that assume new record insertions are at
|
||
|
|
the end of the file</li>
|
||
|
|
<li>When <span class="keyword">DB2<sup>®</sup> UDB Symmetric Multiprocessing</span> is installed,
|
||
|
|
files on which you expect to have parallel index maintenance performed when
|
||
|
|
rows are updated, inserted, or deleted</li>
|
||
|
|
</ul>
|
||
|
|
</div>
|
||
|
|
<p>If you decide to change an existing physical file to reuse deleted record
|
||
|
|
space, and there are logical files with access paths with first-in-first-out
|
||
|
|
(FIFO) or last-in-first-out (LIFO) duplicate key ordering over the physical
|
||
|
|
file, you can re-create the logical files without the FIFO or LIFO attribute
|
||
|
|
and avoid rebuilding the existing access path by following these steps:</p>
|
||
|
|
<ol><li>Rename the existing logical file that has the FIFO or LIFO attribute.</li>
|
||
|
|
<li>Create a second logical file identical to the renamed file
|
||
|
|
except that duplicate key ordering should not be specified for the file. Give
|
||
|
|
the new file the original file name. The new file shares the access path of
|
||
|
|
the renamed file.</li>
|
||
|
|
<li>Delete the renamed file.</li>
|
||
|
|
</ol>
|
||
|
|
</div>
|
||
|
|
<div>
|
||
|
|
<div class="familylinks">
|
||
|
|
<div class="parentlink"><strong>Parent topic:</strong> <a href="rbafoprocop.htm" title="These topics describe several runtime processing options.">File processing options</a></div>
|
||
|
|
</div>
|
||
|
|
</div>
|
||
|
|
</body>
|
||
|
|
</html>
|