Copy and update Rapid Install utility files (conditional)
Do this step only if AutoConfig is not enabled.
Copy the <SID>.env/cmd file and the
appsutil subdirectory
and all of its contents from the old Oracle home to the 9.0.1
Oracle home on the database server node. If the
<SID>.env/cmd refers to a file called
ORACLE.env/cmd, copy that file as well.
Update the <SID>.env/cmd file and,
if applicable, the ORACLE.env/cmd file in the 9.0.1
Oracle home such that any references to the old Oracle home
and TNS_ADMIN locations are
changed to the 9.0.1 Oracle home and TNS_ADMIN locations.
Update the files in the
/appsutil/scripts subdirectory in the 9.0.1
Oracle home such that
any references to the old Oracle home location are changed to
the 9.0.1 Oracle home location.
Once the updates are complete, test the addlnctl.sh/cmd
script in
the 9.0.1 Oracle home by using it to start the new Oracle Net
listener for the database instance. Then, 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.
This will test the Net8 configuration that you may have performed in
the previous step, as well as the new Oracle Net listener. Keep the
listener running; one of the tasks in the next step requires it.
Attention: If AutoConfig is enabled,
the scripts in the /appsutil/scripts/<SID>
of the Oracle8i database server node like
addbctl.sh/cmd, adstopdb.sql, and
adstrtdb.sql will no longer work as they are applicable
only to the Oracle8i database server node only. The
Oracle9i version of the scripts will be available in the near
future.
|
Upgrade specific components and perform post-upgrade tasks
Perform Step 21 in the "Upgrade the Database Manually"
subsection of the "Upgrading the Database to the New Release"
section of Chapter 7 of Oracle9i Database Migration,
Release 1 (9.0.1).
In the "Upgrading Specific Components" section, the tasks in
the following subsections must be performed:
- Upgrading JServer
- Upgrading XDK for Java
- Upgrading Session Namespace, CORBA and OSE
- Upgrading JSP
- Upgrading Oracle Spatial
- Upgrading interMedia
- Upgrading Oracle Text
The other subsections apply to components that are not used in an
Applications database instance by default, or only apply if you
had upgraded from Oracle8. Unless you have manually enabled the
non-default components in the Applications database instance, there
is no need to perform their upgrade tasks.
| Note: It is not necessary to perform
the tasks in the "Recompiling Invalid PL/SQL Modules" subsection at
this time, because you will be directed to do so in the next step.
|
Once you reach the "Adjust Your Initialization Parameter File
for the New Release" subsection of the "Tasks to Complete After
Migrating or Upgrading Your Database" section of Chapter 8,
refer to document 216205.1,
Database Initialization Parameters for Oracle Applications 11i,
on OracleMetaLink. Use the sections
that contain common initialization parameters, initialization
parameters that are specific to Oracle9i Release 1,
and initialization parameter sizing recommendations to make any
necessary changes (additions, updates, or removals) to the
initialization parameters in your Applications database instance.
Do not perform any other tasks in that document at this time.
| Attention:
- The AQ_TM_PROCESSES and JOB_QUEUE_PROCESSES parameters were
required to be set to zero during the upgrade,
but now you must set them to the recommended nonzero values.
- Do not set the UNDO_% parameters yet; you will be directed to
do so as part of the System Managed Undo (SMU) instructions
in the next paragraph.
|
Finally, once all the post-upgrade tasks have been performed,
follow the instructions in the "Enabling System Managed Undo (SMU)"
and "Temporary Tablespace Setup" sections of the aforementioned
document to convert from rollback segment usage to SMU, and to
confirm that the temporary tablespace is properly defined.
Perform 9.0.1.4 patch set tasks
On the database server node, as the owner of the Oracle RDBMS file
system and database instance, perform Step 6 in the patch set notes,
while observing the following:
- Oracle Text, Java, and Oracle Spatial are installed in Oracle
Applications database instances, so you will need to perform
their tasks.
- Oracle Label Security, UltraSearch, Oracle9i
Real Application Clusters Guard, and Oracle Recovery
Manager (RMAN) are not installed by default in Oracle
Applications database instances. The tasks for these
components do not need to be performed unless they have 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.
Note:
After completion of the database upgrade, the package
body JIS817_U_PKGS and the view DEFCALL
in the SYSTEM schema, and the materialized views
BIM_R_FDSP_SUMFUND_MV and
BIM_R_FDSP_SUMMARY_MV in the APPS schema may have a
status of INVALID. These objects are not needed and
can be ignored or dropped.
|
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.
Apply post-upgrade Applications interoperability patches (conditional)
If applicable, apply the following patches to the administration server node:
| Product |
Short Name |
Instructions |
| Applications DBA |
AD |
If you are using Release 11.5.7, and the AD minipack level
is earlier than Minipack G, apply patch
2361208.
This fixes problems with the
"Recreate grants and synonyms for APPS schema(s)" and
"Maintain Multiple Reporting Currencies schema(s)" tasks
in AD Administration.
|
| CRM Gateway for Mobile Devices |
ASG |
If ASG is licensed, you are using Release 11.5.7 or earlier,
and the ASG minipack level is earlier than Minipack P,
apply patch
2637492.
This fixes the package body ASG_REP_CONF.
|
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).
Attention:
Due to bug 2233522, AD Administration and other AD utilities
may complain about missing or unset parameters in the
init<SID>.ora file when used with an
Oracle9i database instance. Such parameters should
not be set, because they are either obsolete in
Oracle9i or are no longer appropriate for the Applications
when used with Oracle9i. It is safe to ignore these
error messages and continue to use the AD utilities as normal.
The bug will be fixed in a future release. |
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.