75 lines
5.0 KiB
HTML
75 lines
5.0 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="Check pending status in referential constraints" />
|
||
|
|
<meta name="abstract" content="Check pending is the condition of a constraint relationship when potential mismatches exist between parent and foreign keys. When the system determines that referential integrity might have been violated, the constraint relationship is marked as check pending." />
|
||
|
|
<meta name="description" content="Check pending is the condition of a constraint relationship when potential mismatches exist between parent and foreign keys. When the system determines that referential integrity might have been violated, the constraint relationship is marked as check pending." />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="rbaforzahfrca.htm" />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="rbaforzahfrcw.htm" />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="rbaforzahfrcx.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="rbaforzahfrcv" />
|
||
|
|
<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>Check pending status in referential constraints</title>
|
||
|
|
</head>
|
||
|
|
<body id="rbaforzahfrcv"><a name="rbaforzahfrcv"><!-- --></a>
|
||
|
|
<!-- Java sync-link --><script language="Javascript" src="../rzahg/synch.js" type="text/javascript"></script>
|
||
|
|
<h1 class="topictitle1">Check pending status in referential constraints</h1>
|
||
|
|
<div><p><em>Check pending</em> is the condition of a constraint relationship
|
||
|
|
when potential mismatches exist between parent and foreign keys. When the
|
||
|
|
system determines that referential integrity might have been violated, the
|
||
|
|
constraint relationship is marked as check pending.</p>
|
||
|
|
<div class="p"> For example: <ul><li>A restore operation where only data in the dependent file is restored
|
||
|
|
and this data is no longer synchronized (a foreign key does not have a parent)
|
||
|
|
with the parent file on the system.</li>
|
||
|
|
<li>A system failure allowed a parent key value to be deleted when a matching
|
||
|
|
foreign key exists. This can only occur when the dependent and parent files
|
||
|
|
are not journaled.</li>
|
||
|
|
<li>A foreign key value does not have a corresponding parent key value. This
|
||
|
|
can happen when you add a referential constraint to existing files that have
|
||
|
|
never before been part of a constraint relationship.</li>
|
||
|
|
</ul>
|
||
|
|
</div>
|
||
|
|
<p>Check pending status is either *NO or *YES.</p>
|
||
|
|
<p>Check pending applies only to the constraints in the established state.
|
||
|
|
A referential constraint that is established and enabled can have a check
|
||
|
|
pending status of *YES or *NO.</p>
|
||
|
|
<p>To get a constraint relationship out of check pending, you must disable
|
||
|
|
the relationship, correct the key (foreign, parent, or both) data, and enable
|
||
|
|
the constraint again. The database then verifies the constraint relationship
|
||
|
|
again.</p>
|
||
|
|
<p>When a relationship is in check pending, the parent and dependent files
|
||
|
|
are in a situation that restricts their use. The parent file I/O restrictions
|
||
|
|
are different from the dependent file restrictions. Check pending restrictions
|
||
|
|
do not apply to the constraints that are in the established and disabled state
|
||
|
|
(which are always in check pending status).</p>
|
||
|
|
</div>
|
||
|
|
<div>
|
||
|
|
<ul class="ullinks">
|
||
|
|
<li class="ulchildlink"><strong><a href="rbaforzahfrcw.htm">Dependent file restrictions in check pending</a></strong><br />
|
||
|
|
This topic outlines the restrictions that apply to an established and enabled referential constraint in check pending.</li>
|
||
|
|
<li class="ulchildlink"><strong><a href="rbaforzahfrcx.htm">Parent file restrictions in check pending</a></strong><br />
|
||
|
|
This topic outlines the restrictions that apply to an established and enabled referential constraint in check pending.</li>
|
||
|
|
</ul>
|
||
|
|
|
||
|
|
<div class="familylinks">
|
||
|
|
<div class="parentlink"><strong>Parent topic:</strong> <a href="rbaforzahfrca.htm" title="These topics discuss how to use referential constraints in your database to ensure that it contains only valid data.">Ensure data integrity with referential constraints</a></div>
|
||
|
|
</div>
|
||
|
|
</div>
|
||
|
|
</body>
|
||
|
|
</html>
|