|Oracle8i Release Notes
Release 3 (8.1.7) 64 Bit for SGI IRIX
Part No. A90269-01
These release notes contain important information not included in the documentation on the Oracle8i for SGI IRIX CD-ROM.
This document contains the following topics:
The following hardware is required to install Oracle8i release 3 (8.1.7) on SGI IRIX systems.
A minimum of 256 MB is required to install Oracle8i products. Oracle8i Client products require 64 MB.
For most systems, twice the amount of RAM or at least 400 MB, whichever is greater.
A CD-ROM drive supported by SGI IRIX is required. Oracle uses ISO 9660 format CD-ROM disks with RockRidge extensions.
This section contains these topics:
Additional product README files are located in the product subdirectories in the $ORACLE_HOME directory or in the
The Oracle8i Administrator's Reference Release 3 (8.1.7) 64 Bit for SGI IRIX, and the Oracle8i Installation Guide Release 3 (8.1.7) 64 Bit for SGI IRIX are available online on the Oracle8i software CD-ROM. To access the documentation, use a Web browser to open the
index.htm file at the top level of the Oracle8i CD-ROM. This file contains links to product and SGI IRIX-specific documentation.
The following Web-sites have the most current information about products included with this release:
The JRE shipped with Oracle8i is used by Oracle Java applications such as Oracle Universal Installer and is the JRE one supported to run with these applications. Only modify this JRE with a patch provided by Oracle Support Services.
The Installer creates the
oraInventory directory the first time it is run. The inventory can contain multiple versions of the JRE, each of which can be used by one or more products or releases. The
oraInventory directory keeps an inventory of products installed on your system as well as other installation information. The location of the
oraInventory directory is defined in the
Products in an Oracle home directory access the JRE through a symbolic link in the
$ORACLE_HOME/JRE directory to the actual location of a JRE within the inventory. Only modify the symbolic link using a patch provided by Oracle Support Services.
Oracle8i release 3 (8.1.7) 64 Bit for SGI IRIX does not support the post-wait driver.
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 these topics:
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 that there is a bug in the way Exceed handles screen coordinates. The Installer window and related Installer dialog boxes or configuration assistants might not display correctly when run through the Exceed server. These display problems might include:
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.
To correct problems with hidden dialog box fields, do the following:
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.
If you install another product category, such as Oracle8i Management Infrastructure, after the successful installation of Oracle8i Server into the same Oracle home directory, Oracle Universal Installer will delete the content of the root.sh script during the course of the installation. Before beginning the installation, enter the following command to backup the root.sh script:
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) 64 Bit for SGI IRIX.
Oracle8i release 3 (8.1.7) client-side libraries are compatible with 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 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 file
Error in invoking target install of makefile
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 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.
If you are installing Oracle8i release 3 (8.1.7) directly from the installation media, you must switch between CD 1 and CD 2 during the installation session to complete a full installation. To avoid having to switch between CDs, copy the contents of each CD to the hard drive and run the Installer from the new location. Copy the contents of each CD in the directory structure as follows:
If the contents of each CD are copied into this structure on the hard drive, Oracle Universal Installer automatically finds the contents of each CD and does not prompt for the location of either CD during the course of installation.
If you run the Installer while the current working directory is in the CD-ROM, perform the following steps to mount the next CD-ROM:
To successfully install products that require you to insert multiple CDs, you must execute the
runInstaller script from a shell.
In X-windows environments, it is possible to launch the Oracle Universal Installer by selecting the
runInstaller script in the File Manager window. However, if you do, you cannot eject the CD until you terminate the installation session.
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.
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 contains these topics:
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.
If you reinstall Oracle8i Server into an Oracle home directory where Oracle8i Server release 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. Purchase of Oracle8i release 3 (8.1.7) includes a restricted-use version of Oracle Internet Directory release 2.1.1 for SGI IRIX that may only be used in conjunction with the Oracle directory-enabled components and products such as Net8, Oracle Advanced Security, Oracle8i, and all future directory-enabled Oracle products.
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, Oracle8i release 3 (8.1.7) silent installation, 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 184.108.40.206.0. The correct version of this utility is 220.127.116.11.0.
Copyright © 2001 Oracle Corporation.
All Rights Reserved.