106 lines
6.7 KiB
HTML
106 lines
6.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 xmlns="http://www.w3.org/1999/xhtml" lang="en-US" xml:lang="en-us">
|
|
<head>
|
|
<meta http-equiv="Content-Type" content="text/html; charset=utf-8" />
|
|
<meta name="dc.language" scheme="rfc1766" 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. -->
|
|
<meta name="dc.date" scheme="iso8601" content="2005-09-19" />
|
|
<meta name="copyright" content="(C) Copyright IBM Corporation 1998, 2006" />
|
|
<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="keywords" content="relational database" />
|
|
<title>Relational database</title>
|
|
<link rel="stylesheet" type="text/css" href="ibmidwb.css" />
|
|
<link rel="stylesheet" type="text/css" href="ic.css" />
|
|
</head>
|
|
<body>
|
|
<a id="Top_Of_Page" name="Top_Of_Page"></a><!-- Java sync-link -->
|
|
<script language = "Javascript" src = "../rzahg/synch.js" type="text/javascript"></script>
|
|
|
|
|
|
<a name="relationaldb"></a>
|
|
<h2 id="relationaldb"><a href="rbafzmst02.htm#ToC_16">Relational database</a></h2><a id="idx1" name="idx1"></a>
|
|
<p>A <span class="italic">relational database</span> is a database that can be
|
|
perceived as a set of tables and can be manipulated in accordance with the
|
|
relational model of data. The relational database contains a set of objects
|
|
used to store, access, and manage data. The set of objects includes tables,
|
|
views, indexes, aliases, distinct types, functions, procedures, sequences, and packages.</p>
|
|
<p>There are three types of relational databases a user can access from an iSeries system. </p>
|
|
<dl>
|
|
<dt class="bold">system relational database</dt>
|
|
<dd>There is one default relational database on any iSeries system. The system
|
|
relational database is always local to that iSeries system. It consists of all
|
|
the database objects that exist on disk attached to the iSeries system that are
|
|
not stored on independent auxiliary storage pools. For more information on
|
|
independent auxiliary storage pools, see the <a href="../rzahg/rzahgicbasic2.htm">System
|
|
Management </a>category of the iSeries™ Information Center.
|
|
<p>The name of the
|
|
system relational database is, by default, the same as the iSeries system name.
|
|
However, a different name can be assigned through the use of the ADDRDBDIRE
|
|
(Add RDB Directory Entry) command or iSeries Navigator.</p>
|
|
</dd>
|
|
<dt class="bold">user relational database</dt>
|
|
<dd>The user may create additional relational databases on an iSeries system
|
|
by configuring independent auxiliary storage pools on the system. Each primary
|
|
independent auxiliary storage pool is a relational database. It consists of
|
|
all the database objects that exist on the independent auxiliary storage pool
|
|
disks. Additionally, all database objects in the system relational database
|
|
of the iSeries system to which the independent auxiliary storage pool is connected
|
|
are logically included in a user relational database. Thus, the name of any
|
|
schema created in a user relational database must not already exist in that
|
|
user relational database or in the associated system relational database.
|
|
<p>Although the objects in the system relational database are logically included
|
|
in a user relational database, certain dependencies between the objects in
|
|
the system relational database and the user relational database are not allowed:</p>
|
|
<ul>
|
|
<li>A view must be created into a schema that exists in the same relational
|
|
database as its referenced tables, views, or functions.</li>
|
|
<li>An index must be created into a schema that exists in the same relational
|
|
database as its referenced table.</li>
|
|
<li>A trigger or constraint must be created into a schema that exists in the
|
|
same relational database as its base table.</li>
|
|
<li>The parent table and dependent table in a referential constraint must
|
|
both exist in the same relational database.</li>
|
|
<li>A table must be created into a schema that exists in the same relational
|
|
database as any referenced distinct types.</li>
|
|
<li>The parent table and dependent table in a referential constraint must
|
|
both exist in the same relational database.</li></ul><p class="indatacontent">Other dependencies between the objects in the system relational database
|
|
and the user relational database are allowed. For example, a procedure in
|
|
a schema in a user relational database may reference objects in the system
|
|
relational database. However, operations on such an object may fail if the
|
|
other relational database is not available. For example, if a user relational
|
|
database is varied off and then varied on to another system.</p>
|
|
<p>A user
|
|
relational database is local to an iSeries system while the independent auxiliary
|
|
storage pool is varied on. Independent auxiliary storage pools can be varied
|
|
off on one iSeries system and then varied on to another iSeries system. Hence, a
|
|
user relational databases may be local to a given iSeries system at one point
|
|
in time and remote at a different point in time. For more information on independent
|
|
auxiliary storage pools, see the <a href="../rzahg/rzahgicbasic2.htm">System Management </a> category of the iSeries Information Center.</p>
|
|
<p>The name of the user
|
|
relational database is, by default, the same as the independent auxiliary
|
|
storage pool name. However, a different name can be assigned through the use
|
|
of the ADDRDBDIRE (Add RDB Directory Entry) command or iSeries Navigator.</p>
|
|
</dd>
|
|
<dt class="bold">remote relational database</dt>
|
|
<dd>Relational databases on other iSeries and non-iSeries systems can be accessed
|
|
remotely. These relational databases must be registered through the use of
|
|
the ADDRDBDIRE (Add RDB Directory Entry) command or iSeries Navigator.
|
|
</dd>
|
|
</dl>
|
|
<p>The database manager is the name used generically to identify the iSeries Licensed Internal
|
|
Code and the DB2 UDB for iSeries portion of the code that manages the relational database.</p>
|
|
<hr /><br />
|
|
[ <a href="#Top_Of_Page">Top of Page</a> | <a href="rbafzmstconcept.htm">Previous Page</a> | <a href="rbafzmstsqlcon.htm">Next Page</a> | <a href="rbafzmst02.htm#wq1">Contents</a> |
|
|
<a href="rbafzmstindex.htm#index">Index</a> ]
|
|
|
|
<a id="Bot_Of_Page" name="Bot_Of_Page"></a>
|
|
</body>
|
|
</html>
|