109 lines
7.7 KiB
HTML
109 lines
7.7 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="DB2 Multisystem: Basic terms and concepts" />
|
||
|
|
<meta name="abstract" content="A distributed file is a database file that is spread across multiple iSeries servers. This section describes some of the main concepts that are used in discussing the creation and use of distributed files by DB2 Multisystem." />
|
||
|
|
<meta name="description" content="A distributed file is a database file that is spread across multiple iSeries servers. This section describes some of the main concepts that are used in discussing the creation and use of distributed files by DB2 Multisystem." />
|
||
|
|
<meta name="DC.subject" content="distributed file, definition, node, node group, node group, figure, partition number, partition number, number, partition, partitioning, partitioning file, file, partition map, partitioning key, key, partitioning, hashing, map, partition, map, partition, node group object, distributed file, partitioned table" />
|
||
|
|
<meta name="keywords" content="distributed file, definition, node, node group, node group, figure, partition number, partition number, number, partition, partitioning, partitioning file, file, partition map, partitioning key, key, partitioning, hashing, map, partition, map, partition, node group object, distributed file, partitioned table" />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="intro.htm" />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="partitionedtables.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="basicterms" />
|
||
|
|
<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>DB2 Multisystem: Basic terms
|
||
|
|
and concepts</title>
|
||
|
|
</head>
|
||
|
|
<body id="basicterms"><a name="basicterms"><!-- --></a>
|
||
|
|
<!-- Java sync-link --><script language="Javascript" src="../rzahg/synch.js" type="text/javascript"></script>
|
||
|
|
<h1 class="topictitle1"><span class="keyword">DB2 Multisystem</span>: Basic terms
|
||
|
|
and concepts</h1>
|
||
|
|
<div><p>A <em>distributed file</em> is a database file that is spread across
|
||
|
|
multiple <span class="keyword">iSeries™</span> servers. This
|
||
|
|
section describes some of the main concepts that are used in discussing the
|
||
|
|
creation and use of distributed files by DB2<sup>®</sup> Multisystem.</p>
|
||
|
|
<p>Each server that has a piece of a distributed file is called a <em>node</em>.
|
||
|
|
Each server is identified by the name that is defined for it in the relational
|
||
|
|
database directory.</p>
|
||
|
|
<p>A group of systems that contains one or more distributed files is called
|
||
|
|
a <em>node group</em>. A <em>node group</em> is a system object that contains
|
||
|
|
the list of nodes across which the data is distributed. A system can be a
|
||
|
|
node in more than one node group.</p>
|
||
|
|
<div class="fignone" id="basicterms__fki"><a name="basicterms__fki"><!-- --></a><span class="figcap">Figure 1. Node groups</span><br /><img src="rbal3509.gif" alt="This graphic shows two node groups. Node group one contains systems A, B, and C. Node group two contains systems A, B, and D. Node groups one and two share systems A and B because a system can be a node in more than one node group." /><br /></div>
|
||
|
|
<p>A file is distributed across all the systems in a node group through <em>partitioning</em>. <em>Table
|
||
|
|
partitioning</em>, further described in Partitioned tables, applies to tables
|
||
|
|
partitioned on a single system.</p>
|
||
|
|
<p>A <em>partition number</em> is a number from 0 to 1023. Each partition number
|
||
|
|
is assigned to a node in the node group. Each node can be assigned many partition
|
||
|
|
numbers. The correlation between nodes and partition numbers is stored in
|
||
|
|
a <em>partition map</em>. The partition map is also stored as part of the node
|
||
|
|
group object. You can provide the partition map when you create a node group;
|
||
|
|
otherwise, the system generates a default map.</p>
|
||
|
|
<p>You define a partition map by using a partitioning file. A <em>partitioning
|
||
|
|
file</em> is a physical file that defines a node number for each
|
||
|
|
partition number.</p>
|
||
|
|
<p>A <em>partitioning key</em> consists of one or more fields in the file that
|
||
|
|
is being distributed. The partitioning key is used to determine which node
|
||
|
|
in the node group is to physically contain rows with certain values. This
|
||
|
|
is done by using <em>hashing</em>, an operating system function that takes the
|
||
|
|
value of the partitioning key for a record and maps it to a partition number.
|
||
|
|
The node corresponding to that partition number is used to store the record.</p>
|
||
|
|
<p>The following example shows what partition number and nodes might look
|
||
|
|
like for a distributed table for two systems. The table has a partitioning
|
||
|
|
key of LASTNAME.</p>
|
||
|
|
|
||
|
|
<div class="tablenoborder"><a name="basicterms__fig1"><!-- --></a><table cellpadding="4" cellspacing="0" summary="" id="basicterms__fig1" frame="void" border="0" rules="none"><caption>Table 1. Partition map</caption><thead align="left"><tr><th valign="top" width="NaN%" class="firstcol" id="d0e210">Partition number</th>
|
||
|
|
<th valign="top" width="NaN%" id="d0e212">Node</th>
|
||
|
|
</tr>
|
||
|
|
</thead>
|
||
|
|
<tbody><tr><th valign="top" width="NaN%" class="firstcol" id="d0e216" headers="d0e210 ">0</th>
|
||
|
|
<td valign="top" width="NaN%" headers="d0e216 d0e212 ">SYSA</td>
|
||
|
|
</tr>
|
||
|
|
<tr><th valign="top" width="NaN%" class="firstcol" id="d0e221" headers="d0e210 ">1</th>
|
||
|
|
<td valign="top" width="NaN%" headers="d0e221 d0e212 ">SYSB</td>
|
||
|
|
</tr>
|
||
|
|
<tr><th valign="top" width="NaN%" class="firstcol" id="d0e226" headers="d0e210 ">2</th>
|
||
|
|
<td valign="top" width="NaN%" headers="d0e226 d0e212 ">SYSA</td>
|
||
|
|
</tr>
|
||
|
|
<tr><th valign="top" width="NaN%" class="firstcol" id="d0e231" headers="d0e210 ">3</th>
|
||
|
|
<td valign="top" width="NaN%" headers="d0e231 d0e212 ">SYSB</td>
|
||
|
|
</tr>
|
||
|
|
</tbody>
|
||
|
|
</table>
|
||
|
|
</div>
|
||
|
|
<p>In the partition map, partition number 0 contains SYSA,
|
||
|
|
partition number 1 contains node SYSB, partition number 2 contains SYSA, and
|
||
|
|
partition number 3 contains SYSB. This pattern is repeated.</p>
|
||
|
|
<p>The hashing of the partitioning key determines a number
|
||
|
|
that corresponds to a partition number. For example, a record that has a value
|
||
|
|
of <tt>Andrews</tt> might hash to partition number 1. A record that has a
|
||
|
|
value of <tt>Anderson</tt> might hash to partition number 2. If you refer
|
||
|
|
to the partition map shown in <a href="#basicterms__fig1">Table 1</a>, records
|
||
|
|
for partition number 1 are stored at SYSB, while records for partition number
|
||
|
|
2 are stored at SYSA.</p>
|
||
|
|
</div>
|
||
|
|
<div>
|
||
|
|
<div class="familylinks">
|
||
|
|
<div class="parentlink"><strong>Parent topic:</strong> <a href="intro.htm" title="DB2 Multisystem is a parallel processing technique that provides greater scalability for databases.">DB2 Multisystem introduction</a></div>
|
||
|
|
</div>
|
||
|
|
<div class="relconcepts"><strong>Related concepts</strong><br />
|
||
|
|
<div><a href="partitionedtables.htm" title="DB2 UDB for iSeries supports partitioned tables using SQL.">Partitioned tables</a></div>
|
||
|
|
</div>
|
||
|
|
</div>
|
||
|
|
</body>
|
||
|
|
</html>
|