- Upgrade Oracle Applications to Release 11.5.4 or later
(conditional)
Only Release 11.5.4 or later releases of Oracle
Applications are certified
for use with Oracle9i Release 1 (9.0.1). If the release of
your Applications system is earlier than 11.5.4, you must apply the
Release 11.5.4 Maintenance Pack,
or a later maintenance pack, to your system now.
- Apply latest certified Forms and Reports (Developer) 6i
patch set (conditional)
Only Patch Set 6 or later of Oracle Developer 6i is certified
for use with the Applications using Oracle9i Release 1
(9.0.1). If the patch set level of Oracle Developer 6i in
your Applications system is earlier than 6, you must apply
Patch Set 6,
or a later certified patch set, to each application tier server
node now. Refer to document 125767.1,
Upgrading Developer 6i with Oracle Applications 11i
on OracleMetaLink for information about the latest certified
patch set and associated installation instructions.
- Apply Applications Interoperability Patches
Oracle provides an interoperability patch for those pieces of
Applications code that require modification to work with
Oracle9i Release 1 (9.0.1). Obtain and install patch
1833692.
In addition, if you are running portions of the CRM suite of
applications you may need additional patches as outlined below.
| Product |
Code |
Instructions |
| Universal Work Queue |
IEU |
- If running earlier code than IEU patchset I,
obtain and install patch
1900420.
|
| Sales Compensation |
AS |
- If you are running Sales Compensation
at a patch level below Sales and Marketing Family Patch
1809318, obtain and install patch
2015079.
-
If you are running Sales Compensation at or above patch
level 1809318, obtain and install patch
2027612.
|
| eMail Center |
IEM |
- Obtain and install Oracle eMail Server 5.2 patch
set1 (patch
1993561)
- Obtain and install two Oracle eMail Server patches,
1683419 and
1878580.
|
| CRM Gateway for Mobile Devices |
ASG |
- Upgrade your Mobile Device Gateway (MDG)
database to Oracle8i Release 8.1.7.2.
- Obtain and install Oracle8i patch
1836101
against the MDG database
- Obtain and install Oracle Lite8i 4.0.0.6.0 patch
1748158
- Obtain and install CRM Gateway for Mobile Devices patch
1809904
|
- Prepare to create the 9.0.1 Oracle home
Decide where you want to install the 9.0.1 Oracle home on the
database server node; it must be in a different directory than
the current Oracle home.
On the database server node, as the owner of the Oracle RDBMS file
system and database instance, unzip and extract the patch set file
appropriate for your platform. Read the patch set notes (usually
delivered in a file called patch_note.htm) as well as Chapter 1
of Oracle9i Database Migration, Release 1 (9.0.1) and make
sure you thoroughly understand the upgrade and patch set installation
process before you begin. Check OracleMetaLink or contact
Oracle Support Services for any known issues with the patch set and
its interoperability with Oracle Applications. Make sure
that you have the latest version of the Database Migration manual,
which can be found on the
Oracle Technology Network.
- Create the 9.0.1 Oracle home
Log in to the database server node as the owner
of the Oracle RDBMS file system and database instance. Ensure
that environment settings such as ORACLE_HOME are set for the new
Oracle home you are about to create, and not for any existing
Oracle homes on the database server node. Perform steps 1-8
in the "Upgrade the Database Manually" section of
Chapter 7 of Oracle9i Database Migration, Release 1 (9.0.1).
In the Available Products window, use the Product Languages button
to select for installation any languages other than American English
that are used by your Applications database instance.
In the Installation Types window, you may choose either the
Enterprise Edition or the Custom installation types. If you choose
Enterprise Edition, then make sure to select the Software Only
database configuration option. If you choose Custom, then in
addition to any other components that you would like to install,
the following components are required by the Applications and must
be installed:
- Oracle9i
- Enterprise Edition Options -> Oracle Spatial,
Oracle Partitioning
- Oracle Net Services -> Oracle Net Listener,
Oracle Connection Manager
- Oracle 9i Development Kit -> Oracle
Call Interface (OCI), Object Type Translator,
Pro*C/C++, Oracle XML Developer's Kit, Oracle
XML SQL Utility
Attention:
The following development tools should not be installed on
Applications database server nodes running Windows.
These tools do not support multiple Oracle homes and are
not used by the Applications.
- Oracle9i Development Kit -> Oracle
Objects for OLE, Oracle ODBC Driver, Oracle Provider
for OLE DB
|
When the Oracle Net Configuration Assistant window appears, use
it to configure the Oracle Net listener for the Applications
database instance as well as external procedures. Refer to the
Oracle9i Net Services Administrator's Guide, Release 1 (9.0.1)
for information about how to configure a listener. Use the
listener.ora file in the old Oracle home as an example of how the
listener.ora file in the 9.0.1 Oracle home should be configured.
Do not start the new listener yet.
Do not perform any other upgrade steps in the Database Migration
manual at this time.
- Install the 9.0.1 patch set files
On the database server node, as the owner of the Oracle RDBMS file
system and database instance, perform steps 4 and 5 (UNIX/Linux) or
step 4 (Windows) in the patch set notes to install the patch set
files into the new 9.0.1 Oracle home, while observing the following:
- The ORACLE_HOME environment setting must point to the new
9.0.1 Oracle home, not to any other existing Oracle homes
on the database server node.
- The ORACLE_SID environment setting must not be set
to the Applications database SID, nor to any other value.
- It is not necessary to shut down the Applications database
instance before applying the patch set, because the patch
set is being applied to the new 9.0.1 Oracle home, which
the database instance is not using yet.
Do not perform any other steps in the patch set notes at this time.
- Shut down Applications server processes
Shut down all Applications server processes except for the database
instance. The Applications will be unavailable to users until all
tasks in this section are completed.
- Apply RDBMS patch 1567117 to the database instance (conditional)
If you are upgrading from 8.1.7.2 or previous versions of
RDBMS, apply patch
1567117
to the database instance. This fixes an invalid Java class which
will cause an ORA-600 error during the upgrade process.
- Prepare to upgrade
Follow the instructions in the "Prepare to Upgrade" section of
Chapter 7 of Oracle9i Database Migration, Release 1 (9.0.1).
We recommend having at least 500 MB of free SYSTEM tablespace and
750 MB of free rollback segment space, with
MAXEXTENTS set to at least 512, before performing the upgrade.
- Upgrade the database instance
Perform steps 9-21 in
the "Upgrade the Database Manually" subsection of the "Upgrade the
Database" section of Chapter 7 of Oracle9i Database Migration,
Release 1 (9.0.1).
Perform the following tasks for the "Upgrading Specific Components"
subsection:
- Upgrading JServer
- Upgrading XDK for Java
- Upgrading Session Namespace, CORBA, and OSE
- Upgrading JSP
- Upgrading Oracle Spatial
- Upgrading Oracle interMedia
- Upgrading Oracle Text
Do not perform the "Recompiling Invalid PL/SQL Modules" subsection as
this will be done later.
The other components are not used in an Applications database
instance by default. Unless you have manually enabled such
components in the Applications database instance, there is no need
to perform their upgrade tasks.
During the upgrade process, there are certain parameters that
must be added, updated, or deleted from the initialization parameter
files ifilecbo.ora and either init<SID>.ora or
spfile<SID>.ora. These
changes should be performed once you reach the "Adjust Your
Parameter File for the New Release" subsection of the "Tasks
to Complete After Upgrading Your Database" section of Chapter 8
of Oracle9i Database Migration, Release 1 (9.0.1).
The following parameter must be added or updated in the
ifilecbo.ora file:
optimizer_features_enable = 9.0.1
The following parameters must be added or updated in either the
init<SID>.ora file or the spfile<SID>.ora file:
_system_trig_enabled = TRUE
compatible = 9.0.1
o7_dictionary_accessibility = TRUE
event="10932 trace name context level 32768"
event="10933 trace name context level 512"
event="10943 trace name context level 16384"
(The events are necessary in order to maintain PL/SQL compiler
compatibility.)
The following parameters, if they exist, must be removed from the
ifilecbo.ora, init<SID>.ora, or spfile<SID>.ora files:
event="10943 trace name context forever, level 2"
event="38004 trace name context forever, level 1"
_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
Shut down and restart the database instance once these changes have
been made.
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.
|
- Perform 9.0.1 patch set tasks
On the database server node, as the owner of the Oracle RDBMS file
system and database instance, perform step 6 (UNIX/Linux) or
step 5 (Windows) in the patch set notes, while observing the
following:
- We recommend that you perform the task that uses utlrp.sql
or utlrcmp.sql to compile all invalid objects in the
database.
- Oracle Label Security and Oracle UltraSearch are not installed
by default in Oracle Applications database instances.
These steps do not need to be performed unless it has been
manually installed.
- Oracle Recovery Manager are not installed by default in
Oracle Applications database instances, so you do not need
to perform the RMAN catalog task unless it has been
manually installed.
After going through all the necessary steps, if you find invalid
JAVA CLASS or UNDEFINED objects, you may recompile them 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 in the SYSTEM schema may have a
status of invalid. These objects are not needed and
can be ignored or deleted.
|
- Re-create database links (conditional)
If the port of the Oracle Net listener in the 9.0.1 Oracle home is
different than that used by the listener in the old Oracle
home, then you must re-create any self-referential database links
that exist in the Applications database instance. To check for the
existence of database links, use SQL*Plus on the database server
node to connect to the Applications database instance as APPS
and run the following query:
$ sqlplus apps/<apps password>
SQL> select db_link from dba_db_links;
If the EDW_APPS_TO_WH and APPS_TO_APPS database links exist, use
the following commands to drop and re-create them:
$ sqlplus apps/<apps password>
SQL> alter session set global_names=false;
SQL> drop database link EDW_APPS_TO_WH;
SQL> drop database link APPS_TO_APPS;
SQL> create database link EDW_APPS_TO_WH connect to apps
identified by <apps password> using
'(DESCRIPTION=(ADDRESS=(PROTOCOL=TCP)(HOST=<host name>)
(PORT=<port number>))(CONNECT_DATA=(SID=<ORACLE_SID>)))';
SQL> create database link APPS_TO_APPS connect to apps
identified by <apps password> using
'(DESCRIPTION=(ADDRESS=(PROTOCOL=TCP)(HOST=<host name>)
(PORT=<port number>))(CONNECT_DATA=(SID=<ORACLE_SID>)))';
where <host name> is the host name of the database server
node, <port number> is the port number of the new Oracle Net
listener for the database instance, and <ORACLE_SID> is the
ORACLE_SID of the database instance.
If you have custom self-referential database links in the database
instance, use the following commands to drop and re-create them:
$ sqlplus apps/<apps password>
SQL> drop database link <custom database link>;
SQL> create database link <custom database link> connect to
<user> identified by <password> using
'(DESCRIPTION=(ADDRESS=(PROTOCOL=TCP)(HOST=<host name>)
(PORT=<port number>))(CONNECT_DATA=(SID=<ORACLE_SID>)))';
where <custom database link>, <user>, <password>,
<host name>, and <ORACLE_SID>
are all as they were in the original database link definition,
and <port number> is the port number of the new Oracle Net
listener for the database instance.
- Configure the Net8 client (conditional)
If the port of the Oracle Net listener in the 9.0.1 Oracle home is
different than that used by the listener in the old
Oracle home, then you must update the entry for the Applications
database instance in the tnsnames.ora file with the new port
number. The tnsnames.ora file is located in the
$ORACLE_HOME/network/admin directory in both the 8.0.6 and
iAS Oracle homes on each application tier server node; each
one must be updated. Refer to the Net8 Administrator's Guide
for instructions on how to do this.
Once the configuration is complete and you have performed the next
step ("Copy and update Rapid Install utility files"),
and the new Oracle Net listener for the database instance is
running, use SQL*Plus to test the Net8/Oracle Net connection from
the 8.0.6 and iAS Oracle homes on each application tier
server node to the database instance.
- Copy and update Rapid Install utility files
Copy the <SID>.env/cmd file and the appsutil subdirectory
from the old Oracle home to the 9.0.1 Oracle home. (If AutoConfig
is not implemented in the Applications system, then you must copy
an additional file, ORACLE.env/cmd.) Update the
<SID>.env/cmd, ORACLE.env/cmd (if applicable), and
/appsutil files and scripts in the 9.0.1 Oracle home to reflect
the new Oracle home directory.
Once the updates are complete, test the addlnctl.sh/cmd script by
using it to start the new Oracle Net listener for the database
instance.
- Activate optimizer enhancement (optional)
If you choose to activate optimizer enhancement, 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.
|
- Re-create grants and synonyms
Oracle9i Release 1 (9.0.1) contains new functionality
regarding grants and synonyms that Oracle8i did not have.
As a result, you
must re-create the grants and synonyms in the APPS schema(s).
On the administration server node, as the owner of the Applications
file system, run AD Administration and select the "Recreate grants
and synonyms for APPS schema(s)" task from the Maintain Applications
Database Objects menu.
If MRC is implemented in your Applications system, then select the
"Maintain Multiple Reporting Currencies schema(s)" task
afterwards. This will re-create grants and synonyms for the MRC
schema(s).
- Restart Applications server processes
Restart all the Applications server processes that you shut down
before upgrading the database instance. Remember that the Oracle
Net listener for the database instance, as well as the database
instance itself, need to be started in the 9.0.1 Oracle
home from now on. Users may return to the system.