99 lines
7.2 KiB
HTML
99 lines
7.2 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="Data integrity" />
|
|
<meta name="abstract" content="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)." />
|
|
<meta name="description" content="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)." />
|
|
<meta name="DC.subject" content="data integrity, function, security" />
|
|
<meta name="keywords" content="data integrity, function, security" />
|
|
<meta name="DC.Relation" scheme="URI" content="rbafyprotect.htm" />
|
|
<meta name="DC.Relation" scheme="URI" content="rbafycncr.htm" />
|
|
<meta name="DC.Relation" scheme="URI" content="rbafyjourg.htm" />
|
|
<meta name="DC.Relation" scheme="URI" content="rbafydicomm.htm" />
|
|
<meta name="DC.Relation" scheme="URI" content="rbafysavepoint.htm" />
|
|
<meta name="DC.Relation" scheme="URI" content="rbafyatomic.htm" />
|
|
<meta name="DC.Relation" scheme="URI" content="rbafymovnow.htm" />
|
|
<meta name="DC.Relation" scheme="URI" content="rbafysaverestore.htm" />
|
|
<meta name="DC.Relation" scheme="URI" content="rbafydamagetolerance.htm" />
|
|
<meta name="DC.Relation" scheme="URI" content="rbafyindexrecovery.htm" />
|
|
<meta name="DC.Relation" scheme="URI" content="rbafycatalogintegrity.htm" />
|
|
<meta name="DC.Relation" scheme="URI" content="rbafyuserasp.htm" />
|
|
<meta name="DC.Relation" scheme="URI" content="rbafyiasp.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="rbafydataintex" />
|
|
<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>Data integrity</title>
|
|
</head>
|
|
<body id="rbafydataintex"><a name="rbafydataintex"><!-- --></a>
|
|
<!-- Java sync-link --><script language="Javascript" src="../rzahg/synch.js" type="text/javascript"></script>
|
|
<h1 class="topictitle1">Data integrity</h1>
|
|
<div><p>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).</p>
|
|
</div>
|
|
<div>
|
|
<ul class="ullinks">
|
|
<li class="ulchildlink"><strong><a href="rbafycncr.htm">Concurrency</a></strong><br />
|
|
<dfn class="term">Concurrency</dfn> is the ability for multiple
|
|
users to access and change data in the same table or view at the same time
|
|
without risk of losing data integrity.</li>
|
|
<li class="ulchildlink"><strong><a href="rbafyjourg.htm">Journaling</a></strong><br />
|
|
The <span class="keyword">DB2<sup>®</sup> UDB for iSeries™</span> journal
|
|
support supplies an audit trail and forward and backward recovery.</li>
|
|
<li class="ulchildlink"><strong><a href="rbafydicomm.htm">Commitment control</a></strong><br />
|
|
The <span class="keyword">DB2<sup>®</sup> UDB for iSeries™</span> commitment
|
|
control support provides a means to process a group of database changes like
|
|
update, insert, DDL, or delete operations as a single unit of work (transaction).</li>
|
|
<li class="ulchildlink"><strong><a href="rbafysavepoint.htm">Savepoints</a></strong><br />
|
|
<span>A <dfn class="term">savepoint</dfn> is a
|
|
named entity that represents the state of data and schemas at a particular
|
|
point in time within a unit of work. You can create savepoints within a transaction.
|
|
If the transaction rolls back, changes are undone back to the specified savepoint,
|
|
rather than to the beginning of the transaction.</span></li>
|
|
<li class="ulchildlink"><strong><a href="rbafyatomic.htm">Atomic operations</a></strong><br />
|
|
When running under COMMIT(*CHG), COMMIT(*CS), or COMMIT(*ALL), all operations are guaranteed to be atomic.</li>
|
|
<li class="ulchildlink"><strong><a href="rbafymovnow.htm">Constraints</a></strong><br />
|
|
<span class="keyword">DB2<sup>®</sup> UDB for iSeries™</span> supports
|
|
unique, referential, and check constraints.</li>
|
|
<li class="ulchildlink"><strong><a href="rbafysaverestore.htm">Save/restore</a></strong><br />
|
|
The <span class="keyword">i5/OS™</span> save/restore
|
|
functions are used to save tables, views, indexes, journals, journal receivers,
|
|
sequences, SQL packages, SQL procedures, SQL triggers, user-defined functions,
|
|
user-defined types, and schemas on disk (save file) or to some external media
|
|
(tape or diskette).</li>
|
|
<li class="ulchildlink"><strong><a href="rbafydamagetolerance.htm">Damage tolerance</a></strong><br />
|
|
The server provides several mechanisms to reduce or eliminate damage caused by disk errors.</li>
|
|
<li class="ulchildlink"><strong><a href="rbafyindexrecovery.htm">Index recovery</a></strong><br />
|
|
<span class="keyword">DB2<sup>®</sup> UDB for iSeries™</span> supplies
|
|
several functions to deal with index recovery. </li>
|
|
<li class="ulchildlink"><strong><a href="rbafycatalogintegrity.htm">Catalog integrity</a></strong><br />
|
|
Catalogs contain information about tables, views, SQL packages, sequences, indexes, procedures, functions, triggers, and parameters in a schema.</li>
|
|
<li class="ulchildlink"><strong><a href="rbafyuserasp.htm">User auxiliary storage pool (ASP)</a></strong><br />
|
|
A schema can be created in a user ASP by using the ASP clause on the CREATE COLLECTION and CREATE SCHEMA statements.</li>
|
|
<li class="ulchildlink"><strong><a href="rbafyiasp.htm">Independent auxiliary storage pool (IASP)</a></strong><br />
|
|
Independent disk pools are used to set up user databases on the iSeries™ server. </li>
|
|
</ul>
|
|
|
|
<div class="familylinks">
|
|
<div class="parentlink"><strong>Parent topic:</strong> <a href="rbafyprotect.htm" title="This topic describes the security plan for protecting SQL data from unauthorized users and the methods for ensuring data integrity.">Data protection</a></div>
|
|
</div>
|
|
</div>
|
|
</body>
|
|
</html> |