95 lines
6.6 KiB
HTML
95 lines
6.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="Redistribution issues for adding systems to a network" />
|
||
|
|
<meta name="abstract" content="The redistribution of a file across a node group is a fairly simple process." />
|
||
|
|
<meta name="description" content="The redistribution of a file across a node group is a fairly simple process." />
|
||
|
|
<meta name="DC.subject" content="redistribution issues, when adding systems to network, adding systems to network, redistribution issues, systems, adding to network, network, adding systems to" />
|
||
|
|
<meta name="keywords" content="redistribution issues, when adding systems to network, adding systems to network, redistribution issues, systems, adding to network, network, adding systems to" />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="expanddb2.htm" />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="custdd.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="scali" />
|
||
|
|
<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>Redistribution issues for adding systems to a network</title>
|
||
|
|
</head>
|
||
|
|
<body id="scali"><a name="scali"><!-- --></a>
|
||
|
|
<!-- Java sync-link --><script language="Javascript" src="../rzahg/synch.js" type="text/javascript"></script>
|
||
|
|
<h1 class="topictitle1">Redistribution issues for adding systems to a network</h1>
|
||
|
|
<div><p>The redistribution of a file across a node group is a fairly simple
|
||
|
|
process.</p>
|
||
|
|
<p>You can use the Change Physical File (CHGPF) command to specify either
|
||
|
|
a new node group for a file or a new partitioning key for a file. The CHGPF
|
||
|
|
command can be used to make a local file into a distributed file, to make
|
||
|
|
a distributed file into a local file, or to redistribute a distributed file
|
||
|
|
either across a different set of nodes or with a different partitioning key.</p>
|
||
|
|
<p>You should be aware that the process of redistribution might involve the
|
||
|
|
movement of nearly every record in the file. For very large files, this can
|
||
|
|
be a long process during which the data in the file is unavailable. You should
|
||
|
|
not do file redistribution often or without proper planning.</p>
|
||
|
|
<p>To change a local physical file into a distributed file, you must specify
|
||
|
|
the node group (NODGRP) and partitioning key (PTNKEY) parameters on the CHGPF
|
||
|
|
command. Issuing this command changes the file to be distributed across the
|
||
|
|
nodes in the node group, and any existing data is also distributed using the
|
||
|
|
partitioning key specified on the PTNKEY parameter.</p>
|
||
|
|
<p>To change a distributed file into a local file, you must specify NODGRP(*NONE)
|
||
|
|
on the CHGPF command. This deletes all the remote pieces of the file and forces
|
||
|
|
all of the data back to the local system.</p>
|
||
|
|
<p>To change the partitioning key of a distributed file, specify the wanted
|
||
|
|
fields on the PTNKEY parameter of the CHGPF command. This does not affect
|
||
|
|
which systems the file is distributed over. It does cause all of the data
|
||
|
|
to be redistributed, because the hashing algorithm needs to be applied to
|
||
|
|
a new partitioning key.</p>
|
||
|
|
<p>To specify a new set of systems over which the file should be distributed,
|
||
|
|
specify a node group name on the node group (NODGRP) parameter of the CHGPF
|
||
|
|
command. This results in the file being distributed over this new set of systems.
|
||
|
|
You can specify a new partitioning key on the PTNKEY parameter. If the PTNKEY
|
||
|
|
parameter is not specified or if *SAME is specified, the existing partitioning
|
||
|
|
key is used.</p>
|
||
|
|
<p>The CHGPF command handles creating new pieces of the file if the node group
|
||
|
|
had new systems added to it. The CHGPF command handles deleting pieces of
|
||
|
|
the file if a system is not in the new node group. Note that if you want to
|
||
|
|
delete and re-create a node group and then use the CRTPF command to redistribute
|
||
|
|
the file, you must specify the node group name on the NODGRP parameter of
|
||
|
|
the CHGPF command, even if the node group name is the same as the one that
|
||
|
|
was used when the file was first created. This indicates that you do want
|
||
|
|
the system to look at the node group and to redistribute the file. However,
|
||
|
|
if you specified a node group on the NODGRP parameter and the system recognized
|
||
|
|
that it is identical to the node group currently stored in the file, then
|
||
|
|
no redistribution occurs unless you also specified PTNKEY.</p>
|
||
|
|
<p>For files with referential constraints, if you want to use the CHGPF command
|
||
|
|
to make the parent file and the dependent file distributed files, you should
|
||
|
|
do the following tasks:</p>
|
||
|
|
<ul><li>Remove the referential constraint. If you do not remove the constraint,
|
||
|
|
the file that you distribute first encounters a constraint error, because
|
||
|
|
the other file in the referential constraint relationship is not yet a distributed
|
||
|
|
file.</li>
|
||
|
|
<li>Use the CHGPF command to make both files distributed files.</li>
|
||
|
|
<li>Add the referential constraint again.</li>
|
||
|
|
</ul>
|
||
|
|
</div>
|
||
|
|
<div>
|
||
|
|
<div class="familylinks">
|
||
|
|
<div class="parentlink"><strong>Parent topic:</strong> <a href="expanddb2.htm" title="By using distributed relational database files, you can more easily expand the configuration of your iSeries servers.">How DB2 Multisystem helps you expand your database system</a></div>
|
||
|
|
</div>
|
||
|
|
<div class="relconcepts"><strong>Related concepts</strong><br />
|
||
|
|
<div><a href="custdd.htm" title="Because the system is responsible for placing the data, you do not need to know where the records actually reside. However, if you want to guarantee that certain records are always stored on a particular system, you can use the Change Node Group Attributes (CHGNODGRPA) command to specify where those records reside.">Customization of data distribution with DB2 Multisystem</a></div>
|
||
|
|
</div>
|
||
|
|
</div>
|
||
|
|
</body>
|
||
|
|
</html>
|