Interoperability Notes

Oracle Applications Release 11i
with Oracle9i Release 2 (9.2.0)

November 2003

Attention: Only Oracle Applications Release 11.5.7 or later is certified for use with Oracle9i Release 2 (9.2.0).

Attention: Oracle9i Release 2 (9.2.0) Oracle Homes that were installed using the Release 11.5.9 Rapid Install on Microsoft Windows must not be upgraded using the 9.2.0.4 patchset. Check the Certify section of OracleMetaLink for the latest information on the application of Oracle9i Release 2 patchsets on Windows.

This document contains the following sections:

• Section 1: Upgrading an Oracle Applications Release 11i database server from prior Oracle RDBMS releases to Oracle9i Release 2 (9.2.0)
  Instructions for upgrading an Oracle Applications Release 11i database server and instance from Oracle8i Release 3 (8.1.7) or Oracle9i Release 1 (9.0.1) to Oracle9i Release 2 (9.2.0).
• Section 2: Applying the latest certified Oracle9i Release 2 (9.2.0) patch set
  Instructions for applying the latest certified Oracle9i Release 2 (9.2.0) patch set to an Oracle Applications Release 11i database server and instance that are already using Oracle9i Release 2 (9.2.0).

Attention: These notes apply to UNIX, Linux, and Windows platforms. However, you may need to modify some instructions slightly depending upon your platform. For example, these notes typically use UNIX/Linux syntax when specifying a directory, so Windows users will need to substitute the appropriate syntax when accessing that directory.

Attention: You can obtain the latest certified 9.2.0 patch set from OracleMetaLink. After logging on to OracleMetaLink, click on "Patches" using the menu on the left of the screen. Use quick links or advanced search to find the 9.2.0.4 patch set. If using advanced search, query for the patch set using the following parameters: Parameter Value Product Family:   Oracle Database Family Release:   Oracle 9.2.0.4 Platform or Language:   <your operating system> Patch Type:   Patchset/Minipack

1. Upgrade Oracle Applications to Release 11.5.7 or later (conditional)
   Only Release 11.5.7 or later releases of Oracle Applications are certified for use with Oracle9i Release 2 (9.2.0). If the release of your Applications system is earlier than 11.5.7, you must upgrade to a later maintenance level now. Release 11.5.9 is the latest available maintenance pack.

2. Apply latest certified Forms and Reports (Developer) 6i patch set (conditional)
   Patch Set 9 or later of Oracle Developer 6i is required when using Oracle Applications with Oracle9i Release 2 (9.2.0). If the patch set level of Oracle Developer 6i in your Applications system is earlier than patch set 9, you must apply 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.

3. Prepare to create the 9.2.0 Oracle home
   Decide where you want to install the 9.2.0 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 2 (9.2) 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.

4. Create the 9.2.0 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 all the steps in the "Install the Release 9.2 Oracle Software" section of Chapter 3 of Oracle9i Database Migration, Release 2 (9.2), except for those steps that refer to the Database Upgrade Assistant.

   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 must choose the Custom installation type. 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 HTTP Server -> BC4J Runtime for Database, Oracle Mod PL/SQL Gateway

   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

   In the Component Locations window, set the JRE 1.3.1 directory to ORACLE_HOME/jre/1.3.1, JRE 1.1.8 directory to ORACLE_HOME/jre/1.1.8, and OUI to ORACLE_HOME/appsoui. This is to make the directory structure consistent with that created by the Applications Rapid Install.

   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 2 (9.2) 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.2.0 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.

5. Install the 9.2.0.4 patch set files
   On the database server node, as the owner of the Oracle RDBMS file system and database instance, perform only the installation portion of the "Installing the Patch Set" steps while observing the following:
   • The ORACLE_HOME environment setting must point to the new 9.2.0 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.2.0 Oracle home, which the database instance is not using yet.

   Do not perform the "Post Install Actions" section yet.

6. Apply RDBMS patches for 9.2.0.4
   Apply the following RDBMS patches to the 9.2.0 Oracle home:

   For all UNIX/Linux platforms:

   • 3131210
   • 3167234

   For Windows platforms:

   • 3160576 - 9.2.0.4 Patch 2
   • 2417995 - The 9.2.0.1 version of this patch will work for all versions of Oracle9i Release 2

7. 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.

8. Prepare to upgrade
   Read Chapter 2 of Oracle9i Database Migration, Release 2 (9.2). Decide whether you will use the Database Upgrade Assistant or perform a manual upgrade, which are the two supported methods of upgrading an Applications database instance. We recommend using the Database Upgrade Assistant, because it will save you significant time and effort.

   If you decide to use the Database Upgrade Assistant, follow the instructions in the "Running the Database Upgrade Assistant Independently" subsection of the "Install the Release 9.2 Oracle Software" section of Chapter 3 of Oracle9i Database Migration, Release 2 (9.2) to start the Database Upgrade Assistant.

   If you decide to perform a manual upgrade, read and perform the steps in the "System Considerations and Requirements" and "Prepare the Database to be Upgraded" subsections of the "Upgrade the Database Manually" section of chapter 3 of Oracle9i Database Migration, Release 2 (9.2). 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.

   Attention: If you are on a Windows platform, please make sure to close any open Services applet window before beginning your upgrade. The removal of the current database service will fail if this window is open.

9. Upgrade the database instance
   Before running the upgrade, ensure that the following parameter, if it exists, is commented out:

             event="38004 trace name context forever, level 1"
             

   Otherwise it will cause deadlocks during the upgrade.

   If you are using the Database Upgrade Assistant, perform all the steps in the "Upgrade the Database Using the Database Upgrade Assistant" section of Chapter 3 of Oracle9i Database Migration, Release 2 (9.2).

   Attention: You may encounter the errors ORA-29844: duplicate operator name specified and ORA-29830: operator does not exist. You may safely ignore the errors.

   If you are performing a manual upgrade, perform all the steps in the "Upgrade the Database" subsection of the "Upgrade the Database Manually" section of Chapter 3 of Oracle9i Database Migration, Release 2 (9.2). When you reach the "Upgrading Specific Components" subsection, the following tasks must be performed:

   • Upgrading Oracle Spatial
   • Upgrading Oracle interMedia
   • Upgrading Oracle Text

   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.

   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 4, refer to the document 216205.1, Database Initialization Parameters (init.ora settings) in Oracle Applications Release 11i on OracleMetaLink. Use the sections that contain common initialization parameters, initialization parameters that are specific to Oracle9i Release 2, and initialization parameter sizing recommendations to make any necessary changes (additions, updates, or removals) to the initialization parameters in your Applications database instance.

   Attention: 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.

   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.

   Shut down and restart the database instance once these changes have been made.

10. Perform 9.2.0.4 Post Install Actions
    On the database server node, as the owner of the Oracle RDBMS file system and database instance, perform the "Post Install Actions" of the "Installing the Patch Set" section of 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 Recovery Manager is 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 completion of the post install steps, connect as SYSDBA and run the following:
    

    SQL> @?/javavm/install/jvmsec3.sql
    SQL> @?/javavm/install/jvmsec5.sql
              

    Attention: When you run jvmsec3.sql and jvmsec5.sql, ignore the following failures: ORA-29532: Java call terminated by uncaught Java exception: java.lang.SecurityException: policy table update SYS:java.lang.RuntimePermission, loadLibrary.oraawt ORA-29532: Java call terminated by uncaught Java exception: java.lang.SecurityException: policy table update SYS:java.lang.RuntimePermission, loadLibrary.oraioser ORA-29532: Java call terminated by uncaught Java exception: oracle.aurora.vm.IdNotFoundException: EJBCLIENT is not a user or role

    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 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 deleted.

11. Implement or update AutoConfig
    If you have already implemented AutoConfig on your system, you must apply the latest AutoConfig rollup patch that is available. If you have not already implemented AutoConfig, you must implement it now. Refer to Using AutoConfig to Manage System Configurations with Oracle Applications 11i on OracleMetaLink for instructions on how to implement or update AutoConfig.

    You should read the entire document whether you are implementing AutoConfig for the first time or updating it with the latest rollup patch. Like AutoConfig itself, the document has changed since its initial release and continues to evolve.

    Note: AutoConfig simplifies the management of the various system component configuration files. Once AutoConfig has been implemented, you must use it for all configuration management rather than editing configuration files directly.

12. Grant dictionary privileges to the SYSTEM, APPS, and MRC schemas
    On the administration server node, use SQL*Plus to connect to the database as APPS and run the $AD_TOP/patch/115/sql/adgrn9i.sql script with the following parameters:

    $ sqlplus apps/<apps password> @$AD_TOP/patch/115/sql/adgrn9i.sql
              <SYSTEM password> <APPS schema name>
              

13. Apply Oracle Applications Object Library (FND) patch
    Apply patch 2838093 to the administration server node. This fixes the package body DBMS_XMLQUERY.

14. Apply Oracle CRM Gateway for Mobile Devices patch (conditional)
    If Oracle CRM Gateway for Mobile Devices (ASG) is licensed, apply patch 2637492 to the administration server node. This fixes the package body ASG_REP_CONF.

15. Apply Oracle Contracts Core patch (conditional)
    If Oracle Contracts Core (OKC) is licensed, apply patch 2652080 to the administration server node. This fixes the view OKC_QUE_RULES_V.

16. Apply AD patch (conditional)
    If you are using Release 11.5.7 and have not already upgraded to AD patch G or later, apply patch 2361208 to the administration server node. This fixes problems with the "Recreate grants and synonyms for APPS schema(s)" and "Maintain Multiple Reporting Currencies schema(s)" tasks in AD Administration.

17. Re-create grants and synonyms
    Oracle9i Release 2 (9.2.0) contains new functionality regarding grants and synonyms that Oracle8i and Oracle9i Release 1 (9.0.1) 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).

18. 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.2.0 Oracle home from now on. Users may return to the system.

1. Prepare for patch set installation
   On the database server node, as the owner of the Oracle9i 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) and make sure that you thoroughly understand the 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 the Applications.
2. Shut down Applications server processes
   Shut down all Applications server processes including the database instance. The Applications will be unavailable to users until all tasks in this section are completed.
3. Temporarily modify initialization parameters for patch set installation
   Set the following parameters in the init<SID>.ora initialization parameter file and/or the spfile<SID>.ora server parameter file to the following values:

            aq_tm_processes = 0
            job_queue_processes = 0
            

   Make note of the original settings for the parameters. They will be needed after the patch set installation.
4. Install the 9.2.0.4 patch set files
   On the database server node, as the owner of the Oracle RDBMS file system and database instance, perform only the installation portion of the "Installing the Patch Set" steps.

5. Apply RDBMS patches for 9.2.0.4
   Apply the following RDBMS patches to the 9.2.0 Oracle home:

   For all UNIX/Linux platforms:

   • 3131210
   • 3167234

   For Windows platforms:

   • 3160576 - 9.2.0.4 Patch 2
   • 2417995 - The 9.2.0.1 version of this patch will work for all versions of Oracle9i Release 2

6. Perform 9.2.0.4 Post Install Actions
   On the database server node, as the owner of the Oracle RDBMS file system and database instance, perform the "Post Install Actions" of the "Installing the Patch Set" section of 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 Recovery Manager is 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 completion of the post install steps, connect as SYSDBA and run the following:
   

   SQL> @?/javavm/install/jvmsec3.sql
   SQL> @?/javavm/install/jvmsec5.sql
            

   Attention: When you run jvmsec3.sql and jvmsec5.sql, ignore the following failures: ORA-29532: Java call terminated by uncaught Java exception: java.lang.SecurityException: policy table update SYS:java.lang.RuntimePermission, loadLibrary.oraawt ORA-29532: Java call terminated by uncaught Java exception: java.lang.SecurityException: policy table update SYS:java.lang.RuntimePermission, loadLibrary.oraioser ORA-29532: Java call terminated by uncaught Java exception: oracle.aurora.vm.IdNotFoundException: EJBCLIENT is not a user or role

   Attention: More information about fixes in Advanced Queues may be found in OracleMetaLink alert 231074.1.

   Attention: Perform steps outlined in OracleMetaLink alert 237371.1.

7. Revert initialization parameters to their original settings
   Revert the aq_tm_processes and job_queue_processes parameters back to their original settings before the patch set installation. Shut down and restart the database instance so that the changes will be reflected in the database settings.

8. Restart Applications server processes
   Restart all the Applications server processes that you shut down before installing the patch set. Users may return to the system.