53 lines
3.6 KiB
HTML
53 lines
3.6 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="Verify referential constraints" />
|
|
<meta name="abstract" content="The system automatically verifies the validity of a referential constraint when you add the constraint with the Add Physical File Constraint (ADDPFCST) command. The system verifies that every non-null value in the foreign key matches a corresponding value in the parent key." />
|
|
<meta name="description" content="The system automatically verifies the validity of a referential constraint when you add the constraint with the Add Physical File Constraint (ADDPFCST) command. The system verifies that every non-null value in the foreign key matches a corresponding value in the parent key." />
|
|
<meta name="DC.Relation" scheme="URI" content="rbaforzahfrca.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="rbaforzahfrco" />
|
|
<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>Verify referential constraints</title>
|
|
</head>
|
|
<body id="rbaforzahfrco"><a name="rbaforzahfrco"><!-- --></a>
|
|
<!-- Java sync-link --><script language="Javascript" src="../rzahg/synch.js" type="text/javascript"></script>
|
|
<h1 class="topictitle1">Verify referential constraints</h1>
|
|
<div><p>The system automatically verifies the validity of a referential
|
|
constraint when you add the constraint with the Add Physical File Constraint
|
|
(ADDPFCST) command. The system verifies that every non-null value in the foreign
|
|
key matches a corresponding value in the parent key.</p>
|
|
<p>If the verification is successful, the constraint rules are enforced on
|
|
subsequent accesses by a user or an application program. An unsuccessful verification
|
|
causes the constraint to be marked as check pending. If the constraint is
|
|
added with the ADDPFCST command, it will be in check pending but disabled
|
|
state.</p>
|
|
<div class="note"><span class="notetitle">Note:</span> It is not uncommon to add a referential constraint to existing files
|
|
that contain large amounts of data. The ADDPFCST command can take several
|
|
hours to complete when a very large number of records are involved. The add
|
|
process places an exclusive lock on the files. You should take this time factor
|
|
and file availability into consideration before you add a referential
|
|
constraint.</div>
|
|
</div>
|
|
<div>
|
|
<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> |