Oracle9i Release Notes Release 1 (9.0.1.1) for Sun SPARC Solaris (64-Bit) Part Number A95133-01 |
|
Oracle is a registered trademark, and Oracle8i, Oracle9i, Oracle Names and Oracle Transparent Gateway are trademarks or registered trademarks of Oracle Corporation. Other names may be trademarks of their respective owners.
Copyright © 2001, Oracle Corporation.
All Rights Reserved.
Release 1 (9.0.1.1) for Sun SPARC Solaris (64-Bit)
August 2001
Part No. A95133-01
These release notes contain system requirements, kernel parameters, and last-minute information not included in the Oracle9i documentation library on the Online Documentation CD-ROM.
This document contains the following topics:
Release 9.0.1.1 is the first version of Oracle9i for Sun SPARC Solaris (64-Bit). Oracle Corporation has introduced many improvements since the initial 9.0.1 release. A list of these improvements can be found by opening the index.htm file at the root level of the Disk 1 CD-ROM.
To determine if you are running Solaris in 64-bit mode, enter the following command:
isainfo -kv
Meet the requirements listed in this section before installing Oracle9i.
The requirements in this release note are current as of the release date for Oracle9i. For the most current information, refer to the online release notes which are located at the following site:
http://docs.oracle.com
If you need assistance with navigating the Oracle documentation site, refer to the following site:
http://docs.oracle.com/instructions.html
Refer also to the Certify Web Page on OracleMetaLink, which provides certified configuration information for Oracle and non-Oracle products. Use the following procedure to access Certify:
http://metalink.oracle.com
Hardware and Software Requirements
The following requirements must be met in order to perform a typical Oracle9i software installation and to create a simple prototype database.
$ /usr/sbin/prtconf | grep "Memory size"
$ /usr/sbin/swap -l
and divide the value in the BLOCKS column by two.
/tmp
directory. If 400 MB or more is not available in /tmp
, you can create a tmp
directory in another file system, then set the environment variables TMP (used by Oracle) and TMPDIR (used by operating system programs like the linker "ld" and library archiver "ar") to point to this location. For example:
Bourne (sh) / Korn (ksh) Shell
$ mkdir /u03/tmp $ TMP=/u03/tmp ; export TMP $ TMPDIR=/u03/tmp ; export TMPDIR
C (csh) shell
% mkdir /u03/tmp % setenv TMP /u03/tmp % setenv TMPDIR /u03/tmp
$
uname-a
To determine which operating system patches are installed, enter the following command:
$ showrev -p
pkginfo -i package name
For example, to determine if the SUNWarc package is installed, type:
pkginfo -i SUNWarc
The following table lists the operating system software requirements:
Oracle9i uses UNIX resources such as shared memory, swap space, and semaphores extensively for interprocess communication. If your kernel parameter settings are insufficient for Oracle9i, you will experience problems during installation and instance startup. The greater the amount of data you can store in memory, the faster your database will operate. In addition, by maintaining data in memory, the UNIX kernel reduces disk I/O activity.
Use a text editor such as vi to change kernel parameter settings in the /etc/system
file after making a backup copy. If you have previously changed your kernel for another program to levels equal to or higher than the levels Oracle9i requires, do not change the settings. If they are too low, change them to levels at least as high as those in the table. If you change the settings, then save the /etc/system
file and restart the system. Refer to the following table to determine if your system shared memory and semaphore kernel parameters are set high enough for Oracle9i.
Use the ipcs
command to obtain a list of the system's current shared memory and semaphore segments, and their identification number and owner.
The parameters in the following table are the minimum values required to run Oracle9i with a single database instance.
Additional product README
files are located in their respective product directories under the $ORACLE_HOME
directory and in the $ORACLE_HOME/relnotes
directory.
This section contains these topics:
During installation of Oracle9i release 9.0.1, you will be prompted to insert additional CD-ROMs from the set that make up Oracle9i release 9.0.1. After inserting the requested disk, change the path in the Disk Location dialog to reflect the root directory of the newly mounted CD-ROM.
For example, when you insert Disk 3 with a directory path of /cdrom/orcl901_3
, change the path in the Disk Location dialog to /cdrom/orcl901_3
.
In an X Window environment, it is possible to launch Oracle Universal Installer by running the runInstaller
script from a shell or by clicking on the script in the File Manager window. Oracle Corporation recommends that you do not launch the script by clicking on the script from the File Manager window since you will not be able to eject a software CD-ROM until you end the installation session. The Oracle9i installation uses multiple CD-ROMs, and it is necessary to insert and eject more than one CD-ROM.
ORA-00604: error occurred at recursive SQL level 1
For installation with a response file, the path to the response file must be the full path on the machine. The Oracle Universal Installer will not properly handle relative paths.
This section contains these topics:
If you are upgrading from an Oracle8i release 8.1.7 Enterprise Edition with Oracle Internet Directory, then you must first upgrade Oracle Internet Directory to release 3.0.1 before upgrading to Oracle9i release 9.0.1 Enterprise Edition.
Oracle9i release 9.0.1 supports upgrades for releases of Oracle Internet Directory release 2.1.1.x.0 to Oracle Internet Directory release 3.0.1.
When performing an Oracle Internet Directory installation the Database Configuration Assistant opens an alert window and shows the passwords for the SYS and SYSTEM database roles. Do not change these passwords. Click OK.
When performing a custom Oracle Internet Directory installation, do not change the global database name or the Oracle SID.
After you install all required patches, configure the file olap.key
with the following command:
$ORACLE_HOME/olap/admin/regctrl /infile olap.cfg
For information about installation errors, refer to the OLAP installation log, which is at the following location:
$ORACLE_HOME/install/olap.log
The Oracle9i Database CD Pack includes an "Oracle9i Personalization and Oracle9i Data Mining" CD. Of these two components, Oracle Data Mining is an option to Oracle9i Enterprise Edition. However, Oracle Personalization is a feature of Oracle9i Application Server. The Oracle9i database does not include a license for Oracle Personalization.
The following pre-installation instructions are in addition to the procedure described in the Solaris section under "Oracle Real Application Clusters" in Chapter 2, Pre-Installation, Oracle9i Installation Guide, Release 9.0.1 for UNIX Systems. This is not change to Oracle9i Real Application Clusters Installation and Configuration.
Add the following step after the section that discusses installing the ORCLudlm package from the opspatch directory on the CD. To perform this step, you must be using UDLM version 3.3.4.3 or greater.
You must create a file to redirect memory access to allow the Process Global Area (PGA) to increase in size beyond 100 MB. You must also create this file if Oracle displays the following error:
ORA-04030: out of process memory when trying to allocate n bytes
Where n is the number of bytes Oracle was attempting to allocate.
To perform this step, become root user and on all nodes in the cluster create the following file:
/opt/SUNWcluster/lib/udlm_shmem_addr_file.txt
The file must contain the following entry:
0x12000000
The attach address that this entry refers to is the address for a memory segment associated with the Solaris clusterware. If your system requires more PGA memory than this entry provides, increase the value of the entry in the file.
Re-start the clusterware on all the nodes in the cluster after you create this file.
In Oracle9i Installation Guide for UNIX Systems, "Additional Steps to Perform as the root user for Installing Real Application Clusters on HP or Solaris" in Chapter 2, you are referred to a file in the opspatch
directory that contains installation instructions for installing a required patch for Real Application Clusters. The name of that file is README.udlm
.
Oracle Real Applications Clusters Guard is not supported on Sun Cluster File System.
If Oracle Real Applications Clusters Guard packs are running, and both the nodes of the cluster simultaneously fail, or if at any time all the nodes are stopped without first stopping the packs with the pfsctl
command, then Oracle Real Application Clusters Guard packs will start automatically when the nodes are subsequently booted.
To stop the Oracle Real Application Clusters Guard packs from restarting automatically, use the following commands as root:
$ cd $ORACLE_HOME/pfs/bin $ pfsctl PFSCTL>pfshalt
In the HTML versions of the Transparent Gateways administrator's guides, the hyperlinks to generic Oracle documentation are not active. To access the generic documentation, use the Oracle9i release 1 (9.0.1) generic documentation CD-ROM.
When you use Oracle Database Configuration Assistant to create a custom database that includes Oracle JServer, it can take over an hour to load Oracle JServer into the database. The amount of time depends on your system's hardware configuration.
If you select a multibyte character set or UTF as the national character set in Oracle9i release 9.0.1, then you must recreate the demo schema and database installation.
For more information on creating schemas, schema dependencies and requirements, refer to the readme.txt
file in the $ORACLE_HOME/demo/schema
directory.
In Oracle9i release 9.0.1, 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 Oracle8i are no longer supported.
To migrate existing NCHAR, NVARCHAR, and NCLOB columns, export and import NCHAR columns, do the following:
Oracle9i release 9.0.1 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.
Oracle9i release 9.0.1 supports the Unicode database character sets AL32UTF8 and UTF8. These database character sets include the Unicode enhancements based on the Unicode standard 3.0.
To migrate the existing AL24UTFFSS database, upgrade your database character set to UTF8 before upgrading to Oracle9i. Oracle Corporation recommends that you use the Character Set Scanner for data analysis before attempting to migrate your existing database character set.
Set the LD_LIBRARY_PATH variable to include the $ORACLE_HOME/lib
directory before running the Character Set Scanner (csscan) from the $ORACLE_HOME
directory. If you do not correctly set the LD_LIBRARY_PATH variable, then the csscan utility will fail.
The extproc binary installed in the $ORACLE_HOME/bin
directory is a 64-bit binary. A 32-bit version of the extproc binary, extproc32
, is also installed in the $ORACLE_HOME/bin
directory.
To use 32-bit external subprograms, change the PROGRAM
value for the entry used for extproc in the listener.ora
file as follows:
PROGRAM
entry to extproc32:
(PROGRAM=extproc32)
LD_LIBRARY_PATH
environment variable to point to the $ORACLE_HOME/lib32
directory.
For more information on Calling External Subprograms from PL/SQL (extproc), refer to the Oracle9i Application Developer's Guide - Fundamentals.
See Also:
The following products are not supported for Oracle9i Release 1 (9.0.1.1) for Sun SPARC Solaris (64-Bit)
Precompiler option Sqlmod*Ada is not supported by this release.
On Sun SPARC Solaris, Entrust/PKI and CyberSafe authentication methods are not supported for this release.
This section presents issues that can occur during post-installation.
The relink script is located in $ORACLE_HOME/bin
. If you run the command relink all
, the relink script tries to relink the Oracle Names and Oracle Connection Manager executables even when these products are not installed. If you did not install Oracle Names and Oracle Connection Manager, you will see the following errors:
ld: fatal: File processing errors. No output written to names make: Fatal error: Don't know how to make target '<ORACLE_HOME>/network/lib/s0nfpc.o'
These errors should be ignored. They will not occur if Oracle Names and Oracle Connection Manager are installed.
|
Copyright © 2001 Oracle Corporation. All Rights Reserved. |
|