Interoperability Notes

Oracle Applications Release 11i
with Oracle8i Enterprise Edition Release 3 (8.1.7)

August 2003

This document contains the following sections:

• Section 1: Upgrading an Oracle Applications Release 11i database server from Oracle8i Enterprise Edition Release 2 (8.1.6) to Release 3 (8.1.7)
  Instructions for upgrading an Oracle Applications Release 11i database server and instance from Oracle8i Enterprise Edition Release 2 (8.1.6) to Release 3 (8.1.7).
• Section 2: Applying the latest certified Oracle8i Enterprise Edition Release 3 (8.1.7) patch set
  Instructions for applying the latest certified Oracle8i Enterprise Edition Release 3 (8.1.7) patch set to an Oracle Applications Release 11i database server and instance that is already using Oracle8i Enterprise Edition Release 3 (8.1.7).

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 8.1.7 patch set 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 patch set using the following parameters: Parameter Value Product Family:   Oracle Database Release:   Oracle 8.1.7.4 Platform:   <your operating system> Limit Search to:   Latest Product Patchsets or Minipacks

1. Apply Applications interoperability patch and AP minipack (conditional)
   Older releases of the Applications require an interoperability patch to be able to use Oracle8i Enterprise Edition Release 3 (8.1.7.2) or later. If you are using Release 11.5.4 or earlier, apply patch 1961224 to the forms server node and administration server node, if you have not done so already.

   If you are using Release 11.5.3 or earlier, you must also apply Oracle Payables Minipack C or later to all application tier server nodes, if you have not done so already.

2. Prepare to create the 8.1.7 Oracle home
   Decide where you want to install the 8.1.7 Oracle home on the database server node; it must be in a different directory than the 8.1.6 Oracle home.

   Decide whether you want to install the 8.1.7 Oracle home manually, or use the Rapid Install to create it for you. Using the Rapid Install will save you considerable configuration time and effort, because it automatically installs all the proper components and creates all the environment and configuration files for you. You must use Rapid Install Release 11.5.4 or later, because earlier releases contain Oracle8i Enterprise Edition Release 2 (8.1.6).

   On the database server node, as the owner of the Oracle8i 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 the first three chapters of Oracle8i Migration, Release 3 (8.1.7) and make sure you thoroughly understand the upgrade and patch set installation process before you begin. Follow the suggestion to check OracleMetaLink or contact Oracle Support Services for the latest status of, alerts regarding, and issues with the patch set and its interoperability with the Applications. Make sure that you have the latest version of the Migration manual, which can be found on the Oracle Technology Network.

   Attention: Use of the Oracle Data Migration Assistant (ODMA) is not supported with Applications database upgrades.

3. Create the 8.1.7 Oracle home
   If you use the Rapid Install to create the 8.1.7 Oracle home, use the "Create Upgrade file system" option to prevent a new database instance from being created. Follow the instructions in the "Upgrading Your Installation" chapter of Installing Oracle Applications, Release 11i to create the 8.1.7 Oracle home on the database server node. Configure the database server node only; if you configure other nodes, the Rapid Install will install more than the 8.1.7 Oracle home on the database server node. Since you are not upgrading the Applications, ignore any references to Upgrading Oracle Applications, Release 11i. As you go through the configuration process, make sure that environment settings such as SID and DB Character Set are set to the same values as your existing database instance.

   If you choose to manually install the 8.1.7 Oracle home, make sure you are logged in to the database server node as the owner of the Oracle8i file system and database instance. Also ensure that environment settings such as ORACLE_HOME are set for the new Oracle home you are about to create, and not for the existing 8.1.6 Oracle home or any other Oracle home that may exist on the database server node. Perform steps 1-7 of the "Upgrade the Database Manually" subsection of the "Upgrading the Database to the New Oracle8i Release" section of Chapter 7 of Oracle8i Migration, Release 3 (8.1.7). You must perform a Custom installation of the Enterprise Edition. In addition to any other components that you would like to install, the following components are required by the Applications and must be installed:

   • Oracle8i Server
   • Oracle Product Options -> Oracle Spatial, Oracle interMedia, Advanced Replication, Oracle Partitioning
   • Net8 Products -> Net8 Client, Net8 Server, Oracle Connection Manager
   • Oracle Utilities -> (all)
   • Oracle Java Products -> (all)
   • Oracle Configuration Assistants -> (all)
   • Development Tools -> Oracle Call Interface (OCI), Object Type Translator, Oracle XML Developer's Kit, Oracle XML SQL Utility
   • Oracle Installation Products -> Oracle Universal Installer
   • Documentation

   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. Development Tools -> Oracle Objects for OLE, Oracle ODBC Drivers, Oracle OLE Providers for OLE DB

   In the Available Product components window, use the Product Languages button to select for installation any languages other than American English that are used by your Applications database instance.

   When the Net8 Configuration Assistant window appears, use it to configure the Net8 listener for the Applications database instance as well as external procedures. Refer to the Net8 Administrator's Guide for information about how to configure a listener. Use the listener.ora file in the 8.1.6 Oracle home as an example of how the listener.ora file in the 8.1.7 Oracle home should be configured. Do not start the new listener yet.

   Do not perform any other upgrade steps in the Migration manual at this time.

4. Install the 8.1.7 patch set files
   On the database server node, as the owner of the Oracle8i file system and database instance, perform steps 4, 5, and 6 (UNIX/Linux) or step 4 (Windows) in the patch set notes to install the patch set files into the new 8.1.7 Oracle home, while observing the following:
   • The ORACLE_HOME environment setting must point to the new 8.1.7 Oracle home, not to the 8.1.6 Oracle home nor any other Oracle homes that may possibly be installed on the node, such as Oracle8 or OracleiAS.
   • The ORACLE_SID environment setting must not be set to the Applications database instance 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 8.1.7 Oracle home, which the database instance is not using yet.
   • UNIX/Linux only: If you used the Rapid Install to create the 8.1.7 Oracle home, Oracle Label Security is not installed by default, so you do not need to perform that task unless it has been manually installed.

   Do not perform any other steps in the patch set notes at this time.

5. Apply RDBMS patches to the 8.1.7 Oracle home
   Apply the following RDBMS patches to the 8.1.7 Oracle home:

   For all UNIX platforms:
   

   • 1805407
   • 2073948
   • 2225569
   • 2293786
   • 2360357
   • 2386334
   • 2401670
   • 2664217
   • 2865515

   For 32-bit Linux platform only:
   

   • 2062423
   • 2062512

   For Windows platform:
   

   • 2792558 - 8.1.7.4.7 Patch for Windows NT and Windows 2000

6. Apply workaround for upgrade problem with locally managed tablespaces
   The compatibility of the database must be reset to prevent an upgrade problem with the locally managed tablespaces in the Applications database instance.

   On the database server node, as the owner of the Oracle8i file system and database instance, start Server Manager, connect to the database instance as INTERNAL, and execute the following command:

   	  SVRMGR> alter database reset compatibility ;
   	  

   Make sure that environment settings such as ORACLE_SID and ORACLE_HOME are pointing to the Applications database instance and the 8.1.6 Oracle home.

7. Apply RDBMS patch 1567117 to the database instance
   Download patch 1567117 to the database server node. Only the script fix1567117.sql should be run. This fixes an invalid Java class which will cause an ORA-600 error during the upgrade process.

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

9. Prepare to upgrade
   On the database server node, as the owner of the Oracle8i file system and database instance, perform steps 1-12 in the "Prepare to Upgrade" subsection of the "Upgrading the Database to the New Oracle8i Release" section of Chapter 7 of Oracle8i Migration, Release 3 (8.1.7). Make sure that environment settings such as ORACLE_SID and ORACLE_HOME are pointing to the Applications database instance and the 8.1.6 Oracle home.

   We recommend having 500 MB of free SYSTEM tablespace and 750 MB of free rollback segment space before performing the upgrade.

10. Upgrade the database instance
    On the database server node, as the owner of the Oracle8i file system and database instance, perform steps 8-20 of the "Upgrade the Database Manually" subsection of the "Upgrading the Database to the New Oracle8i Release" section of Chapter 7 of Oracle8i Migration, Release 3 (8.1.7).

    When you perform the task of adjusting the initialization parameter file for use with the new release, 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 Oracle8i Release 3, and initialization parameter sizing recommendations to make any necessary changes (additions, updates, or removals) to the initialization parameters in your Applications database instance.

    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.

    In the "Upgrading Specific Components" section of Chapter 7, the tasks in the following subsections must be performed:

    • Upgrading interMedia Text From a Previous 8.1 Release
    • Upgrading Oracle Replication
    • Upgrading JServer

    Oracle Spatial also needs to be upgraded. Please refer to the document Oracle Spatial User's Guide and Reference, Release 8.1.7 for instructions on how to upgrade Oracle Spatial.

    The other subsections apply to components that 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 the tasks in their subsections.

    When upgrading JServer, you may disregard steps 14 through 21 because the Oracle Servlet Engine (OSE) is not used in Applications database instances. You may also disregard the steps for starting the Java Accelerator in step 22; however, you must load the XML Parser for PL/SQL and the XML Class Generator for Java.

    To load an XML jar file, use the command:

    loadjava -user sys/<sys password> -r -v <jar file>
              

    Attention: Due to doc bug 1930973, the PDF version of the Migration manual is missing an important step (running catxsu.sql) of the Upgrading JServer subsection, and therefore only has 21 steps. The HTML version does not have this problem. Make sure that your version of the manual has 22 Upgrading JServer steps before performing them.

11. Perform 8.1.7 patch set tasks
    On the database server node, as the owner of the Oracle8i file system and database instance, perform steps 7-19 (UNIX/Linux) or steps 5-17 (Windows) in the patch set notes, while observing the following:
    • In step 9 (UNIX/Linux) or step 7 (Windows), it is not necessary to run catalog.sql, catproc.sql, or catrep.sql.
    • In step 10 (UNIX/Linux) or step 8 (Windows), the only necessary action is to run initxml.sql.
    • We recommend that you perform the task that uses utlrp.sql or utlrcmp.sql to compile all invalid objects in the database.
    • Oracle interMedia Text is installed in Oracle Applications database instances, so you will need to perform that task.
    • It is not necessary to perform steps 17 and 18 (UNIX/Linux) or steps 15 and 16 (Windows).

    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.

12. Apply RDBMS patch 2708478
    Apply RDBMS patch 2708478 to the database. This patch cleans up duplicate AQ rows.

13. Re-create database links (conditional)
    If the port of the Net8 listener in the 8.1.7 Oracle home is different than that used by the Net8 listener in the 8.1.6 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 Net8 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>, and <ORACLE_SID> are all as they were in the original database link definition, and <port number> is the port number of the new Net8 listener for the database instance.

14. Configure the Net8 client (conditional)
    If the port of the Net8 listener in the 8.1.7 Oracle home is different than that used by the Net8 listener in the 8.1.6 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 (conditional)"), and the new Net8 listener for the database instance is running, use SQL*Plus to test the Net8 connection from the 8.0.6 and iAS Oracle homes on each application tier server node to the database instance. If you do not need to perform the next step, then use the addlnctl.sh/cmd script to start the new Net8 listener for the database instance before testing the Net8 connections.

15. Copy and update Rapid Install utility files (conditional)
    If you manually created the 8.1.7 Oracle home earlier in this section, you must copy the <SID>.env/cmd file and the appsutil subdirectory from the 8.1.6 Oracle home to the 8.1.7 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 8.1.7 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 Net8 listener for the database instance.

16. Restart Applications server processes
    Restart all the Applications server processes that you shut down before upgrading the database instance. Remember that the Net8 listener for the database instance, as well as the database instance itself, need to be started in the 8.1.7 Oracle home from now on. Users may return to the system.

1. Apply Applications interoperability patch and AP minipack (conditional)
   Older releases of the Applications require an interoperability patch to be able to use Oracle8i Enterprise Edition Release 3 (8.1.7.2) or later. If you are using Release 11.5.4 or earlier, apply patch 1961224 to the forms server node and administration server node, if you have not done so already.

   If you are using Release 11.5.3 or earlier, you must also apply Oracle Payables Minipack C or later to all application tier server nodes, if you have not done so already.

2. Prepare for patch set installation
   On the database server node, as the owner of the Oracle8i 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. Follow the suggestion to check OracleMetaLink or contact Oracle Support Services for the latest status of, alerts regarding, and issues with the patch set and its interoperability with the Applications.
3. 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.
4. Temporarily modify init<SID>.ora parameters for patch set installation
   Set the following parameters in the init<SID>.ora 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.
5. Install the patch set files
   On the database server node, as the owner of the Oracle8i file system and database instance, perform steps 4, 5, and 6 (UNIX/Linux) or step 4 (Windows) in the patch set notes to install the patch set files into the new 8.1.7 Oracle home. Make sure that your environment settings such as ORACLE_HOME and ORACLE_SID are pointing to the Oracle8i Oracle home and database instance, and not to other Oracle home environments that may possibly be installed on the node, such as Oracle8 or OracleiAS.

   As you perform the steps in the patch set notes, make note of the following:

   • UNIX/Linux only: Oracle Label Security is not installed by default in Oracle Applications database instances, so you do not need to perform that task unless it has been manually installed.
   • 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 8.1.7 Oracle home, which the database instance is not using yet.

   Do not perform any other steps in the patch set notes at this time.

6. Apply RDBMS patches to the 8.1.7 Oracle home
   Apply the following RDBMS patches to the 8.1.7 Oracle home:

   For all UNIX platforms:
   

   • 1805407
   • 2073948
   • 2225569
   • 2293786
   • 2360357
   • 2386334
   • 2401670
   • 2664217
   • 2865515

   For 32-bit Linux platform only:
   

   • 2062423
   • 2062512

   For Windows platform:
   

   • 2792558 - 8.1.7.4.7 Patch for Windows NT and Windows 2000

7. Apply RDBMS patch 1567117 to the database instance (conditional)
   If you are upgrading from 8.1.7.2 or previous versions of RDBMS, download patch 1567117 to the database server node. Only the script fix1567117.sql should be run. This fixes an invalid Java class which will cause an ORA-600 error during the upgrade process.

8. Perform 8.1.7 patch set tasks
   On the database server node, as the owner of the Oracle8i file system and database instance, perform steps 7-19 (UNIX/Linux) or steps 5-17 (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 interMedia Text is installed in Oracle Applications database instances, so you will need to perform that task.
   • It is not necessary to perform step 18 (UNIX/Linux) or step 16 (Windows).

9. Apply RDBMS patch 2708478
   Apply RDBMS patch 2708478 to the database. This patch cleans up duplicate AQ rows.

10. Revert init<SID>.ora 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.
11. 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.