|Oracle8i Release Notes
Release 3 (8.1.7) for Intel UNIX (DG/UX Intel and SCO UnixWare)
These release notes contain important last minute information not included in the documentation library of your Oracle8i for Intel UNIX (DG/UX Intel and SCO UnixWare) Online Documentation CD-ROM.
This document contains the following topics:
The following hardware is required to install Oracle8i release 3 (8.1.7) on Intel Unix systems.
A minimum of 128 MB is required to install Oracle8i products. Oracle8i Client products require 64 MB.
Twice the amount of RAM or at least 400 MB, whichever is greater, is recommended for most systems.
A CD-ROM drive supported by UNIX is required. Oracle uses ISO 9660 format CD-ROM disks with RockRidge extensions.
In addition to the parameters listed in the Oracle8i Installation Guide Release 3 (8.1.7) for Intel UNIX (DG/UX Intel, SCO UnixWare, Solaris Intel), set the STRTHRESH parameter to 0x0. This setting removes the limit on STREAMS resources being used by the operating system kernel.
The JRE shipped with Oracle8i is used by Oracle Java applications such as Oracle Universal Installer and is the only one supported to run with these applications. Customers should not modify this JRE, unless it is done through a patch provided by Oracle Support Services.
This section contains information on Oracle8i documentation.
Additional product README files are located in the product subdirectories in the Oracle home directory or in the
The following websites have the most current information about products included with this release:
Oracle8i release 3 (8.1.7) does not include an SPX protocol adapter for Intel UNIX. Intel UNIX clients cannot connect to an Oracle8i database using the Novell SPX protocol.
In Oracle8i release 3 (8.1.7), the default behavior for the ResultSet::getXXXStream() APIs have been modified to comply with the JDBC specification. They return null values for database null LONG or LONG RAW values. In earlier versions of the JDBC drivers, the default behavior was to return the empty stream for database null values. To restore the previous JDBC default behavior when using the release 8.1.7 drivers, you must use the Java property
jdbc.backward_compatible_to_8.1.6. For example, to cause the release 8.1.7 JDBC drivers to return empty streams from calls to
ResultSet::getXXXStream(), set the following command at the virtual machine:
jdbc.backward_compatible_to_8.1.6 Java property applies to the release 8.1.7 JDBC Thin driver and the OCI driver.
It is efficient to use the single-task architecture to transfer large amounts of data between the user and Oracle8i. To make the single-task import (
impst), export (
expst), and SQL*Loader (
sqlldrst) executables, use the
ins_rdbms.mk make file in the
$ORACLE_HOME/rdbms/lib directory. Enter the following:
This section contains information on installation issues.
If you are using the Hummingbird Exceed X-windows server while installing and using Oracle8i, set the window manager to Native so that Microsoft windows functions as the window manager. See the Exceed documentation for instructions on configuring the window manager.
While Oracle supports the use of Exceed for installing and configuring products, be aware of the following common installations problems with using this X Windows server:
To fix either problem, you must exit the entire X Windows session and start a new session. You cannot fix the problem by opening a new shell and re-running the Installer from the shell.
The Xconfig window appears.
The Font Settings dialog box appears.
The Font Database dialog box appears.
The Add Font Directory dialog box appears.
Oracle Corporation recommends that you install Oracle8i release 3 (8.1.7) into a new Oracle home directory. Do not install Oracle8i release 3 (8.1.7) into an Oracle home directory that already contains Oracle products.
If you must install Oracle8i release 3 (8.1.7) into an Oracle home directory that contains release 8.1.5 or release 8.1.6 products, use the Installer to remove the release 8.1.5 or release 8.1.6 products before beginning the new installation.
Be aware of the following issues when running the Oracle Universal Installer in non-interactive mode.
Oracle no longer provides a character mode installer. However, you can configure the Oracle Universal Installer to perform a non-interactive installation of Oracle products. You can run the Installer in non-interactive mode directly from your system's X-windows console or through an X-terminal or PC X-Windows server on a remote system.
For more information on the non-interactive installation of Oracle products, see the Oracle8i Installation Guide Release 3 (8.1.7) for Intel UNIX (DG/UX Intel, SCO UnixWare, Solaris Intel).
Oracle8i release 3 (8.1.7) client-side libraries are compatible with release 2 (8.1.6) client-side libraries if the libraries are used with Oracle applications and tools. The libraries are not compatible when used by a database or listener. This means that applications and tools running in the same Oracle home directory as these 8.1.6 client-side libraries will not encounter runtime errors if the libraries are upgraded to 8.1.7 during an installation. If you upgrade the 8.1.6 client-side libraries in the same Oracle home directory as an Oracle8i release 2 (8.1.6) database or listener, and the database or listener is not also upgraded to release 8.1.7, the release 8.1.6 versions of the database or listener do not work. To keep the older versions of the database or listener intact, you must install Oracle8i release 3 (8.1.7) in a new Oracle home directory.
Review the following known upgrade issues before upgrading Oracle8i.
If you attempt to upgrade an Oracle8i release 2 (8.1.6) database to a release 3 (8.1.7) database in the same Oracle home directory, you will receive ignorable installation runtime errors that occur when the release 8.1.6 software is de-installed.
Oracle Universal Installer upgrades software by first de-installing the old software, then installing the new software. The errors that occur during an upgrade in the same Oracle home directory appear as relinking errors during the RDBMS and Net8 Server installation. Because these errors are relinking errors that occur during the de-installation of the release 8.1.6 software and because the affected files are replaced and relinked again when the release 8.1.7 software is installed, you can safely ignore these errors.
While upgrading the software, Oracle Universal Installer displays error dialog boxes with the following messages:
Error in invoking target ioracle of make fileORACLE_HOME
Error in invoking target install of makefileORACLE_HOME
Click [Ignore] on each of these dialog boxes to allow the installation to continue. To avoid these errors, install the release 3 (8.1.7) software into a new Oracle home directory, then perform the database upgrade.
Before performing either a manual database upgrade or an automated database upgrade using Oracle Data Migration Assistant, you must first set the _SYSTEM_TRIG_ENABLED parameter in the initialization parameter file to FALSE. After upgrading the database, you must either remove the _SYSTEM_TRIG_ENABLED parameter from the initialization parameter file or set it to TRUE before attempting to upgrade any other products, for example Oracle JServer. Refer to the Oracle8i Migration guide for more information on upgrade and migration.
Review the following known problems, restrictions, and workarounds before using the Oracle Universal Installer:
This problem does not occur if you install release 8.1.6 or release 8.1.7 after installing release 8.1.5.
In X-windows environments, you can launch the Oracle Universal Installer by selecting the
runInstaller script in the File Manager window. You can also launch the Oracle Universal Installer by executing the
runInstaller script from a shell.
If you launch the Oracle Universal Installer by selecting the
runInstaller script in the File Manager window, you cannot eject the CD until you terminate the installation session. However, you must eject the CD to continue with multi-CD installations. To successfully install products that require you to insert multiple CDs, you must execute the
runInstaller script from a shell.
In Oracle8i release 3 (8.1.7) you must set the COBDIR environment variable to a valid path before running the Oracle Universal Installer. If you do not set this environment variable before starting the installation session, the Pro*COBOL release 8.1.7 precompiler is not available for selection during installation.
You cannot de-install Oracle JServer separately from other products installed with Oracle8i release 3 (8.1.7).
De-installing Oracle JServer causes Oracle Universal Installer to remove Oracle8i and other products dependent on Oracle JServer from your system.
This section describes issues about system management products.
In Oracle8i release 3 (8.1.7), you can install the Oracle Intelligent Agent extensions (Oracle Applications Extensions, Oracle HTTP Server Extensions, Oracle EBusiness Management Tool Extensions, and so on) separately.
This means that during installation, you can select the Oracle Intelligent Agent and separately select any of the Oracle Intelligent Agent extensions. Oracle Data Gatherer is installed as part of the basic Oracle Intelligent Agent.
You can grant the OEM _MONITOR database role to any database user as a "preferred credential" when registering advanced (database) events available with the Oracle Enterprise Manager Diagnostics Pack.
This role is defined in the
$ORACLE_HOME/rdbms/admin/catsnmp.sql script which is called by the catalog scripts at database creation time. In addition to the OEM_MONITOR role, the database user requires quota on their default tablespace within the monitored database, to have some of the advanced events evaluated. If you fail to do this, an insufficient privilege message appears.
If you reinstall Oracle8i Server into an Oracle home directory where Oracle8i Server release 3 (8.1.7) is already installed, you must also reinstall any product options, such as Oracle Partitioning, that were enabled before you began the reinstallation.
Several products included with Oracle8i release 3 (8.1.7) are now directory-enabled and can take advantage of an LDAP version 3 directory server such as Oracle Internet Directory. However, Oracle Internet Directory Server is not released with Oracle8i release 3 (8.1.7) for Intel UNIX (DG/UX Intel and SCO Unixware).
If you use the Custom installation type of Oracle8i Enterprise Edition to install Oracle Advanced Security into an existing Oracle home directory that already contains Oracle8i Enterprise Edition, you must install Oracle Advanced Security separately from any other product options, or the installation fails. To use the Radius adapter configured for CHAP (challenge-response) mode, you must relink the
oracle executable and the Oracle
sqlplus clients with JDK release 1.1.7.
When you use Oracle Database Configuration Assistant to create a custom database that includes Oracle JServer, it can take over an hour to finish loading Oracle JServer into the database depending on your system's hardware configuration.
In a Typical, silent installation of Oracle8i release 3 (8.1.7), Net8 Configuration Assistant does not configure an IIOP listening end point to provide access to Oracle JServer. After installation, start the Net8 Configuration Assistant from the command line and configure an IIOP end point for the listener called LISTENER. For more information, see the Net8 Administrator's Guide.
The Heterogeneous Services Agent Control Utility (
agtctl) incorrectly reports its version as 22.214.171.124.0. The correct version of this utility is 126.96.36.199.0.
This section contains the following topics:
When creating a database for use with Oracle Parallel Server, you must set the SYSTEM tablespace size to 274 MB. If you are creating a custom database with the Oracle Database Configuration Assistant, you must change the SYSTEM tablespace size from the default of 260 MB to 274 MB before creating the database. In addition, the size of the raw device that you create for the SYSTEM tablespace must also be at least 275 MB. This requirement supersedes the corresponding file size requirement listed in the Oracle8i Parallel Server Setup and Configuration Guide. For more information on creating raw devices on Intel UNIX systems, see the Oracle8i Administrator's Reference.
Be aware of the following differences between Oracle Parallel Server Manager and Oracle Parallel Server Management:
When running in Cluster mode and creating new listeners, the Net8 Configuration Assistant sometimes fails to start the newly created listeners on all nodes of the cluster. To work around this problem, log in to each node and enter the command:
Copyright © 2001 Oracle Corporation.
All Rights Reserved.