Thursday, May 12, 2011

Oracle Applications Release 11i with Oracle 10g Release 2 (10.2.0)


Oracle Applications Release 11i with Oracle 10g Release 2 (10.2.0) [ID 362203.1]
Modified 17-FEB-2011 Type WHITE PAPER Status PUBLISHED


View Change log

Interoperability Notes

Oracle E-Business Suite Release 11i
with Oracle Database 10g Release 2 (10.2.0)

February 2011

This document describes how to use Oracle E-Business Suite Release 11i with Oracle Database 10g Release 2 (10.2.0.x), where x denotes the patch set level (currently 5). If you have previously saved or printed a copy of this document, note that it may be updated from time to time. Before you begin the tasks, always ensure that you have the most current instructions of document 362203.1 on My Oracle Support.

Attention
Interoperability notes of previous patch sets are available through the following links:

10.2.0.2 Interoperability Notes
10.2.0.3 Interoperability Notes
10.2.0.4 Interoperability Notes

Attention
Oracle E-Business Suite Releases prior to 11.5.10 are not certified for use with Oracle Database 10g Release 2 (10.2.0). If you are on release 11.5.10, ensure that you apply the prerequisite patches listed in this document, including the appropriate Consolidated Update patch. If you are following this document as part of the R12 upgrade, you have to be on release 11.5.7 at the minimum. Check My Oracle Support to make sure that your platform and environment configuration are certified to work with Oracle Database 10g before performing any instruction in this document.

Attention
If you are going to use 10g Real Application Clusters (RAC) or Automatic Storage Management (ASM), seeConfiguring Oracle Applications Release 11i with 10g Real Application Clusters and Automatic Storage Management on My Oracle Support.

This document contains the following sections:

Attention
These notes apply to UNIX, Linux, and Windows platforms. However, you may need to modify some instructions slightly depending on 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 10.2.0.5 patch set from patch 8202632 on My Oracle Support.

Section 1: Upgrading an 11i Database to Oracle Database 10g Release 2 (10.2.0)


Follow the instructions in this section if you have an Oracle E-Business Suite Release 11i system using Oracle8iRelease 3 (8.1.7), Oracle9i Release 1 (9.0.1), Oracle9i Release 2 (9.2.0), or Oracle 10g Release 1 (10.1.0), and you wish to upgrade the database server and instance to Oracle Database 10g Release 2 (10.2.0).

Before the Database Installation:

  1. Verify software versions
    The following software component versions must exist in your environment.

    SoftwareMinimum VersionTierDetails
    Oracle Database Enterprise Edition
    		DatabaseRead the "Determine the Upgrade Path to the New Oracle Database 10g Release" subsection in Chapter 2 of the Oracle Database Upgrade Guide 10g Release 2 (10.2). Make sure that direct upgrade is supported from your current release.
    Oracle E-Business Suite (for those staying on 11i)11.5.10 CU2ApplicationApply
    Oracle E-Business Suite (for those upgrading to R12)11.5.7ApplicationIf your Oracle E-Business Suite Release is earlier than 11.5.7, apply the11.5.10 E-Business Suite Consolidated Update 2
    Developer 6iPatch set 17ApplicationIf your patch set level is earlier than patch set 17, apply the latest certified patch set. See Upgrading Developer 6i with Oracle Applications 11i on My Oracle Support.
    AutoConfigLatest versionApplicationImplement AutoConfig or upgrade to the latest version. See Using AutoConfig to Manage System Configurations with Oracle Applications 11i on My Oracle Support for instructions.

    DirectX9.0bWindows customers ONLY - Database tierOn Windows, run the DirectX diagnostics tool DxDiag.exe in c:\windows\system32. If you receive a generic error opening the display adapter information, use the Windows update tool to upgrade to DirectX 9.0b.

    Attention
    Apply the interoperability patch and the necessary pre-requisite patches before performing the steps in the AutoConfig document. This ensures that you have the right code level when running AutoConfig.

  2. Migrate to Oracle Portal 10g (conditional)
    Oracle Portal 3.0.9 is not certified to run on Oracle Database 10g. If you plan to continue using Oracle Portal with Oracle E-Business Suite 11i, then the existing Oracle Portal functionality must be migrated to Oracle Portal 10g to ensure compatibility with Oracle Database 10g. Read and follow instructions in Installing Oracle Applications Server 10g with Oracle E-Business Suite Release 11i on My Oracle Support.

    You may remove Oracle Portal 3.0.9 and any dependencies from Oracle E-Business Suite by performing the steps in Remove Oracle Portal 3.0.9 from E-Business Suite Release 11i on My Oracle Support. Oracle Portal 3.0.9 should be removed only after the upgrade to Oracle Portal 10g, in order to ensure that any custom Portal data is successfully migrated.

  3. Update application tier context file with new database listener port number (conditional)
    The new 10.2.0 Oracle home uses its own database listener for the database instance, replacing the current database listener. Use the Context Editor to update the following variables in the Applications context file on each application tier server node to reflect the 10.2.0 configuration:

    Variable NameValue
    s_dbhostNew database hostname
    s_dbdomainNew database domain name
    s_db_serv_sidNew database SID
    s_dbportNew database listener port
    s_apps_jdbc_connect_descriptorNULL

    See Using AutoConfig to Manage System Configurations with Oracle Applications 11i on My Oracle Support for instructions on how to update and run the Context Editor.

    Attention
    Do not run AutoConfig on the application tier once the context file has been updated. Doing so will cut off the entire application tier from the database instance until after the upgrade is complete. You will be instructed to run AutoConfig on the application tier to configure the system for the new port number once the upgrade is finished and the new database listener is in use.

  4. Export OLAP analytical workspaces (conditional)
    If your database server node is on the 32-bit Solaris platform, perform detailed steps 1 to 4 of Upgrading OLAP from 32 to 64 bits on My Oracle Support.

Database Installation:

  1. Prepare to create the 10.2.0 Oracle home
    The 10.2.0 Oracle home must be installed on the database server node in a different directory than the current Oracle home.

    Read Chapters 1 and 2 of the Oracle Database Installation Guide 10g Release 2 (10.2) for your platform. Also read Chapter 1 and the "System Considerations and Requirements" section of Chapter 3 of the Oracle Database Upgrade Guide 10g Release 2 (10.2). Make sure you thoroughly understand the installation and upgrade processes. Perform any step that is relevant for your environment.

  2. Install the base 10.2.0 software
    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 Chapter 3 of the Oracle Database Installation Guide 10g Release 2 (10.2) for your platform.

    In the Installation Types window, use the Product Languages button to select any languages other than American English that are used by your Applications database instance. Choose the Enterprise Edition installation type. In the subsequent windows, select the options not to upgrade an existing database and to install the database software only.

    Attention
    You may ignore the errors when running utlu102i.sql as documented in 370825.1.

  3. Install Oracle Database 10g Products from the 10g Companion CD
    On the database server node, as the owner of the Oracle RDBMS file system and database instance, perform the tasks in section 3.5, "Installing Oracle Database 10g Products" in the Oracle Database Companion CD Installation Guide for your platform. Do not perform the tasks in the "Preparing Oracle Workflow Server for the Oracle Workflow Middle Tier Installation" section.

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

  4. Perform 10.2.0.5 patch set pre-installation tasks
    On the database server node, as the owner of the Oracle 10g file system and database instance, unzip and extract the 10.2.0.5 patch set file for your platform. Read the patch set notes (usually README.html). Make sure you thoroughly understand the upgrade and patch set installation process before you begin. Check My Oracle Support or contact Oracle Support Services to determine any known issues with the patch set and its interoperability with Oracle E-Business Suite.

    Perform the tasks in the "Preinstallation Tasks" section of the patch set notes (if they apply to your system).

  5. Perform 10.2.0.5 patch set installation tasks
    On the database server node, as the owner of the Oracle RDBMS file system and database instance, perform the tasks in the "Installing the Oracle Database 10g Patch Set Interactively" section of the patch set notes. Make sure that:
    • The ORACLE_HOME environment variable points to the new 10.2.0 Oracle home.
    • The PATH environment variable includes $ORACLE_HOME/bin and the directory where the new perl executable is located (usually $ORACLE_HOME/perl/bin).
    • The LD_LIBRARY_PATH environment variable includes $ORACLE_HOME/lib.
    • The PERL5LIB environment variable points to the directories where the new perl libraries are located (usually $ORACLE_HOME/perl/lib/[perl version] and $ORACLE_HOME/perl/lib/site_perl/[perl version])
    • You use the runInstaller (UNIX/Linux) or the setup.exe executable (Windows) provided in the patch set to run OUI.

  6. Create nls/data/9idata directory
    On the database server node, as the owner of the Oracle RDBMS file system and database instance, run the $ORACLE_HOME/nls/data/old/cr9idata.pl script to create the $ORACLE_HOME/nls/data/9idata directory.

    After creating the directory, make sure that the ORA_NLS10 environment variable is set to the full path of the 9idata directory whenever you enable the 10g Oracle home.

    Attention
    Check to make sure the $ORACLE_HOME/nls/data/9idata directory is created and is non-empty.

  7. Apply additional 10.2.0.5 RDBMS patches
    Apply the following patches:

    For all UNIX/Linux platforms, apply RDBMS patch 9726739.

    For all Windows platforms, apply Windows patch 1 - 32-bit, 64-bit or a later Windows patch.

    Attention
    While not mandatory for the interoperability of Oracle E-Business Suite with the Oracle Database, customers may choose to apply Database Patch Set Updates (PSU) on their Oracle E-Business Suite Database. If so, please see Document 1147107.1 ('Database Patch Set Update Overlay Patches Required for Use with PSUs and Oracle E-Business Suite') on My Oracle Support for more information.

Database Upgrade:

  1. Shut down Applications server processes and database listener
    On each application tier server node, shut down all server processes or services. On the database tier server node, shut down the Oracle Net or Net8 database listener in the old Oracle home.

    Note
    The Applications will be unavailable to users until all remaining tasks in this section are completed.

  2. Prepare to upgrade
    Read Chapter 2 of Oracle Database Upgrade Guide 10g Release 2 (10.2). Take note of the section pertaining to the Database Upgrade Assistant (DBUA).

    Attention
    If event="38004 trace name context forever, level 1" is defined in either the init[SID].ora initialization parameter file or the spfile[SID].ora server parameter file, remove it.

    Attention (Windows only)
    Make sure that the Services applet window is closed on the database server node. You cannot remove the current database instance service during the upgrade if this window is open.

    Attention
    Unset the TNS_ADMIN environment variable.

  3. Upgrade the database instance
    The instructions for the database upgrade are outlined in Oracle Database Upgrade Guide 10g Release 2 (10.2) Chapters 3 and 4.

    Perform the steps from the "Run the Pre-Upgrade Information Tool" section to the "Upgrade the Database Using the Database Upgrade Assistant" section of chapter 3.

    We recommend that you use 500 MB as the SYSAUX tablespace size. Set autoextend on for the SYSAUX tablespace.

    If you plan to change the PL/SQL compilation mode, disable the compilation of objects.

  4. Modify initialization parameters
    Use the following sections in document 216205.1, Database Initialization Parameters (init.ora settings) in Oracle Applications Release 11i on My Oracle Support as a guideline:

    • Common database initialization parameters
    • Release-specific database initialization parameters for 10gR2
    • Database initialization parameter sizing

    If System Managed Undo (SMU) is disabled in your database instance, ignore the initialization parameters that begin with "undo_". You will be instructed to configure them in the next step.

    If native compilation of PL/SQL code is disabled in your database instance, ignore the initialization parameters that pertain to the native compilation of PL/SQL code.

    Note
    There are many ways to generate the parameter file (for example, copying and updating an old init.ora parameter file). You are not confined to using the parameter files generated by the database upgrade assistant.

  5. Additional database configuration
    Ensure that System Managed Undo (SMU) is enabled in the database instance, and that the temporary tablespace is properly defined. In My Oracle Support document 216205.1, follow the instructions in these sections:

    • Release-specific database initialization parameters for 10gR2
    • Enabling System Managed Undo (SMU)
    • Temporary Tablespace Setup

  6. Perform 10.2.0.5 patch set post-installation tasks
    Review the "Postinstallation Tasks" section of the patch set notes. Perform the steps that are relevant for your database.

    Note
    Skip the sections "Upgrading Earlier Oracle Database to Oracle Database 10g Release 2 (10.2.0.5)", "Enabling Oracle Database Vault", and "Upgrading Oracle Database 10g Release 10.2.0.x to Oracle Database 10g Release 10.2.0.5" of the patch set notes.

  7. Install Oracle Data Mining and OLAP
    Note
    Restricted use licences for Oracle Data Mining and OLAP are included with Oracle Database Enterprise Edition for the purposes of upgrading existing E-Business Suite databases.

    Verify that Oracle Data Mining and OLAP are installed in your database by using SQL*Plus to connect to the database as SYSDBA and running the following command:

    SQL> connect / as sysdba; SQL> select comp_id from dba_registry where comp_id='ODM' or comp_id='AMD';

    If the query does not return ODM, then you do not have Oracle Data Mining installed. To install Data Mining, use SQL*Plus to connect to the database as SYSDBA and run the following command:

    SQL> connect / as sysdba; SQL> @$ORACLE_HOME/rdbms/admin/dminst.sql SYSAUX TEMP

    If the query does not return AMD, then you do not have OLAP installed. To install OLAP, use SQL*Plus to connect to the database as SYSDBA and run the following command:

    SQL> connect / as sysdba; SQL> @$ORACLE_HOME/olap/admin/olap.sql SYSAUX TEMP

  8. Natively compile PL/SQL code (optional)
    If you are not on the Windows Itanium platform, you can choose to run Oracle E-Business Suite 11i PL/SQL database objects in natively compiled mode with Oracle Database 10g. See the "Compiling PL/SQL Code for Native Execution" section of Chapter 11 of Oracle Database PL/SQL User's Guide and Reference 10g Release 2 (10.2).

    When modifying the initialization parameters pertaining to the PL/SQL native compilation, use document 216205.1, on My Oracle Support as a guideline. You can set the plsql_native_library_subdir_count parameter as described in the PL/SQL user's guide. Create the associated subdirectories for the given plsql_native_library_dir and plsql_native_library_subdir_count parameters.

After the Database Upgrade:

  1. Fix Korean lexers
    Use SQL*Plus to connect to the database as SYSDBA, and run drkorean.sql using the following command:
    $ sqlplus "/ as sysdba" @$ORACLE_HOME/ctx/sample/script/drkorean.sql

  2. Import OLAP analytical workspaces (conditional)
    If your database server node was upgraded from the 32-bit Solaris platform, perform detailed steps 7 and 8 of Upgrading OLAP from 32 to 64 bits on My Oracle Support.

  3. Start the new database listener (conditional)
    If the Oracle Net listener for the database instance in the new Oracle home has not been started, you must start it now. Since AutoConfig has not yet been implemented, start the listener with the lsnrctl executable (UNIX/Linux) or Services (Windows). See the Oracle Database Net Services Administrator's Guide, 10g Release 2 (10.2) for more information.

    Attention
    Set the TNS_ADMIN environment variable to the directory where you created your listener.ora and tnsnames.ora files.

  4. Run adgrants.sql (conditional)
    If you have at least AD.I or E-Business Suite release 11.5.10 installed on your system, copy $APPL_TOP/admin/adgrants.sql (adgrants_nt.sql for Windows) from the administration server node to the database server node. Use SQL*Plus to connect to the database as SYSDBA and run the script using the following command:
    $ sqlplus "/ as sysdba" @adgrants.sql (or adgrants_nt.sql)      [APPS schema name]

    Note
    Verify the usage of adgrants.sql in the adgrants.sql script. Older versions of adgrants.sql require the APPLSYS schema name parameter to be passed instead of APPS.

  5. Grant create procedure privilege on CTXSYS
    Copy $AD_TOP/patch/115/sql/adctxprv.sql from the administration server node to the database server node. If you are upgrading to R12, use the R12 version of the file. Use SQL*Plus to connect to the database as APPS and run the script using the following command:
    $ sqlplus apps/[APPS password] @adctxprv.sql \     [SYSTEM password] CTXSYS

  6. Deregister the previous database server (conditional)
    If you plan to change the database port, host, SID, or database name parameter on the database server, you must also update AutoConfig on the database tier and deregister the previous database server node.

    Use SQL*Plus to connect to the database as APPS and run the script using the following command:

    $ sqlplus apps/[APPS password]  SQL> exec fnd_conc_clone.setup_clean;

  7. Implement and run AutoConfig
    Implement and run AutoConfig in the new Oracle home on the database server node. If the database listener of the new Oracle home is defined differently than the old Oracle home, you must also run AutoConfig on each application tier server node to update the system with the new listener.

    See Using AutoConfig to Manage System Configurations with Oracle Applications 11i on My Oracle Support for instructions on how to implement and run AutoConfig.

    Shut down all processes, including the database and the listener, and restart them to load the new environment settings.

  8. Gather statistics for SYS schema
    Copy $APPL_TOP/admin/adstats.sql from the administration server node to the database server node. If you are upgrading to R12, use the R12 version of the file. Note that adstats.sql has to be run in restricted mode. Use SQL*Plus to connect to the database as SYSDBA and use the following commands enable restricted mode, run adstats.sql, and disable restricted mode:
    $ sqlplus "/ as sysdba" SQL> alter system enable restricted session; SQL> @adstats.sql  SQL> alter system disable restricted session; SQL> exit;

    Note
    Make sure that you have at least 1.5 GB of free default temporary tablespace.

  9. Re-create custom database links (conditional)
    If the Oracle Net listener in the 10.2.0 Oracle home is defined differently than the one used by the old Oracle home, you must re-create any custom 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;
    The EDW_APPS_TO_WH and APPS_TO_APPS database links, if they exist, should have been updated with the new port number by AutoConfig in the previous step.

    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=[hostname])      (PORT=[port number]))(CONNECT_DATA=(SID=[ORACLE_SID])))';
    where [custom database link], [user], [password], [hostname], [port number], and [ORACLE_SID] reflect the new Oracle Net listener for the database instance.

  10. Re-create grants and synonyms
    Oracle Database 10g Release 2 (10.2) contains new functionality for grants and synonyms compared to previous database releases. As a result, you must re-create the grants and synonyms in the APPS schema. 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" task from the Maintain Applications Database Objects menu.

    If MRC is implemented in your Applications system, then run the "Maintain Multiple Reporting Currencies schema" task to re-create MRC triggers in the Apps schema.

  11. Apply Oracle Receivables patch
    Apply Oracle Receivables patch 5753621.

  12. Restart Applications server processes (conditional)
    Restart all the Application tier server processes that you shut down previously. Remember that the Oracle Net listener for the database instance, as well as the database instance itself, need to be started in the 10.2 Oracle home. Users may return to the system.

Section 2: Upgrading an Existing Oracle Database 10g Release 2 (10.2.0) patch set


Follow the instructions in this section if you have an Oracle E-Business Suite Release 11i system using Oracle 10g Release 2 (10.2.0) and you wish to apply the latest certified Oracle 10g Release 2 (10.2.0) patch set to it.

  1. Upgrade to DirectX version 9.0b (conditional)
    If you are on a Windows platform, run the DirectX diagnostics tool DxDiag.exe in c:\windows\system32. If you run this tool and it displays a generic error opening the display adapter information, use the Windows Update tool to upgrade to DirectX 9.0b.

  2. Perform 10.2.0.5 Patch Set preinstallation tasks (conditional)
    On the database server node, as the owner of the Oracle 10g file system and database instance, unzip and extract the patch set file appropriate for your platform. Read the patch set notes (usually README.html) and make sure that you thoroughly understand the patch set installation process before you begin. Check My Oracle Support or contact Oracle Support Services to determine any known issues with the patch set and its interoperability with Oracle E-Business Suite.

    Perform the tasks in the "Preinstallation Tasks" section of the patch set notes (if they apply to your system).

  3. Shut down Applications server processes
    Shut down all Applications and database server processes. The Applications will be unavailable to users until all tasks in this section are completed.

  4. Disable Database Vault (conditional)
    If you have Database Vault installed, perform steps 1 and 2 of Section 5 of document 428503.1 on My Oracle Support to disable Database Vault.

  5. Perform 10.2.0.5 Patch Set installation tasks
    On the database server node, as the owner of the Oracle RDBMS file system and database instance, perform the tasks in the "Installing the Oracle Database 10g Patch Set Interactively" section of the patch set notes. Make sure that you use the runInstaller (UNIX/Linux) or the setup.exe executable (Windows) provided in the patch set to run OUI.

    Do not perform the "Postinstallation Tasks" section yet.

  6. Perform 10.2.0.5 Patch Set postinstallation tasks
    Review the "Postinstallation Tasks" section of the patch set notes. Perform the steps that are relevant for your database.

    Note
    Skip the sections "Upgrading Earlier Oracle Database to Oracle Database 10g Release 2 (10.2.0.5)" and "Enabling Oracle Database Vault" of the patch set notes.

  7. Apply additional 10.2.0.5 RDBMS patches
    Apply the following RDBMS patches to the 10.2.0 Oracle home:

    For all UNIX/Linux platforms, apply RDBMS patch 9726739.

    For all Windows platforms, apply Windows patch 1 - 32-bit, 64-bit or a later Windows patch.

    Attention
    While not mandatory for the interoperability of Oracle E-Business Suite with the Oracle Database, customers may choose to apply Database Patch Set Updates (PSU) on their Oracle E-Business Suite Database. If so, please see Document 1147107.1 ('Database Patch Set Update Overlay Patches Required for Use with PSUs and Oracle E-Business Suite') on My Oracle Support for more information.

  8. Gather statistics for SYS schema
    Copy $APPL_TOP/admin/adstats.sql from the administration server node to the database server node. Note that adstats.sql has to be run in restricted mode. Use SQL*Plus to connect to the database as SYSDBA and use the following commands to restart the database in restricted mode, run adstats.sql, and restart the database in normal mode:
    $ sqlplus "/ as sysdba" SQL> shutdown normal; SQL> startup restrict; SQL> @adstats.sql  SQL> shutdown normal; SQL> startup;  SQL> exit;

    Note
    Make sure that you have at least 1.5 GB of free default temporary tablespace.

  9. Apply Oracle Receivables patch
    Apply Oracle Receivables patch 5753621.

  10. Enable Database Vault (conditional)
    If you disabled Database Vault, enable it by performing steps 4 and 5 of Section 5 of document 428503.1 on My Oracle Support.

  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.

Change Log
DateDescription
March 30, 2006
  • First Posting
June 1, 2006
  • Added patch 5004076 for Linux x86-64.
  • Added note to skip section 7.2 of the patch set notes.
August 15, 2006
  • Added patch 5043440 for Windows x86-64.
October 31, 2006
  • Modified the 10g Companion CD section.
December 1, 2006
  • Added Tru64 related steps.
January 24, 2007
  • Added R12 updates.
March 19, 2007
  • Removed conditional statements.
  • Changed Korean lexers to step 21.
April 11, 2007
  • 10.2.0.3 updates.
April 13, 2007
  • Modified section 2 postinstallation tasks to skip section 7.1.
July 6, 2007
  • Windows Itanium certification for 10.2.0.3.
  • Allowing Windows 32 for native compilation.
September 4, 2007
  • Windows x64 certification for 10.2.0.3.
November 27, 2007
  • zLinux certification for 10.2.0.3.
  • Added patches 5871314 and 5755471.
  • Changed step number references in OLAP document.
  • Added reference to 370825.1.
June 6, 2008
  • Added licensing info for OLAP and Data Mining
July 15, 2008
  • 10.2.0.4 updates
October 21, 2008
  • Database vault info modified
November 17, 2008
  • Added connection to SYSDBA in ODM/OLAP examples
December 17, 2008
  • Updated sections 10.1, 10.4, 10.7 to section names.
April 30, 2009
  • Added required patch 6600051.
July 21, 2009
  • Added OPatch 6880880.
  • Added Windows patches corresponding to 6600051.
  • Added attention statement to double check contents of $ORACLE_HOME/nls/data/9idata.
August 19, 2009
  • Added patches 6521934, 7496636, 7497678
  • Requiring Windows patch 24
  • Removed conditional in applying 10.2.0.4 RDBMS patches.
January 11, 2010
  • Changed references from OracleMetaLink to My Oracle Support
  • Added requirement for patch 7441176 and Windows patch 24 for Itanium
  • Changed ordering of applying additional 10.2.0.4 RDBMS patches and performing 10.2.0.4 patch set postinstallation tasks in Section 2.
  • Added in Section 1 that running patch postinstall steps are not needed.
July 2, 2010
  • Update for 10.2.0.5.
  • Added iStore patch 6400762.
  • Updated adgrants.sql to run with APPS schema name parameter instead of APPLSYS.
August 13, 2010
  • Added RDBMS patch 9726739.
  • Moved deregistering of database server to "Database Upgrade" section.
October 5, 2010
  • Added 10.2.0.5 Windows patch requirements
November 29, 2010
  • Added reference to 1147107.1 regarding PSU patch list
February 17, 2011
  • Removed 11.5.9 references as 10.2.0.5 is not certified with 11.5.9.
  • Replaced pre-upgrade adgentns.pl step with post-upgrade fnd_conc_clone step.
Note 362203.1 by Oracle Applications Development
Copyright 2006 Oracle Corporation
Last updated: Thu February 17, 2011

Show Related Information Related

Products
  • Oracle E-Business Suite > Applications Technology > Technology Components > Oracle Applications Technology Stack

Back to topBack to top

Posted by at

No comments:

Post a Comment

Subscribe to: Post Comments (Atom)