84 lines
6.1 KiB
HTML
84 lines
6.1 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="Journaling considerations with DB2 Multisystem" />
|
||
|
|
<meta name="abstract" content="Although the Start Journal Physical File (STRJRNPF) and End Journal Physical File (ENDJRNPF) commands are distributed to other systems, the actual journaling takes place on each system independently and to each system's own journal receiver." />
|
||
|
|
<meta name="description" content="Although the Start Journal Physical File (STRJRNPF) and End Journal Physical File (ENDJRNPF) commands are distributed to other systems, the actual journaling takes place on each system independently and to each system's own journal receiver." />
|
||
|
|
<meta name="DC.subject" content="journaling, considerations with, Multisystem, DB2, journaling considerations" />
|
||
|
|
<meta name="keywords" content="journaling, considerations with, Multisystem, DB2, journaling considerations" />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="cldf.htm" />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="usedisfile.htm" />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="cllp.htm" />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="cldf.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="jourc" />
|
||
|
|
<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>Journaling considerations with DB2 Multisystem</title>
|
||
|
|
</head>
|
||
|
|
<body id="jourc"><a name="jourc"><!-- --></a>
|
||
|
|
<!-- Java sync-link --><script language="Javascript" src="../rzahg/synch.js" type="text/javascript"></script>
|
||
|
|
<h1 class="topictitle1">Journaling considerations with DB2<sup>®</sup> Multisystem</h1>
|
||
|
|
<div><p>Although the Start Journal Physical File (STRJRNPF) and End Journal
|
||
|
|
Physical File (ENDJRNPF) commands are distributed to other systems, the actual
|
||
|
|
journaling takes place on each system independently and to each system's own
|
||
|
|
journal receiver.</p>
|
||
|
|
<p>As an example, you have two systems (A and B) on which you have a distributed
|
||
|
|
file. You need to create a journal and a receiver on both system A and system
|
||
|
|
B, and the journal name and library must be the same on both systems. When
|
||
|
|
you issue the STRJRNPF command, the command is distributed to both systems
|
||
|
|
and journaling starts on both systems. However, the journal receiver on system
|
||
|
|
A contains only the data for changes that occur to the piece of the file that
|
||
|
|
resides on system A. The journal receiver on system B contains
|
||
|
|
only the data for changes that occur to the piece of the file that resides
|
||
|
|
on system B.</p>
|
||
|
|
<p>This affects your save and restore strategy as well as your backup strategy;
|
||
|
|
for example:</p>
|
||
|
|
<ul><li>After you issue the STRJRNPF command, you should save the database file
|
||
|
|
from each of the systems in the file's node group.</li>
|
||
|
|
<li>You need to practice standard journal management on each of the systems.
|
||
|
|
You need to change and to save the journal receivers appropriately, so that
|
||
|
|
you can manage the disk space usage for each system. Or, you can take advantage
|
||
|
|
of the system change-journal management support. <div class="note"><span class="notetitle">Note:</span> Just the names of
|
||
|
|
the journal must be the same on each of the systems; the attributes do not.
|
||
|
|
Therefore, for example, you can specify a different journal receiver threshold
|
||
|
|
value on the different systems, reflecting the available disk space on each
|
||
|
|
of those systems.</div>
|
||
|
|
</li>
|
||
|
|
<li>If you do need to recover a piece of a distributed database file, you
|
||
|
|
only need to use the journal receiver from the system where the piece of the
|
||
|
|
distributed file resided. From that journal receiver, you apply the journaled
|
||
|
|
changes using the Apply Journaled Changes (APYJRNCHG) command or remove the
|
||
|
|
journaled changes using the Remove Journaled Changes (RMVJRNCHG) command.</li>
|
||
|
|
<li>You are <strong>not</strong> be able to use the journal receiver from one system
|
||
|
|
to apply or remove the journaled changes to a piece of the file on another
|
||
|
|
system. This is because each piece of the file on each system has its own
|
||
|
|
unique journal identifier (JID).</li>
|
||
|
|
</ul>
|
||
|
|
</div>
|
||
|
|
<div>
|
||
|
|
<div class="familylinks">
|
||
|
|
<div class="parentlink"><strong>Parent topic:</strong> <a href="cldf.htm" title="Some CL commands, when run, affect all the pieces of the distributed file.">CL commands: Affect all the pieces of a distributed file with DB2 Multisystem</a></div>
|
||
|
|
</div>
|
||
|
|
<div class="relconcepts"><strong>Related concepts</strong><br />
|
||
|
|
<div><a href="usedisfile.htm" title="As soon as the file is created, the system ensures that the data is partitioned and that the files remain at concurrent levels.">System activities after the distributed file is created</a></div>
|
||
|
|
<div><a href="cllp.htm" title="Some CL commands, when run, affect only the piece of the distributed file that is located on the local system (the system from which the command was run).">CL commands: Affect only local pieces of a distributed file with DB2 Multisystem</a></div>
|
||
|
|
<div><a href="cldf.htm" title="Some CL commands, when run, affect all the pieces of the distributed file.">CL commands: Affect all the pieces of a distributed file with DB2 Multisystem</a></div>
|
||
|
|
</div>
|
||
|
|
</div>
|
||
|
|
</body>
|
||
|
|
</html>
|