Database Server Enterprise Edition Release 9.0.1
August 2002
This document describes the process to upgrade an existing database
instance running on Oracle8i Enterprise Edition Release 8.1.7.x
directly to a version 9.0.1 patch set. Upgrading your system to an
9.0.1 patch set from a version earlier than 8.1.7 (for example 8.0.6
or 8.1.5) is not supported. In this case you must either
migrate/upgrade to 9.0.1.0 first and then install the patch set, or
upgrade/migrate to 8.1.7 and then follow these intructions.
Attention: There is an error in the 9.0.1.4 README (patch_note.htm)
indicating that upgrading from 8.1.7 directly to 9.0.1.4 is not
supported. It is supported as documented here. See Note 214972.1 for
the wording which should have appeared in the 9.0.1.4 Patch Set
README.
Attention: These notes apply to UNIX and Windows NT/2000 platforms.
However, you may need to modify some instructions slightly depending
upon your platform. For example, these notes typically use UNIX syntax
when specifying a directory, so Windows NT/2000 users will need to
substitute the appropriate syntax when accessing that
directory(folder).
Attention: You can obtain the most recent 9.0.1 patchset from
OracleMetaLink. After logging on to OracleMetaLink, navigate to the
patch download page using the menu on the left of the screen. Query
for the patchset using the following parameters:
Parameter
Value
Product Family Oracle Server
Release 9.0.1.x (where x is the highest version available)
Platform
Limit Search to Latest Product Patchsets or Minipacks
Upgrading from Oracle8i Release 8.1.7.x Database Server to Oracle9i
Enterprise Edition Release 9.0.1.x
Follow instructions in this section only if you have an existing
Database Server using Oracle8i Enterprise Edition Release 8.1.7.x.
Upgrading from pre-8.1.7 versions directly to an 9.0.1 patch set is
not supported.
1.
Install Oracle9i Enterprise Editions Release 9.0.1 in new ORACLE_HOME.
Log in as the user who manages (owns) the Oracle9i Enterprise
Edition files and database. Make sure that none of the environment
settings such as ORACLE_HOME, PATH, ORA_NLS, etc. refer to the
existing Oracle8i Enterprise Edition Release 8.1.7 environment.
If you have not already installed the current Oracle9i
Enterprise Edition Release 9.0.1 files, follow the instructions in the
Oracle9i Installation Guide. Install the files in a location other
than the existing 8.1.7 Oracle home. Choose to install all components
currently used by your 8.1.7 database.
Attention: Windows NT/2000 customers should not install the
following development tools. These tools do not support multiple
Oracle Homes.
* Oracle Objects for OLE
* Oracle ODBC Drivers
* Oracle OLE Providers for OLEDB
We also recommend choosing all the languages, (or at a minimum
all the required languages) during the installation.
Do not run any migration scripts at this time.
2. Install 9.0.1 Patch Set
Install the latest Oracle9i Release 9.0.1 patch set into the
9.0.1 Oracle Home using Oracle Universal Installer.
Do not run any SQL scripts at this time.
3. Check OracleMetaLink for additional patches
Additional issues with 9.0.1 may have been identified since this
document and the Patch Set Release Notes were authored. Check Document
149018.1 on Metalink for the latest issues/alerts.
4. Prepare Database for Upgrade
The 'Prepare to Upgrade' section of Chapter 7 (Upgrading from an
Older Release of Oracle to the New Oracle9i Release) of the Oracle9i
Migration Release 1 (9.0.1) contains steps to be executed to the
existing database in the existing environment before upgrade. Complete
all the steps listed there.
5.
Shutdown Servers, Concurrent Managers and Database
All servers and processes such as the Web Server and Net8
Listener must be shut down and all users must be logged out before
starting the database upgrade.
The Database will be unavailable to users until all tasks in
these notes are completed.
6. Modify init.ora parameters.
Some of the database initialization parameters have changed or
become obsolete in Oracle9i Enterprise Edition Release 9.0.1. Details
are available in the Oracle9i Migration manual.
Attention: During your database migration, instructions in the
Oracle9i Database Migration Release 1 (9.0.1) require the value of
_system_trig_enabled to be temporarily set to false at the beginning
of the migration, and restored to true before upgrading JServer.
7. Backup the Database.
We recommend taking a backup of your database.
8. Ensure Adequate Rollback and System Space
Ensure that there is sufficient free space in the SYSTEM
tablespace and for the Rollback segments (see Oracle9i Migration
Release 1 (9.0.1) for more details.
9. Upgrade the Database
Follow instructions in the manual Oracle9i Migration Release 1
(9.0.1) to upgrade the database to the current release. Ensure that
you have the latest version of the manual, which can be found on the
Oracle Technology Network.
Continue Chapter 7 of the Oracle9i Migration Release 1 (9.0.1)
Guide with the section titled 'Upgrade the Database'. If using the
dbma to perform the migration then start with the section titled
'Running the Oracle Data Migration Assistant Independently'. If
choosing to perform the migration manually start with the section
entitled 'Upgrade the Database Manually' but skip to step 9 as the new
release has already been installed .
You will be upgrading directly to the current 9.0.1 patch set level.
1. You must now complete the steps specific to any components
referred in the Migration Document that you are using.
There is no need to compile invalid database objects at this time.
2. Oracle9i Release 9.0.1 Patch Set release notes contains
additional steps required to complete the install of the patch set.
Follow the instructions in the How to Install This Patch Set section
to upgrade the Databases to the latest patch set level. The step 9 in
this document has instructions to run the following script, you may
ignore running this script:
* ?/rdbms/admin/catpatch.sql
10. Compile All objects.
You may use the standard utility utlrp.sql (found in
$ORACLE_HOME/rdbms/admin) to compile all invalid objects in the
database.
Some database objects will have become invalid due to the
database upgrade.
Change Log
Date Description
June 21, 2002
* Document created based on 8.1.7 version and Applications 11i
Interoperability guide.
August 13, 2002
* Updated for 9.0.1.4
No comments:
Post a Comment