Thursday, May 12, 2011

Oracle Applications Release 11i with Oracle 11g Release 1 (11.1.0)


Oracle Applications Release 11i with Oracle 11g Release 1 (11.1.0) [ID 452783.1]
Modified 29-NOV-2010 Type WHITE PAPER Status PUBLISHED


View Change log

Interoperability Notes

Oracle E-Business Suite Release 11i
with Oracle Database 11g Release 1 (11.1.0)

November 2010

This note is the master document describing the use of Oracle E-Business Suite Release 11i with Oracle Database 11g Release 1 (11.1.0.x), where x denotes the patch set level (currently 7). It may refer to related interoperbility notes, which you should review if they apply to your specific release of the Oracle Database. The most current version of this document is Note 452783.1 on My Oracle Support.

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

11.1.0.6 Interoperability Notes

Attention
Oracle E-Business Suite releases prior to 11.5.10 Consolidated Update patch 2 are not certified with Oracle Database 11g Release 1 (11.1.0). Check My Oracle Support to make sure that your platform and environment configuration are certified with Oracle Database 11g before performing any instruction in this document.

Attention
If you are going to use 11g Real Application Clusters (RAC) or Automatic Storage Management (ASM), see Using Oracle 11g Release 1 Real Application Clusters and Automatic Storage Management with Oracle E-Business Suite Release 11i on My Oracle Support.

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 11.1.0.7 patch set from patch 6890831 on My Oracle Support.

This document contains the following sections:

Section 1: Upgrading an E-Business Suite 11i Database to Oracle Database 11g Release 1 (11.1.0)


Follow the instructions in this section if you have an Oracle E-Business Suite Release 11i system using Oracle9i Release 2 (9.2.0), Oracle 10g Release 1 (10.1.0), or Oracle 10g Release 2 (10.2.0) and you wish to upgrade the database server and instance to Oracle Database 11g Release 1 (11.1.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" subsection in Chapter 2 of theOracle Database Upgrade Guide 11g Release 1 (11.1). Make sure that direct upgrade is supported from your current release.
    Oracle E-Business Suite11.5.10 CU2ApplicationApply
    ATG Rollup Patch6ApplicationApply patch 5903765. Also apply patch 7456837.
    Developer 6iPatch set 18ApplicationIf your patch set level is earlier than patch set 18, apply the latest certified patch set. See Upgrading Developer 6i with Oracle Applications 11i on My Oracle Support.
    AutoConfigLatest version with 7011280ApplicationImplement AutoConfig or upgrade to the latest version. See Using AutoConfig to Manage System Configurations with Oracle Applications 11i on My Oracle Support for instructions. You must run AutoConfig on both the database and application tiers. Also apply patch 7011280.

    Daylight Saving changes
    		Database tierSee Complying with Daylight Saving Time (DST) and Time Zone Rule Changes in E-Business Suite 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.

    Attention
    ATG Rollup patch 6 has a prerequisite to upgrade the database version to 9.2.0.8 or higher. Ensure that all the prerequisites are completed before upgrading to 11g.
  2. Apply GL patch 6815663 (conditional)
    If the Applications tier is on the Windows platform, apply patch 6815663.

  3. Migrate to Oracle Portal 10g (conditional)
    Oracle Portal 3.0.9 is not certified with Oracle Database 11g. 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 11g. 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.

  4. Deregister the current 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 current database server node.

    To update AutoConfig on the database tier, follow the instructions in Using AutoConfig to Manage System Configurations with Oracle Applications 11i on My Oracle Support.

    To deregister the current database server node, run the following command as the owner of the Oracle RDBMS file system and current database instance:

    $ perl $ORACLE_HOME/appsutil/bin/adgentns.pl    appspass=[APPS db user password]    contextfile=$CONTEXT_FILE -removeserver

  5. Update application tier context file with new database listener port number (conditional)
    The new 11.1.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 11.1.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.

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

Database Installation:

  1. Prepare to create the 11.1.0 Oracle home
    The 11.1.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 11g Release 1 (11.1) for your platform. Also read Chapter 1 and the "System Considerations and Requirements" section of Chapter 3 of the Oracle Database Upgrade Guide 11g Release 1 (11.1). Make sure you thoroughly understand the installation and upgrade processes. Perform any step that is relevant for your environment.

  2. Install the base 11.1.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 11g Release 1 (11.1) 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.

  3. Install Oracle Database 11g Products from the 11g Examples CD
    On the database server node, as the owner of the Oracle RDBMS file system and database instance, perform the tasks in section 3, "Download Oracle Database Examples" in the Oracle Database Examples CD Installation Guide.

    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.

    After the installation, make sure that:

    • The ORACLE_HOME environment variable points to the new 11.1.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])

  4. Perform 11.1.0.7 patch set pre-installation tasks
    On the database server node, as the owner of the Oracle 11g file system and database instance, unzip and extract the 11.1.0.7 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 11.1.0.7 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 11g 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.

  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 11g Oracle home.

  7. Apply additional 11.1.0.7 RDBMS patches
    Apply the following RDBMS patches to the 11.1.0 Oracle home:

    For all UNIX/Linux platforms, apply the following RDBMS patches:

    For Windows platforms, apply patch 4 - 32-bit, 64-bit or a later patch set.

    Attention
    Do not apply any of the patch special instructions. They will be done after the database upgrade.

    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 11g Release 1 (11.1). Take note of the section pertaining to the Database Upgrade Assistant (DBUA).

    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.

  3. Upgrade the database instance
    The instructions for the database upgrade are outlined in Oracle Database Upgrade Guide 11g Release 1 (11.1) 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 and any step in chapter 4 that is relevant to your environment.

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

    When upgrading all statistics tables, note that Oracle E-Business Suite has only one statistics table, APPLSYS.FND_STATTAB, that needs to be upgraded.

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

  4. Modify initialization parameters
    Use the following sections in Note 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 11gR1
    • Database initialization parameter sizing

    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 unless you are on the HP Itanium platform.

    Attention
    For the HP Itanium platform, set plsql_native_library_dir to a valid directory and plsql_native_library_subdir_count to 149. These parameters are required whether you are running in native or interpreted mode.

    Ensure that the temporary tablespace is properly defined. Follow the instructions in the Temporary Tablespace Setup section.

    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. Perform 11.1.0.7 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 sections 9.1, 9.2, and 9.12 of the patch set notes.

  6. Natively compile PL/SQL code (optional)
    You can choose to run Oracle E-Business Suite 11i PL/SQL database objects in natively compiled mode with Oracle Database 11g. See the "Compiling PL/SQL Program Units for Native Execution" section of Chapter 12 of Oracle Database PL/SQL Language Reference 11g Release 1 (11.1).

After the Database Upgrade:

  1. Fix Korean lexers (conditional)
    If you upgraded from 10.1.0 or previous releases, 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 4 and 5 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, 11g Release 1 (11.1) 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
    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. 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.

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

  8. Re-create custom database links (conditional)
    If the Oracle Net listener in the 11.1.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.

  9. Re-create grants and synonyms
    Oracle Database 11g Release 1 (11.1) 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.

  10. 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 11.1 Oracle home. Users may return to the system.

Section 2: Applying an Existing Oracle Database 11g Release 1 (11.1.0) patch set


Follow the instructions in this section if you have an Oracle E-Business Suite Release 11i system using Oracle 11g Release 1 (11.1.0) and you wish to apply the latest certified Oracle 11g Release 1 (11.1.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 11.1.0.7 Patch Set preinstallation tasks (conditional)
    On the database server node, as the owner of the Oracle 11g 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. Perform 11.1.0.7 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 11g 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.

  5. Perform 11.1.0.7 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 sections 9.1 and 9.12 of the patch set notes.

  6. Apply additional 11.1.0.7 RDBMS patches
    Apply the following RDBMS patches to the 11.1.0 Oracle home:

    For all UNIX/Linux platforms, apply the following RDBMS patches:

    For Windows platforms, apply patch 4 - 32-bit, 64-bit or a later patch set.

    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.

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

  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.

Section 3: Unsupported Products


Oracle Enterprise Planning and Budgeting (EPB) is currently not supported with E-Business Suite 11i on Database 11g.

Section 4: Known Issues


The following are known issues with E-Business Suite 11i on Database 11g:
  1. Customers using Dell hardware

    For customers using Dell hardware, see Note 555036.1 on My Oracle Support. This affects functionality which uses the 11g JDBC such as AutoConfig on the database tier (for more details, refer to bug 6485149.

  2. Uploading images to HRMS system

    For customers using the HRMS system, see Note 785448.1 on My Oracle Support.

Change Log
DateDescription
March 25, 2008
  • First Posting
April 1, 2008
  • Added patch 6501565 to fix bug 6905885. This fixes the error 'FRM-40735: ON-ERROR trigger raised unhandled exception ORA-01001' when running INV Miscellaneous Transaction and WIP Move Transaction forms.
  • Added note to apply patch special instructions only for 6501565.
  • Added 6318357, 6454237, 6633314, 6633347 for Windows.
April 4, 2008
  • Changed MSD, EPB support info.
  • Updated UNIX patch requirements.
  • Added step to perform patch special instructions.
April 10, 2008
  • Updated Database Vault support info.
April 16, 2008
  • Updated BSC support info.
April 21, 2008
  • Changed patch requirement 6670485 and 6636451 to 6459753
  • Changed EPB support info.
June 26, 2008
  • Added RAC information.
  • Modified Oracle Database Examples installation step.
  • Updated Windows patch 1 requirement to patch 3.
July 3, 2008
  • Added Windows x64 information.
July 30, 2008
  • Added 6972189, 6899909, 6459753 for UNIX/Linux.
  • Removed MSD from unsupported list of products.
  • Required 2 additional plsql initialization parameters.
  • Removed forms compilation issues from the known issues section.
December 18, 2008
  • Added Windows patch 12 and 7253531.
December 24, 2008
  • Updated for 11.1.0.7 certification.
February 11, 2009
  • Updated for 11.1.0.7 certification for Windows 32-bit.
  • Added patch 6972189
March 9, 2009
  • Updated for 11.1.0.7 certification for Windows 64-bit.
  • Modified GL patch to 6815663.
  • Added uploading images into HRMS known issue.
May 21, 2009
  • Added patch 7456837.
  • Modified DST note from 359145.1 to 458452.1
November 29, 2010
  • Changed references from MetaLink to My Oracle Support.
  • Added 11.1.0.7 patches 6815733, 8940108 and 9743057.
  • Added statement in Section 1 to disregard patch special instructions.
  • Moved patch set postinstallation tasks in Section 2 to run before application of RDBMS patches.
  • Added reference to 1147107.1 regarding PSU patch list.
  • Modified adgrants.sql to run with parameter APPS instead of APPLSYS
Note 452783.1 by Oracle Applications Development
Copyright 2008 Oracle Corporation
Last updated: Mon Nov 29, 2010

Show Related Information Related

Products
  • Oracle E-Business Suite > Applications Technology > Technology Components > Oracle Applications Technology Stack
Keywords
E-BUSINESS; 11GR1; UPGRADE
Errors
FRM-40735; ORA-1001

Back to topBack to top

Posted by at

No comments:

Post a Comment

Subscribe to: Post Comments (Atom)