86 lines
5.7 KiB
HTML
86 lines
5.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="reference" />
|
|
<meta name="DC.Title" content="Journaling" />
|
|
<meta name="abstract" content="The DB2 UDB for iSeries journal support supplies an audit trail and forward and backward recovery." />
|
|
<meta name="description" content="The DB2 UDB for iSeries journal support supplies an audit trail and forward and backward recovery." />
|
|
<meta name="DC.subject" content="journaling, data integrity, auxiliary storage pools, schema, auxiliary storage pools" />
|
|
<meta name="keywords" content="journaling, data integrity, auxiliary storage pools, schema, auxiliary storage pools" />
|
|
<meta name="DC.Relation" scheme="URI" content="rbafydataintex.htm" />
|
|
<meta name="DC.Relation" scheme="URI" content="rbafyrfupdating.htm" />
|
|
<meta name="DC.Relation" scheme="URI" content="../rzaki/rzakikickoff.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="rbafyjourg" />
|
|
<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</title>
|
|
</head>
|
|
<body id="rbafyjourg"><a name="rbafyjourg"><!-- --></a>
|
|
<!-- Java sync-link --><script language="Javascript" src="../rzahg/synch.js" type="text/javascript"></script>
|
|
<h1 class="topictitle1">Journaling</h1>
|
|
<div><p>The <span class="keyword">DB2<sup>®</sup> UDB for iSeries™</span> journal
|
|
support supplies an audit trail and forward and backward recovery.</p>
|
|
<div class="section"><p>Forward recovery can be used to take an older version of a table
|
|
and apply the changes logged on the journal to the table. Backward recovery
|
|
can be used to remove changes logged on the journal from the table.</p>
|
|
</div>
|
|
<div class="section"><p>When an SQL schema is created, a journal and journal receiver
|
|
are created in the schema. When SQL creates the journal and journal receiver,
|
|
they are only created on a user auxiliary storage pool (ASP) if the ASP clause
|
|
is specified on the CREATE SCHEMA statement. However, because placing journal
|
|
receivers on their own ASPs can improve performance, the person managing the
|
|
journal might want to create all future journal receivers on a separate ASP.</p>
|
|
</div>
|
|
<div class="section"><p>When a table is created into the schema, it is automatically journaled
|
|
to the journal <span class="keyword">DB2 UDB for iSeries</span> created
|
|
in the schema (QSQJRN). A table created in a non-schema will also have journaling
|
|
started if a journal named QSQJRN exists in that library. After this point,
|
|
it is your responsibility to use the journal functions to manage the journal,
|
|
the journal receivers, and the journaling of tables to the journal. For example,
|
|
if a table is moved into a schema, no automatic change to the journaling status
|
|
occurs. If a table is restored, the normal journal rules apply. That is,
|
|
if the table was journaled at the time of the save, it is journaled to the
|
|
same journal at restore time. If the table was not journaled at the time
|
|
of the save, it is not journaled at restore time.</p>
|
|
</div>
|
|
<div class="section"><p>The journal created in the SQL collection is normally the journal
|
|
used for logging all changes to SQL tables. You can, however, use the system
|
|
journal functions to journal SQL tables to a different journal.</p>
|
|
</div>
|
|
<div class="section"><p>A user can stop journaling on any table using the journal functions,
|
|
but doing so prevents an application from running under commitment control.
|
|
If journaling is stopped on a parent table of a referential constraint with
|
|
a delete rule of NO ACTION, CASCADE, SET NULL, or SET DEFAULT, all update
|
|
and delete operations will be prevented. Otherwise, an application is still
|
|
able to function if you have specified COMMIT(*NONE); however, this does not
|
|
provide the same level of integrity that journaling and commitment control
|
|
provide.</p>
|
|
</div>
|
|
</div>
|
|
<div>
|
|
<div class="familylinks">
|
|
<div class="parentlink"><strong>Parent topic:</strong> <a href="rbafydataintex.htm" title="Data integrity protects data from being destroyed or changed by unauthorized persons, system operation or hardware failures (such as physical damage to a disk), programming errors, interruptions before a job is completed (such as a power failure), or interference from running applications at the same time (such as serialization problems).">Data integrity</a></div>
|
|
</div>
|
|
<div class="relref"><strong>Related reference</strong><br />
|
|
<div><a href="rbafyrfupdating.htm" title="If you are updating a parent table, you cannot modify a primary key for which dependent rows exist.">Update tables with referential constraints</a></div>
|
|
</div>
|
|
<div class="relinfo"><strong>Related information</strong><br />
|
|
<div><a href="../rzaki/rzakikickoff.htm">Journaling</a></div>
|
|
</div>
|
|
</div>
|
|
</body>
|
|
</html> |