99 lines
6.4 KiB
HTML
99 lines
6.4 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="task" />
|
||
|
|
<meta name="DC.Title" content="Ensuring two-phase commit integrity" />
|
||
|
|
<meta name="abstract" content="Complete or cancel all pending resynchronizations of commitment control definitions before you replace your software." />
|
||
|
|
<meta name="description" content="Complete or cancel all pending resynchronizations of commitment control definitions before you replace your software." />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="prepareswupgrade.htm" />
|
||
|
|
<meta name="copyright" content="(C) Copyright IBM Corporation 2004, 2006" />
|
||
|
|
<meta name="DC.Rights.Owner" content="(C) Copyright IBM Corporation 2004, 2006" />
|
||
|
|
<meta name="DC.Format" content="XHTML" />
|
||
|
|
<meta name="DC.Identifier" content="ensuretwophase" />
|
||
|
|
<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>Ensuring two-phase commit integrity</title>
|
||
|
|
</head>
|
||
|
|
<body id="ensuretwophase"><a name="ensuretwophase"><!-- --></a>
|
||
|
|
<!-- Java sync-link --><script language="Javascript" src="../rzahg/synch.js" type="text/javascript"></script>
|
||
|
|
<h1 class="topictitle1">Ensuring two-phase commit integrity</h1>
|
||
|
|
<div><p>Complete or cancel all pending resynchronizations of commitment
|
||
|
|
control definitions before you replace your software.</p>
|
||
|
|
<div class="section"> <p>You need to perform this task only if both of the following are
|
||
|
|
true:</p>
|
||
|
|
<ul><li>Your server is connected in a network.</li>
|
||
|
|
<li>Your system runs applications that use two-phase commit support.</li>
|
||
|
|
</ul>
|
||
|
|
<p>Two-phase commit support is used when an application updates database
|
||
|
|
files on more than one system. Two-phase commit support ensures that the databases
|
||
|
|
remained synchronized. If you are not sure whether your system uses two-phase
|
||
|
|
commit support, perform steps <a href="#ensuretwophase__step1twophase">1</a> and <a href="#ensuretwophase__step2twophase">2</a>. You might need to continue with
|
||
|
|
the rest of the procedure.</p>
|
||
|
|
<p>Remember that any actions you take with respect
|
||
|
|
to a pending resynchronization affect the other systems that are participating
|
||
|
|
in the logical unit of work (transaction) with your system. Therefore, you
|
||
|
|
or someone else will also need to handle pending resynchronizations on the
|
||
|
|
connected systems before you begin your upgrade procedure.</p>
|
||
|
|
<p>If you perform
|
||
|
|
this procedure 1 or 2 days before you install the new release, you should
|
||
|
|
recheck for resynchronizations before starting the installation.</p>
|
||
|
|
<p>To
|
||
|
|
work with pending resynchronizations on your source system, do the following:</p>
|
||
|
|
</div>
|
||
|
|
<ol><li class="stepexpand" id="ensuretwophase__step1twophase"><a name="ensuretwophase__step1twophase"><!-- --></a><span>To display all commitment definitions that might
|
||
|
|
require resynchronization, type the following Work with Commitment Definitions
|
||
|
|
(WRKCMTDFN) command:</span> <pre>WRKCMTDFN JOB(*ALL) STATUS(*RESYNC)</pre>
|
||
|
|
</li>
|
||
|
|
<li class="stepexpand" id="ensuretwophase__step2twophase"><a name="ensuretwophase__step2twophase"><!-- --></a><span>If you see the message, <samp class="codeph">No commitment
|
||
|
|
definitions are active</samp>, you can skip the rest of this procedure.</span></li>
|
||
|
|
<li class="stepexpand"><span>On the Work with Commitment Definitions display, type <samp class="codeph">19</samp> (Cancel
|
||
|
|
Resync) in the Option column for each commitment definition. You see the Cancel
|
||
|
|
Resync display.</span></li>
|
||
|
|
<li class="stepexpand"><span>If the value in the column <em>Resync Required</em> is <samp class="codeph">Yes</samp> for
|
||
|
|
any remote location listed, then do the following for that location:</span><ol type="a"><li class="substepexpand"><span>Attempt an action, such as restarting communications, and allow
|
||
|
|
the resynchronization to complete.</span></li>
|
||
|
|
<li class="substepexpand"><span>If you cannot allow the resynchronization to complete, specify
|
||
|
|
option 1 (Select) to cancel resynchronization to that remote location.</span> <p>You could receive message CPF83E4, which indicates that the logical
|
||
|
|
unit of work is in an undecided state. You will have to make an educated decision
|
||
|
|
to force either a commit operation or a rollback operation before you can
|
||
|
|
successfully cancel resynchronization. These options are available from the
|
||
|
|
Work with Commitment Definitions display.</p>
|
||
|
|
<p>By canceling resynchronization,
|
||
|
|
you could cause the databases between the two systems to be in an inconsistent
|
||
|
|
state. You must then take the responsibility for determining the action taken
|
||
|
|
by all the other locations that participated in this Logical Unit of Work
|
||
|
|
(LUW), and resynchronize the database changes.</p>
|
||
|
|
</li>
|
||
|
|
</ol>
|
||
|
|
</li>
|
||
|
|
<li class="stepexpand"><span>Refresh the display periodically. When resynchronization for a
|
||
|
|
commitment definition completes or cancels successfully, the value in the <em>Resync
|
||
|
|
in Progress</em> column will be <samp class="codeph">No</samp>. </span> <p>The resynchronization
|
||
|
|
or a cancelation of resynchronization might not take place immediately. They
|
||
|
|
are dependent on the state of the other systems that are participating in
|
||
|
|
the logical unit of work.</p>
|
||
|
|
</li>
|
||
|
|
</ol>
|
||
|
|
<div class="section"> <p>For more information on commitment control and resynchronization,
|
||
|
|
see the topic <a href="../rzakj/rzakjheuristic.htm">When
|
||
|
|
to force commits and rollbacks and when to cancel resynchronization</a> .</p>
|
||
|
|
</div>
|
||
|
|
</div>
|
||
|
|
<div>
|
||
|
|
<div class="familylinks">
|
||
|
|
<div class="parentlink"><strong>Parent topic:</strong> <a href="prepareswupgrade.htm" title="To prepare the server for software installation, review and perform the preparation tasks that pertain to your server.">Preparing the server for software upgrade or replacement</a></div>
|
||
|
|
</div>
|
||
|
|
</div>
|
||
|
|
</body>
|
||
|
|
</html>
|