If you are using a Windows operating system for your
database server, apply database patchset 9.0.1.3 and
database patch 9.0.1.3.0 patch 3 or higher.
This combination of patches for Windows NT/2000
contains fixes corresponding to those identified above.
Check OracleMetaLink for additional patches
Additional issues with Applications running on 9.0.1 may
have been identified since this document was authored.
Check the Certify section of OracleMetaLink for the
latest issues.
Log in as the Oracle user
Log in as the user who manages (owns) the existing
Oracle8i Enterprise Edition files and Applications
database. Make sure that none of the environment settings
such as ORACLE_HOME, PATH, ORA_NLS, etc. refer to the
existing Oracle8 Enterprise Edition Release 8.0.x or
Oracle9i environment.
Prepare Database for Upgrade
The Prepare to Upgrade section of Oracle9i
Database Migration (9.0.1) contains steps to be executed
to the existing database in the existing environment before
upgrade. Complete all the steps listed there.
Apply Workaround for JAVA CLASS
Some databases may encounter an ORA-600 error during the
upgrade due to an invalid Java class (bug 1567117). You can
determine if your database has the problem by executing the
select statement using SQL*Plus connected as INTERNAL:
SQL> select dbms_java.resolver
SQL> ('oracle/xml/parser/v2/XSLTContext',
SQL> 'APPS','JAVA CLASS')
SQL> from dual;
If the above command results in an ORA-600 error with the
following arguments: [26599], [1], [14] ..., then you have an
invalid JAVA CLASS.
To workaround the issue, start SQL*Plus and connect to the
database instance as SYS
user. Execute the following command.
SQL> update idl_ub1$
SQL> set length = 1935
SQL> where obj# = ( select obj# from obj$ o, user$ u
SQL> where o.type# = 29
SQL> and u.name = 'APPS'
SQL> and o.name = '/577f4ba0_XSLTContext' )
SQL> and piece# = 3 ;
SQL> commit ;
SQL> exit ;
Shut Down Servers, Concurrent Managers and Database
All servers and processes such as the Oracle Applications
forms server, Web Server and Concurrent Managers must be
shut down and all users must be logged out before starting
the database upgrade.
Oracle Applications will be unavailable to users until all
tasks in these notes are completed.
Backup the Oracle Applications Database
Log in as the user who manages (owns) the Oracle9i
files and database. We recommend taking a backup of your
database before moving up the database to Oracle9i
server.
Log in as the Oracle user
Log in as the user who manages (owns) the Oracle9i
files and database. Make sure that none of the environment
settings such as ORACLE_HOME, PATH, ORA_NLS, etc. refer to
the existing Oracle8 Enterprise Edition Release 8.0.x or
Oracle8i Enterprise Edition Release 8.1.x environment.
Ensure Adequate Rollback and System Space
Ensure that there is sufficient free space in the SYSTEM
tablespace (greater than 500 MB) and for the Rollback
segments (greater than 750 MB) with each having maxextents
greater than 512.
Upgrade the Oracle Applications Database
Follow instructions in the Oracle9i
Database Migration (9.0.1) to migrate the database
to the current release. An updated version of this
document may be found on the
Oracle Technology Network. You must follow the
manual method of Database Upgrade.
Modify init.ora parameters
Some database initialization parameters have changed
or become obsolete in Oracle9i Release 9.0.1.x. Details
are available in the Oracle9i Database
Migration manual. In addition to whatever other
parameters are appropriate at your site, add or update the
following:
Make sure that compatibility and optimizer_features_enable
is not set to a release before 9.0.0. Set both fields to 9.0.1
after Migrating/Upgrading the Database and before the
Upgrading Specific Components portion of the Database
Migration manual.
_system_trig_enabled = TRUE
o7_dictionary_accessibility = TRUE
compatible = 9.0.1
optimizer_features_enable = 9.0.1
event="10932 trace name context level 32768"
event="10933 trace name context level 512"
event="10943 trace name context level 16384"
Some of the events set above are for maintaining PL/SQL compiler
compatibility.
If your init.ora file contains the following parameters, you
should remove them now.
event="10943 trace name context forever, level 2"
_complex_view_merging
_new_initial_join_orders
_optimizer_mode_force
_optimizer_undo_changes
_or_expand_nvl_predicate
_ordered_nested_loop
_push_join_predicate
_push_join_union_view
_sort_elimination_cost_ratio
_use_column_stats_for_function
Attention:
During your database migration, instructions in the
Oracle9i Database Migration (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.
|
Upgrade the Specific Database Components
The Oracle Applications Release 11i databases currently
uses the following components, you must now complete the steps
specific to these components referred in the Migration Document.
- Upgrading Oracle JServer
- Upgrading XDK for Java
- Upgrading Session Namespace, CORBA and OSE
- Upgrading JSP
- Upgrading Oracle Spatial
- Upgrading interMedia
- Upgrading Oracle Text
- Upgrading Statistics Tables Created by DBMS_STATS Package
- Recompiling Invalid PL/SQL Modules
These are the only components that you must upgrade in a
standard Applications database instance. Unless you have
specifically enabled other components for your local
customizations, you need not perform any other database
component upgrades.
After going through all the necessary steps, if you find invalid
JAVA CLASS or UNDEFINED objects, you may recompile then individually.
Generally, Snapshots and Materialized Views are marked as
UNDEFINED objects. We recommend compiling UNDEFINED objects
treating them as snapshots.
Attention:
After completion of the database upgrade, package
body JIS817_U_PKGS has a state of
invalid. This package is not needed and
can be ignored or deleted.
|
Oracle 9i Patch Set Post Install tasks
Post Install tasks mentioned in the Oracle 9i
Database Server Patch Set README file should be executed now
to complete the database migration. In the Post Install Actions
step of this readme file, please ignore all the actions from
the beginning, up to and including
"ALTER SYSTEM DISABLE RESTRICTED SESSION; ". You must
perform all actions beginning from the interMedia Text section.
Configure the Oracle Net listener
The Oracle Net listener must be configured such that the
database can be accessed from the Oracle Applications Release
11i file system and the Oracle8 Enterprise Edition
Release 8.0.x technology stack. Refer to the Net9
Administrator's Guide. Start the listener once
it has been configured.
Ensure configuration of the Oracle Net client
Configure the Oracle Net client on each Release 11i
server (other than the database server) such that the Oracle
Applications Release 11i file system can connect to
the database on the Release 11i database server. Ensure
that your configuration is using the new 9.0.1 ORACLE_HOME.
Refer to the Net8 Administrator's Guide.
The TWO_TASK environment variable on UNIX, or the LOCAL
environment setting on Windows NT/2000, must be set to the
connect string of the Applications database that you
define. Use SQL*Plus to test the connection.
Compile All Apps objects
Many database objects will become invalid due to the database
upgrade. Compile the objects that belong to the APPS schema. Run
AD Administration on the administration server and choose the
"Compile APPS schema(s)" option from the Maintain Applications
Database Objects menu.
You may use the standard utility utlrp.sql (found in
$ORACLE_HOME/rdbms/admin) to compile all the non Oracle
Applications schema objects.
Recreate grants and synonyms for APPS schema(s)
Oracle9i database has additional privileges compared
to Oracle8i. Run AD Administration on the administration
server and choose the "Recreate grants and synonyms for APPS
schema(s)" option from the Maintain Applications Database
Objects menu.
Activate optimizer enhancement (optional)
The Oracle9i consolidated patch
includes an optimizer
enhancement. If you chose to install the patch, you should
activate the enhancement now.
Add the following line to your init.ora file:
event="38004 trace name context forever, level 1"
Shut down and restart the database.
| Attention: Everytime the
database is upgraded to a higher version of RDBMS, this
event has to be removed or commented out as it will
cause deadlocks during the upgrade. Do not
disable this event from the session level.
|
Update 8.0.6 ORACLE HOMEs
The 8.0.6 ORACLE HOME used by Oracle Applications must be
updated to connect to Oracle9i database.
-
If you are using a UNIX (or Linux) operating system for
your database server, apply latest cerified patchset
(patchset 3 or higher) to all Oracle 8.0.6 ORACLE_HOMEs.
Follow the instructions in the readme file of the patchset.
-
If you are using a Windows operating system for your
database server, apply patch 8.0.6.3.5 to all Oracle
8.0.6 ORACLE_HOMEs. Follow the instructions in the
readme file of the patch.
Apply latest certified Forms patchset
Use of Developer 6i with Oracle 9i requires at
a minimum Forms Patch Set 6. Instructions for installing
Forms patch sets can be found on OracleMetaLink; see
document 125767.1,
Upgrading Developer 6i with Oracle Applications 11i
.
Note that use of Developer 6i with the E-Business Suite
also requires Oracle JInitiator 1.1.7.32 or higher. Instructions
for upgrading Jinitiator can be found on OracleMetaLink;
see document 124606.1,
Upgrading Oracle JInitiator with Oracle Applications
11i
.