readme_rdbms.htm

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

tablespace to <tt>XDB</tt> tablespace and change <tt>xml</tt> to <tt>xdb</tt>
in the datafile names. These appear in Tables 2-1, 2-2, 2-3, and 2-4, and
in Example 2-1. For example, the datafile name <tt>db_name_raw_xml_50m</tt>
should be <tt>db_name_raw_xdb_50m</tt> and the datafile symbolic link name
<tt>db_name_xml</tt> should be <tt>db_name_xdb</tt>.
<br><a NAME="565665"></a><!--TOC=h2-"565665"-->
<h3 CLASS="H2">
<font face="Arial, Helvetica, sans-serif"><font color="#330099">3.4 Real
Application Clusters Deinstallation</font></font></h3>
<!--/TOC=h2--><a NAME="565668"></a>

<p CLASS="BP">To perform deinstallation in the Real Application Clusters
environment, please do not choose the deinstall products option from the
Welcome page in OUI.
<br><a NAME="565671"></a>

<p CLASS="BP">Please follow the following steps to perform Real Application
Clusters deinstallation.
<ol CLASS="LN1" TYPE="1">
<li CLASS="LN1" TYPE="1" VALUE="1">
<a NAME="565673"></a>1. Choose the nodes that your oracle home has been
installed on in the node selection page in OUI.</li>

<li CLASS="LN1" TYPE="1" VALUE="2">
<a NAME="565675"></a>2. Click on Installed Products button in the File
Locations page in OUI.</li>

<li CLASS="LN1" TYPE="1" VALUE="3">
<a NAME="565676"></a>3. Choose the Oracle home you want to deinstall and
click the Remove button.</li>

<br>&nbsp;
<p>&nbsp;</ol>
<a NAME="561192"></a><!--TOC=h1-"561192"-->
<h2 CLASS="H1">
<font face="Arial, Helvetica, sans-serif"><font color="#330099">4 COMPATIBILITY</font></font></h2>
<!--/TOC=h1--><a NAME="527452"></a>

<p CLASS="BP">This section contains recommendations on upgrading to this
release, and on preparing for future changes (for example, to comply with
future SQL ANSI standards). If you follow these recommendations, upgrading
to newer releases of Oracle will be simplified.
<br><a NAME="506637"></a><!--TOC=h2-"506637"-->
<h3 CLASS="H2">
<font face="Arial, Helvetica, sans-serif"><font color="#330099">4.1 Nesting
of Quotation Marks in Initialization Parameter Values</font></font></h3>
<!--/TOC=h2--><a NAME="560494"></a>

<p CLASS="BP">Starting with Oracle9<i>i</i> release 9.2, the nesting of
quotation marks using the backslash (\) escape character is no longer supported.
This may affect how Oracle interprets parameter values in your initialization
parameter file or server parameter file.
<br><a NAME="560500"></a>

<p CLASS="BP">For example, assume you have the following initialization
parameter in your parameter file:
<pre CLASS="CE"><a NAME="560503"></a>CONTROL_FILES = "ctlfile\'1.ora"
<a NAME="560529"></a></pre>
<a NAME="560505"></a>

<p CLASS="BP">In releases prior to release 9.2, the filename would be interpreted
as <tt>ctlfile'1.ora</tt>. Starting with release 9.2, the filename in the
previous example would be interpreted as <tt>ctlfile\'1.ora</tt>.
<br><a NAME="560509"></a>

<p CLASS="BP">Oracle Corporation highly recommends modifying your parameter
files to remove such references. Refer to the <i>Oracle9</i>i<i> Database
Reference</i> for other methods of nesting quotation marks in initialization
parameter values.
<br><a NAME="560492"></a><!--TOC=h2-"560492"-->
<h3 CLASS="H2">
<font face="Arial, Helvetica, sans-serif"><font color="#330099">4.2 CONNECT
INTERNAL Desupport</font></font></h3>
<!--/TOC=h2--><a NAME="477926"></a>

<p CLASS="BP"><tt>CONNECT INTERNAL</tt> has been desupported in this release.
Users making DBA-privileged connections to the database must use one of
the following syntaxes:
<pre CLASS="CE"><a NAME="507028"></a>CONNECT / AS SYSDBA&nbsp; or CONNECT &lt;username/password> AS SYSDBA</pre>
<a NAME="507032"></a>

<p CLASS="BP">Users who have relied on CONNECT INTERNAL in connect strings
must replace CONNECT INTERNAL with one of the above commands. See the <i>Oracle9</i>i
<i>Database Administrator's Guide</i> for further details.
<br><a NAME="478078"></a><!--TOC=h2-"478078"-->
<h3 CLASS="H2">
<font face="Arial, Helvetica, sans-serif"><font color="#330099">4.3 SQL.BSQ</font></font></h3>
<!--/TOC=h2--><a NAME="478082"></a>

<p CLASS="BP">Oracle recommends not changing <tt>SQL.bsq</tt> before installation
because some modifications may jeopardize customer supportability.
<br><a NAME="521031"></a><!--TOC=h2-"521031"-->
<h3 CLASS="H2">
<font face="Arial, Helvetica, sans-serif"><font color="#330099">4.4 LU6.2
Protocol</font></font></h3>
<!--/TOC=h2--><a NAME="521034"></a>

<p CLASS="BP">LU6.2 protocol is not supported for Oracle9<i>i</i>. Migrate
or upgrade to TCP/IP based protocols.
<br><a NAME="550727"></a><!--TOC=h2-"550727"-->
<h3 CLASS="H2">
<font face="Arial, Helvetica, sans-serif"><font color="#330099">4.5 Interoperability
with the 8.1.7 JDBC Thin Driver</font></font></h3>
<!--/TOC=h2--><a NAME="550730"></a>

<p CLASS="BP">There is a known problem with connecting from a client using
the 8.1.7.0 or 8.1.7.1 JDBC Thin driver to the 9.0.1 Oracle database. The
problem causes the Oracle server to return ORA-600 errors during operation.
A JDBC patch is available for download from:
<pre CLASS="CE"><a NAME="551367"></a><a href="http://metalink.oracle.com/metalink/plsql/m12_documents.showNOT?p_id=147731.1">http://metalink.oracle.com/metalink/plsql/m12_documents.showNOT?p_id=147731.1</a>
<a NAME="562102"></a></pre>
<a NAME="551368"></a>

<p CLASS="BP">The patch must be applied to the 8.1.7.0 and 8.1.7.1 JDBC
drivers to ensure proper operation.
<br><a NAME="563850"></a><!--TOC=h2-"563850"-->
<h3 CLASS="H2">
<font face="Arial, Helvetica, sans-serif"><font color="#330099">4.6 JDBC
Updates</font></font></h3>
<!--/TOC=h2--><a NAME="563853"></a>

<p CLASS="BP">For up-to-date information about database URLs and connection
cache timeouts in the JDBC Developer's Guide and Reference, please see
<pre CLASS="CE"><a NAME="563852"></a><a href="http://otn.oracle.com/tech/java/sqlj_jdbc/content.html">http://otn.oracle.com/tech/java/sqlj_jdbc/content.html</a>
<a NAME="565552"></a></pre>
<a NAME="565744"></a><!--TOC=h2-"565744"-->
<h3 CLASS="H2">
<font face="Arial, Helvetica, sans-serif"><font color="#330099">4.7 OJMS
Queues and Upgrade</font></font></h3>
<!--/TOC=h2--><a NAME="565751"></a>

<p CLASS="BP">If an upgrade is performed to RDBMS 9.2, from an earlier
database version in which OJMS queues or topics already exist, then the
OJMS type bodies that contain PL/SQL member functions may become invalid
and unusable. The OJMS PL/SQL types and the AQ queues and topics that were
created using these types however remain usable and no data is lost or
corrupted. The OJMS Java client library functionality is also not affected.
This problem is documented in Bug 2365565 and a patch can be downloaded
from Metalink.
<br><a NAME="565746"></a><!--TOC=h2-"565746"-->
<h3 CLASS="H2">
<font face="Arial, Helvetica, sans-serif"><font color="#330099">4.8 Configuring
ODM for Upgraded Database Requires XML DB</font></font></h3>
<!--/TOC=h2--><a NAME="565603"></a>

<p CLASS="BP">When upgrading an Oracle9<i>i</i> release 9.0.1 database
that does not have ODM installed, DBCA will not permit configuring ODM
in the upgraded database if XML DB is not already configured. The ODM option
is grayed out and, therefore, cannot be selected.
<br><a NAME="565607"></a>
<h5 CLASS="SH3">
<font face="Arial, Helvetica, sans-serif">Workaround</font></h5>
<a NAME="565622"></a>

<p CLASS="BP">ODM requires that the XML database option be either configured
or be selected to be configured. If you select the Oracle XML DB feature
and then select ODM, you will be able to configure ODM.
<br><a NAME="565555"></a><!--TOC=h1-"565555"-->
<h2 CLASS="H1">
<font face="Arial, Helvetica, sans-serif"><font color="#330099">5 ORACLE9<i>i</i>
SAMPLE SCHEMAS</font></font></h2>
<!--/TOC=h1--><a NAME="565556"></a>

<p CLASS="BP">The seed database now contains a set of sample schemas (in
addition to the traditional <tt>SCOTT</tt> schema), which are installed
by default when you install Oracle. These sample schemas are used in many
of the examples that appear in the documentation and training materials
for Oracle9<i>i</i>. These new schemas are documented in the book <i>Oracle9</i>i
<i>Sample Schemas</i>, which is on the documentation CD.
<br><a NAME="478226"></a><!--TOC=h1-"478226"-->
<h2 CLASS="H1">
<font face="Arial, Helvetica, sans-serif"><font color="#330099">6 RESTRICTIONS
ON PL/SQL LANGUAGE</font></font></h2>
<!--/TOC=h1--><a NAME="560552"></a><!--TOC=h2-"560552"-->
<h3 CLASS="H2">
<font face="Arial, Helvetica, sans-serif"><font color="#330099">6.1 Inter-version
RPC and Default Arguments</font></font></h3>
<!--/TOC=h2--><a NAME="478282"></a>

<p CLASS="BP">Calls from one server to functions and procedures on a second
server running a different version of Oracle may have problems when using
defaulted argument values if one of the servers is a 8.0.X release. Symptoms
may vary depending upon the source code involved. The errors <tt>PLS-801[1411]</tt>
and <tt>PLS-801[1407]</tt> are quite likely, but other symptoms, including
silently wrong results, are possible. The suggested workaround is to provide
an explicit value for each argument on any call through a database link
if it is possible that the sending and receiving systems are running different
versions of Oracle.
<br><a NAME="516050"></a><!--TOC=h2-"516050"-->
<h3 CLASS="H2">
<font face="Arial, Helvetica, sans-serif"><font color="#330099">6.2 DATETIME</font></font></h3>
<!--/TOC=h2--><a NAME="516053"></a>

<p CLASS="BP">For functions implemented in PL/SQL, the following checks
are not <b>completely</b> enforced for argument or return types: the datetime
and interval day to seconds fractional seconds precision check, and the
interval leading field precision check. This affects the precision part
of the datetime/interval data when SQL calls a PL/SQL function.
<br><a NAME="560065"></a><!--TOC=h2-"560065"-->
<h3 CLASS="H2">
<font face="Arial, Helvetica, sans-serif"><font color="#330099">6.3 External
Procedures: Loading DLLs through PL/SQL Libraries</font></font></h3>
<!--/TOC=h2--><a NAME="560072"></a>

<p CLASS="BP">In Oracle9<i>i</i> release 2, <tt>EXTPROC</tt>, by default,
will only load DLLs that are in the <tt>$ORACLE_HOME/bin</tt> or <tt>$ORACLE_HOME/lib</tt>
directory. Also, only local sessions, that is, Oracle client process that
are running on the same machine, are allowed to connect to <tt>EXTPROC</tt>.
<br><a NAME="560078"></a>

<p CLASS="BP">To load DLLs from other directories, the environment variable
<tt>EXTPROC_DLLS</tt> should be set. The value for this environment variable
is a colon (:) separated list of DLL names qualified with the complete
path.
<br><a NAME="560106"></a>

<p CLASS="BP">For example:
<pre CLASS="CE"><a NAME="560082"></a>EXTPROC_DLLS=/private1/home/scott/dll/myDll.so:/private1/home/scott/dll/newDll.so
<a NAME="560111"></a></pre>
<a NAME="560085"></a>

<p CLASS="BP">The preferred method to set this environment variable is
through the <tt>ENVS</tt> parameter in the <tt>listener.ora</tt> file.
Please refer to the Oracle Net manual and the <i>Oracle9</i>i <i>Application
Developer's Guide - Fundamentals</i> for more information on the <tt>EXTPROC</tt>
feature.
<br><a NAME="521179"></a><!--TOC=h1-"521179"-->
<h2 CLASS="H1">
<font face="Arial, Helvetica, sans-serif"><font color="#330099">7 UTILITIES</font></font></h2>
<!--/TOC=h1--><a NAME="522027"></a><!--TOC=h2-"522027"-->
<h3 CLASS="H2">
<font face="Arial, Helvetica, sans-serif"><font color="#330099">7.1 SQL
Loader</font></font></h3>
<!--/TOC=h2--><a NAME="505982"></a><!--TOC=h3-"505982"-->
<h4 CLASS="H3">
<font face="Arial, Helvetica, sans-serif"><font color="#330099">7.1.1 BUFFERS
Keyword</font></font></h4>
<!--/TOC=h3--><a NAME="505983"></a>

<p CLASS="BP">The <tt>BUFFERS</tt> keyword is no longer supported for input
file processing.
<br><a NAME="505448"></a><!--TOC=h3-"505448"-->
<h4 CLASS="H3">
<font face="Arial, Helvetica, sans-serif"><font color="#330099">7.1.2 Size
of CHAR or RAW Fields in Direct Path Loads When No Length is Specified</font></font></h4>
<!--/TOC=h3--><a NAME="505449"></a>

<p CLASS="BP">For direct path loads in previous versions of SQL*Loader,
the size of a <tt>CHAR</tt> or <tt>RAW</tt> field specified with no length
in the data file was assumed to be the same size as the column in the table.
As of Oracle9<i>i</i>, direct path loads operate in the same way as conventional
path loads and assume a length of 255.
<br><a NAME="534310"></a><!--TOC=h3-"534310"-->
<h4 CLASS="H3">
<font face="Arial, Helvetica, sans-serif"><font color="#330099">7.1.3 SQL*Loader
and Multi-Level Collections</font></font></h4>
<!--/TOC=h3--><a NAME="534311"></a>

<p CLASS="BP">SQL*Loader does not support multi-level collections in Oracle9<i>i</i>.
One possible workaround is to load each table individually as a single-table
load, and supply your own correlation information; for example, supply
the SIDs. If you do this, you must be careful about rows in the parent
table without corresponding child rows in the child nested tables, and
orphan rows in the child nested tables without parent rows. Currently,
this method works only for direct path loads; it does not work in conventional
path.
<br><a NAME="526039"></a><!--TOC=h3-"526039"-->
<h4 CLASS="H3">
<font face="Arial, Helvetica, sans-serif"><font color="#330099">7.1.4 SQL*Loader
Handling of Byte-Order Mark and SKIP Parameter</font></font></h4>
<!--/TOC=h3--><a NAME="526040"></a>

<p CLASS="BP">If the character set of the datafile is a unicode character
set (<tt>UTF-16</tt> or <tt>UTF-8</tt>) and it contains a byte-order mark
(BOM) in the first few bytes of the file, then use of the command line
parameter <tt>SKIP</tt> is not supported. If <tt>SKIP</tt> is specified,
the byte-order mark will not be read and interpreted as a byte-order mark.
<br><a NAME="561025"></a><!--TOC=h3-"561025"-->
<h4 CLASS="H3">
<font face="Arial, Helvetica, sans-serif"><font color="#330099">7.1.5 Using
SQL*Loader or OCI for Data Loading</font></font></h4>
<!--/TOC=h3--><a NAME="561046"></a>

<p CLASS="BP">If you use SQL*Loader (with conventional path) or OCI to
load data into varrays or primary-key-based-refs (<tt>pkrefs</tt>) and
the data being loaded is in a different character set from the database
character set, then unexpected problems may occur. The problems include:
<ul CLASS="LB1">
<li CLASS="LB1" TYPE="DISC">
<a NAME="561031"></a>rows getting rejected for a field too large for the
database column when the field is not actually too large</li>

<li CLASS="LB1" TYPE="DISC">
<a NAME="561033"></a>the load being aborted with no rows loaded versus
just that row getting rejected if a field is actually too large for the
database column</li>

<li CLASS="LB1" TYPE="DISC">
<a NAME="561036"></a>rows which are reported as loaded correctly but then
the <tt>pkref</tt> columns show up as blank when selected with SQL*Plus</li>

<br>&nbsp;
<p>&nbsp;</ul>
<a NAME="561039"></a>

<p CLASS="BP">To avoid these problems, set the client character set (using
the environment variable <tt>NLS_LANG</tt>) to the database character set
before loading the data.
<br><a NAME="561042"></a>