toc.htm

Debian中文参考手册,系统介绍了Debian系统

<div class="sect2">
<!--
infolevel=all
infotype=general
--><a id="i772665" name="i772665"></a>
<h3>
<font face="arial, helvetica, sans-serif" color="#330099">
Character Sets
</font>
</h3>
<p>The following section provides information on restrictions and updates to character sets.
</p>
<div class="sect3">
<!--
infolevel=all
infotype=general
--><a id="i772667" name="i772667"></a>
<h4>
<font face="arial, helvetica, sans-serif" color="#330099">
Oracle9<em>i</em> NCHAR Datatypes 
</font>
</h4>
<p>In Oracle9<em>i</em> release 2 (9.2.0.1.0), the SQL NCHAR datatypes are limited to the Unicode character set encoding (UTF8 and AL16UTF16). Alternative character sets such as the fixed-width Asian character set JA16SJISFIXED in Oracle8<em>i</em> are no longer supported.
</p>
<p>To migrate existing NCHAR, NVARCHAR, and NCLOB columns, export and import NCHAR columns, complete the following steps: 
</p>
<ol type="1" start="1">
<li>
<p>Export all SQL NCHAR columns from Oracle8<em>i</em>. 
</p>
</li>
<li>
<p>Drop the SQL NCHAR columns. 
</p>
</li>
<li>
<p>Migrate the database to Oracle9<em>i</em><em>.</em>
</p>
</li>
<li>
<p>Import the SQL NCHAR columns in to Oracle9<em>i</em>. 
</p>
</li>
</ol>
</div class="sect3">
<div class="sect3">
<!--
infolevel=all
infotype=general
--><a id="i772691" name="i772691"></a>
<h4>
<font face="arial, helvetica, sans-serif" color="#330099">
AL24UTFFSS Character Set 
</font>
</h4>
<p>Oracle9<em>i</em> release 2 (9.2.0.1.0) does not support the Unicode character set AL24UTFFSS introduced in Oracle7. This character set was based on the Unicode standard 1.1, which is now obsolete. 
</p>
<p>Oracle9<em>i</em> release 2 (9.2.0.1.0) supports the Unicode database character sets AL32UTF8 and UTF8. These database character sets include the Unicode enhancements based on the Unicode standard 3.0. 
</p>
<p>To migrate the existing AL24UTFFSS database, upgrade your database character set to UTF8 before upgrading to Oracle9<em>i</em>. Oracle Corporation recommends that you use the Character Set Scanner for data analysis before attempting to migrate your existing database character set.
</p>
</div class="sect3">
<div class="sect3">
<!--
infolevel=all
infotype=general
--><a id="i772709" name="i772709"></a>
<h4>
<font face="arial, helvetica, sans-serif" color="#330099">
Character Set Scanner
</font>
</h4>
<p>Set the LIBPATH variable to include the <code>&#036;ORACLE&#095;HOME&#047;lib</code> directory before running the Character Set Scanner (csscan) from the <code>&#036;ORACLE&#095;HOME</code> directory. If you do not correctly set the LIBPATH variable, then the csscan utility will fail. 
</p>
</div class="sect3">
</div class="sect2"><a id="CHDCGCHD" name="CHDCGCHD"></a>
<div class="sect2">
<!--
infolevel=all
infotype=general
--><a id="i772655" name="i772655"></a>
<h3>
<font face="arial, helvetica, sans-serif" color="#330099">
Demo Schema
</font>
</h3>
<p>If you select a multibyte character set or UTF as the national character set in Oracle9<em>i</em> release 2 (9.2.0.1.0), then you must recreate the demo schema and the database installation. 
</p>
<p>For more information on creating schemas, schema dependencies and requirements, refer to the <code>readme.txt</code> file in the <code>&#036;ORACLE&#095;HOME&#047;demo&#047;schema</code> directory. 
</p>
</div class="sect2"><a id="BABHECGC" name="BABHECGC"></a>
<div class="sect2">
<!--
infolevel=all
infotype=general
--><a id="sthref11" name="sthref11"></a>
<h3>
<font face="arial, helvetica, sans-serif" color="#330099">
Oracle Advanced Security
</font>
</h3>
<p>If you install <code>jsse.jar</code> and <code>jcert.jar</code> as extensions (located in <code>&#036;JAVA&#095;HOME&#047;jre&#047;lib&#047;ext</code>), then you must also install <code>jssl-1&#095;1.jar</code> in the same directory.
</p>
</div class="sect2"><a id="CACBIIJI" name="CACBIIJI"></a>
<div class="sect2">
<!--
infolevel=all
infotype=general
--><a id="i772615" name="i772615"></a>
<h3>
<font face="arial, helvetica, sans-serif" color="#330099">
Oracle Internet Directory (OID)
</font>
</h3>
<p>Review the following information if you intend to install Oracle Internet Directory (OID).
</p>
<div class="sect3">
<!--
infolevel=all
infotype=general
--><a id="sthref12" name="sthref12"></a>
<h4>
<font face="arial, helvetica, sans-serif" color="#330099">
Starting Up OID Server
</font>
</h4>
<p>By default, the OID server is started on port 389. If this port is unavailable, then OID server is started on a different port, which is logged in the following file: 
</p>
<pre>&#036;ORACLE&#095;HOME&#047;ldap&#047;install&#047;oidca.out
</pre>
</div class="sect3">
<div class="sect3">
<!--
infolevel=all
infotype=general
--><a id="sthref13" name="sthref13"></a>
<h4>
<font face="arial, helvetica, sans-serif" color="#330099">
Custom Installation and Global Database Name
</font>
</h4>
<p>When performing a custom Oracle Internet Directory installation, do not change the global database name or the Oracle SID. 
</p>
</div class="sect3">
<div class="sect3">
<!--
infolevel=all
infotype=general
--><a id="sthref14" name="sthref14"></a>
<h4>
<font face="arial, helvetica, sans-serif" color="#330099">
Upgrade from Enterprise Edition Oracle9<em>i</em> or Oracle8<em>i</em>
</font>
</h4>
<p>If you have installed in the same ORACLE&#095;HOME either Oracle Internet Directory release 3.0.1.<em>x</em> and the complete release of Oracle9<em>i</em> (9.0.1) Enterprise Edition, or Oracle Internet Directory 2.1.1.<em>x</em> and the complete release of Oracle8<em>i</em> (8.1.7) Enterprise Edition, then you must first upgrade Oracle Internet Directory to the release 9.2.0.<em>x</em>.<em>x</em> version, and then upgrade as a separate step either Oracle9<em>i</em> Enterprise Edition release 1 (9.0.1) or Oracle8<em>i</em> release 3 (8.1.7) to Oracle9<em>i</em> Enterprise Edition release 2 (9.2.0.<em>x</em>.<em>x</em>).
</p>
<div align="center">
<br /><table summary="This is a layout table to format a tip" title="This is a layout table to format a tip" dir="ltr" border="1" width="80%" frame="hsides" rules="groups" cellpadding="3" cellspacing="0"><tbody>
<tr>
<td align="left" colspan="1" rowspan="1">
<p>
<font face="arial, helvetica, sans-serif">
<strong><strong>See Also</strong>:</strong>
</font>
</p><em>Oracle Internet Directory README</em> for more information on Oracle Internet Directory utilities, and necessary pre-upgrade and post-upgrade tasks. 
</td>
</tr></tbody>
</table><br />
</div>
</div class="sect3">
</div class="sect2"><a id="CACEDFFI" name="CACEDFFI"></a>
<div class="sect2">
<!--
infolevel=all
infotype=general
--><a id="sthref15" name="sthref15"></a>
<h3>
<font face="arial, helvetica, sans-serif" color="#330099">
Oracle Real Application Clusters
</font>
</h3>
<p>Review the following section if you will install Oracle Real Application Clusters.
</p>
<div class="sect3">
<!--
infolevel=all
infotype=general
--><a id="sthref16" name="sthref16"></a>
<h4>
<font face="arial, helvetica, sans-serif" color="#330099">
Restrictions for Installing Real Application Clusters
</font>
</h4>
<p>If you are installing Oracle9<em>i</em> release 2 (9.2.0.1.0) Real Applications Clusters on a cluster that already contains an ORACLE&#095;HOME for a previous release of Real Application Clusters, then you must run the Oracle Universal Installer from the cluster node with the oraInventory installation registry. Doing this ensures that product installation inventories are synchronized on the nodes with information about existing ORACLE&#095;HOME directories.
</p>
</div class="sect3">
<div class="sect3">
<!--
infolevel=all
infotype=general
--><a id="sthref17" name="sthref17"></a>
<h4>
<font face="arial, helvetica, sans-serif" color="#330099">
Additional Preinstallation Requirements for Real Application Clusters
</font>
</h4>
<p>The following requirements are in addition to those documented in the installation guide.
</p>
<ul>
<li type="disc">
<p>The user id (UID) of the oracle user needs to be less than 65536 for Real Application Cluster installs.
</p>
</li>
<li type="disc">
<p>You need to create the directory <code>&#047;var&#047;opt&#047;oracle</code>. This directory path is required for the <code>srvConfig.loc</code> file, which the Installer creates during Real Application Clusters installation and configuration.
</p>
</li>
</ul>
</div class="sect3">
<div class="sect3">
<!--
infolevel=all
infotype=general
--><a id="sthref18" name="sthref18"></a>
<h4>
<font face="arial, helvetica, sans-serif" color="#330099">
Real Application Clusters Custom Installation Requirements
</font>
</h4>
<p>Complete the following tasks if you install Oracle Real Application Clusters:
</p>
<div class="sect4">
<!--
infolevel=all
infotype=general
--><a id="sthref19" name="sthref19"></a>
<h5>
<font face="arial, helvetica, sans-serif" color="#330099">
DRSYS Tablespace and Oracle Enterprise Manager
</font>
</h5>
<p>If you plan to create an Oracle Enterprise Manager repository in an existing database, and you plan to use the DRSYS tablespace for the repository, then ensure that the DRSYS tablespace raw device data file has an additional 50 MB of free space. This is in addition to the 250 MB size documented for this raw device.
</p>
</div class="sect4">
</div class="sect3">
<div class="sect3">
<!--
infolevel=all
infotype=general
--><a id="sthref20" name="sthref20"></a>
<h4>
<font face="arial, helvetica, sans-serif" color="#330099">
Real Application Clusters and Database Upgrade Assistant
</font>
</h4>
<p>If you use Database Upgrade Assistant to upgrade an earlier Oracle database version (the "source" database) to Oracle9<em>i</em> release 2 (9.2.0.1.0) (the "target" database), then the upgraded database will always use the server parameter file SPFILE by default to store <code>init.ora</code> file parameters. If the source database also uses SPFILE (either a cluster filesystem file or a shared raw device), then the upgraded target database also uses the same SPFILE. 
</p>
<p>If the source database does not use an SPFILE, then the target database uses a default server parameter file, <code>spfile.ora</code>, which is located in the <code>&#036;ORACLE&#095;HOME&#047;dbs&#047;</code> directory.
</p>
<p>If your platform does not support a cluster file system, then you must move the SPFILE to a shared raw device, using the following procedure:
</p>
<ol type="1" start="1">
<li>
<p>Create an SPFILE with the following commands:
</p>
<pre>&#036; sqlplus "&#047; as sysdba"
SQL&gt; create pfile&#061;&#039;?&#047;dbs&#047;init<em>dbname</em>.ora&#039; from spfile&#061;&#039;?&#047;dbs&#047;spfile.ora&#039;;
SQL&gt; create spfile&#061;&#039;&#047;dev&#047;oracle&#095;dg&#047;<em>dbname</em>&#095;spfile&#039; frompfile&#061;&#039;?&#047;dbs&#047;init<em>dbname</em>.ora&#039;;
SQL&gt; exit;

</pre>
<p>where <em><code>dbname</code></em> is the name of your cluster database.
</p>
</li>
<li>
<p>Go to the <code>&#036;ORACLE&#095;HOME&#047;dbs</code> directory using the following command:
</p>
<pre>&#036; cd &#036;ORACLE&#095;HOME&#047;dbs

</pre>
</li>
<li>
<p>Create an <code>&#036;ORACLE&#095;HOME&#047;dbs&#047;init</code><em><code>sid</code></em><code>.ora</code> file, where <em><code>sid</code></em> is the system identifier of the instance on the node. The <code>init</code><em><code>sid</code></em><code>.ora</code> file must contain the following line:
</p>
<pre>SPFILE&#061;&#039;&#047;dev&#047;oracle&#095;dg&#047;<em>dbname</em>&#095;spfile&#039;

</pre>
</li>
<li>
<p>Copy the <code>init</code><em><code>sid</code></em><code>.ora</code> file to the remote nodes on which the cluster database has an instance with the following commands:
</p>
<pre>&#036; rcp init<em>sid</em>.ora node<em>x:</em>&#036;ORACLE&#095;HOME&#047;dbs&#047;init<em>sidx</em>.ora

</pre>
<p>where <em><code>sidx</code></em> is the system identifier of the instance on node <em><code>x</code></em>. Repeat the preceding <code>rcp</code> command for each member node of the cluster database.
</p>
</li>
<li>
<p>Restart the cluster database with the following command syntax:
</p>
<pre>&#036; srvctl stop database -d <em>dbname</em>
&#036; srvctl start database -d <em>dbname</em>

</pre>
</li>
</ol>
</div class="sect3">
<div class="sect3">
<!--
infolevel=all
infotype=general
--><a id="sthref21" name="sthref21"></a>
<h4>
<font face="arial, helvetica, sans-serif" color="#330099">
Real Application Clusters and Database Configuration Assistant
</font>
</h4>
<p>The following section provides information on using Database Configuration Assistant (DBCA) to create a Real Application Clusters database.
</p>
</div class="sect3">
<div class="sect3">
<!--
infolevel=all
infotype=general
--><a id="sthref22" name="sthref22"></a>
<h4>
<font face="arial, helvetica, sans-serif" color="#330099">
Placing Datafiles On a Shared Non-OFA Cluster Configuration
</font>
</h4>
<p>If your ORACLE&#095;HOME directory is not on a shared cluster filesystem partition, but you want to place datafiles, controlfiles, redo log files, or other database files on a shared cluster filesystem partition, then invoke DBCA using the following syntax to create the cluster database:
</p>
<pre>&#036; dbca -datafileDestination <em>pathname</em>

</pre>
<p>where <em><code>pathname</code></em> is the location where you want files to be placed. 
</p>
<p>For example, to place datafiles in the path <code>&#047;ora&#047;oradata</code>, give the following command:
</p>
<pre>&#036; dbca -datafileDestination &#047;ora&#047;oradata
</pre>
<div align="center">
<br /><table summary="This is a layout table to format a tip" title="This is a layout table to format a tip" dir="ltr" border="1" width="80%" frame="hsides" rules="groups" cellpadding="3" cellspacing="0"><tbody>
<tr align="left" valign="top">
<td align="left" colspan="1" rowspan="1">
<p>
<font face="arial, helvetica, sans-serif">
<strong>Note:</strong>
</font>
</p>For optimal performance and data security, Oracle Corporation recommends that you configure your database in accordance with the Optimal Flexible Architecture (OFA) standard. For more information on OFA, refer to <em>Oracle9i Administrator&#039;s Reference for UNIX Systems</em>.
</td>