Interoperability Notes Oracle EBS 11i with Oracle Database 11gR2 (11.2.0.2) [ID 881505.

1] Modified 20-MAY-2011 Type WHITE PAPER Status PUBLISHED View Change log Interoperability Notes Oracle E-Business Suite Release 11i with Oracle Database 11g Release 2 (11.2.0) May 2011 This note is the master document describing the use of Oracle EBusiness Suite Release 11i with Oracle Database 11g Release 2 (11.2.0.x), where x denotes the patch set level (currently 2). 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 881505.1 on My Oracle Support. Attention Interoperability notes of previous patch sets are available through the following links: 11.2.0.1 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 2 (11.2.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 2 Real Application

Clusters 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.2.0.2 patch set from patch 10098816 on My Oracle Support. This document contains the following sections:

Section 1: Upgrading an E-Business Suite 11i Database to Oracle Database 11g Release 2 (11.2.0) Instructions for upgrading an Oracle E-Business Suite Release 11i database server and instance from Oracle9i Release 2 (9.2.0), Oracle 10g Release 1 (10.1.0), Oracle 10g Release 2 (10.2.0), Oracle Database 11g Release 1 (11.1.0), or earlier versions of Oracle Database 11g Release 2 (11.2.0) to the latest version of Oracle Database 11g Release 2 (11.2.0).

Subsections: Before the Database Installation Database Installation Database Upgrade After the Database Upgrade

Section 2: Unsupported Products This section lists products that are currently not supported with Oracle E-Business Suite Release 11i on Oracle Database 11g. Section 3: Known Issues This section lists known issues with Oracle E-Business Suite Release 11i on Oracle Database 11g.

Section 1: Upgrading an E-Business Suite 11i Database to

Oracle Database 11g Release 2 (11.2.0) Follow the instructions in this section if you plan to upgrade the database server and instance to Oracle Database 11g Release 2 (11.2.0). Before the Database Installation: 1. Verify software versions The following software component versions must exist in your environment. Minimu Software m Tier Version Oracle Database Enterpris e Edition Details

Database Read the "Determine the Upgrade Path" subsection in Chapter 2 of theOracle Database Upgrade Guide 11g Release 2 (11.2). Make sure that direct upgrade is supported from your current release.

Oracle E- 11.5.10 Applicatio Apply Business CU2 n Suite

11.5.10 E-Business Suite Consolidated Update 2 11g Release 2 interoperability patch for 11.5.10 (8815204) Patch 5644137 If you are using Oracle iStore (IBE) Patch 6400762

o o

ATG Rollup Patch

Applicatio Apply patch 5903765. Also n apply patch 7456837. Applicatio If your patch set level is earlier than n patch set 18, apply the latest certified patch set. See Upgrading

Develope Patch r 6i set 18

Developer 6i with Oracle Applications 11i on My Oracle Support. AutoConfi Latest Applicatio g version n with 9835302 Implement 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 9835302.

Daylight Saving changes

Database See Complying with Daylight tier Saving Time (DST) and Time Zone Rule Changes in E-Business Suite on My Oracle Support for instructions. 9.0b Windows On Windows, run the DirectX custome diagnostics tool DxDiag.exe in rs ONLY c:\windows\system32. If you receive -Database a generic error opening the display tier adapter information, use the Windows update tool to upgrade to DirectX 9.0b.

DirectX

Attention The interoperability patch requires TXK RUP-U. When performing the instructions implementing AutoConfig, apply TXK RUP-U (or a later version of TXK) then apply the interoperability patch before running AutoConfig. This ensures that you have the right code level when running AutoConfig. 3. Apply GL patch 6815663 (conditional) If the Applications tier is on the Windows platform, apply patch 6815663. 4. 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 11ion 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. 5. Update application tier context file with new database listener port number (conditional) The new 11.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 11.2.0 configuration: Variable Name s_dbhost s_dbdomain s_db_serv_sid s_dbport Value New database hostname New database domain name New database SID New database listener port

s_apps_jdbc_connect_descri NULL ptor 6. 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. Database Installation: 5. Prepare to create the 11.2.0 Oracle home The 11.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 11g Release 2 (11.2) 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 2 (11.2). Make sure you thoroughly understand the installation and upgrade processes. Perform any step that is relevant for your environment. Attention For HP Itanium and HP PA RISC platforms using the NFS file system, choose a disk to install the 11g Oracle home separate from the database files. The mount options of the disk containing the database files must include forcedirectio. The 11g Oracle home (or any other binaries) must not include the forcedirectio mount option. 6. Install the 11.2.0.2 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 4 of the Oracle Database Installation Guide 11g Release 2 (11.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. 7. 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 4, "Download Oracle Database Examples" in the Oracle Database Examples 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:
o

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

8. 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. 9. Apply additional 11.2.0.2 RDBMS patches For UNIX/Linux platforms, apply RDBMS patches
o o

10149223 10229719

For Windows platforms, apply patch 1 - 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 EBusiness Suite') on My Oracle Support for more information. Attention Do not apply any of the patch special instructions. The scripts are run as part of the upgrade. Database Upgrade: 10.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. Attention Make sure that you do not have the LOCAL_LISTENER initialization parameter set to ensure that the database does not inadvertently point to a non-existent listener during upgrade. 12.Drop SYS.ENABLED$INDEXES (conditional) If the SYS.ENABLED$INDEXES table exists, use SQL*Plus to connect to the database as SYSDBA and running the following command to drop it: 13.SQL> drop table sys.enabled$indexes; 14.Disable Database Vault (conditional) If you have Database Vault installed, perform steps 1 to 6 of Part 2 of document 1091086.1 on My Oracle Support to

disable Database Vault. 15.Prepare to upgrade Read Chapter 2 of Oracle Database Upgrade Guide 11g Release 2 (11.2). 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. 16.Upgrade the database instance The instructions for the database upgrade are outlined in Oracle Database Upgrade Guide 11g Release 2 (11.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 and any step in chapter 4 that is relevant to your environment. In Oracle Database 11g, the DMSYS schema is no longer used. The Data Mining option is installed in the SYS schema. The 11.2 preupgrade tool has been extended to include a warning that the DMSYS schema should be dropped. If this warning is reported, it is recommended to drop the schema as per the Oracle Data Mining Administrator's Guide 11g Release 2 (11.2). Removing the DMSYS schema has no effect on the functioning of Data Mining. 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. 17.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:

o o

Common database initialization parameters Release-specific database initialization parameters for 11gR2 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. 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. 18.Install OLAP Note Restricted use licences for OLAP are included with Oracle Database Enterprise Edition for the purposes of upgrading existing E-Business Suite databases. The interdependence of products and database objects in the Oracle E-Business Suite require that this step be performed. While not all EBS products use the OLAP schema, this step is needed to prevent errors while performing installations, upgrades, or patching of database objects. 19.Verify that OLAP is installed in your database by using SQL*Plus to connect to the database as SYSDBA and running the following command: 20.SQL> connect / as sysdba; 21.SQL> select comp_id from dba_registry where comp_id='AMD'; 22.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:

23.SQL> connect / as sysdba; 24.SQL> @$ORACLE_HOME/olap/admin/olap.sql SYSAUX TEMP 25.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 2 (11.2). After the Database Upgrade: 18.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: 19.$ sqlplus "/ as sysdba" @$ORACLE_HOME/ctx/sample/script/drkorean.sql 20.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 2 (11.2) for more information. Attention Set the TNS_ADMIN environment variable to the directory where you created your listener.ora and tnsnames.ora files. 21.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: 22.$ sqlplus "/ as sysdba" @adgrants.sql (or adgrants_nt.sql) 23. [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. 24.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: 25.$ sqlplus apps/[APPS password] @adctxprv.sql \ 26. [SYSTEM password] CTXSYS

27.Set CTXSYS parameter Use SQL*Plus to connect to the database as SYSDBA and run the following command: 28.$ sqlplus "/ as sysdba" 29.SQL> exec ctxsys.ctx_adm.set_parameter('file_access_role', 'public'); 30.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. Use SQL*Plus to connect to the database as APPS and run the following command: $ sqlplus apps/[APPS password] SQL> exec fnd_conc_clone.setup_clean; 31.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. 32.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: 33.$ sqlplus "/ as sysdba" 34.SQL> shutdown normal; 35.SQL> startup restrict; 36.SQL> @adstats.sql 37.SQL> shutdown normal; 38.SQL> startup; 39.SQL> exit; Note Make sure that you have at least 1.5 GB of free default temporary tablespace. 40.Re-create custom database links (conditional) If the Oracle Net listener in the 11.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: 41.$ sqlplus apps/[apps password] 42.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. 43.Apply Oracle Human Resources (HRMS) patch 7721754 (conditional) If you are using Oracle HRMS, apply patch 7721754. 44.Re-create grants and synonyms Oracle Database 11g Release 2 (11.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. 45.Enable Database Vault (conditional) If you disabled Database Vault, enable it by performing step 7 of Part 2 of document 1091086.1 on My Oracle Support. 46.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.2 Oracle home.

Users may return to the system. Section 2: Unsupported Products The following products are not supported with E-Business Suite 11i on Database 11g: 1. Oracle Demand Planning (ODP) 2. Oracle Enterprise Planning and Budgeting (EPB) 3. Oracle Enterprise Data Warehouse (EDW) 4. Oracle Balance Scorecard Expert (BSC Expert). Section 3: Known Issues The following are known issues with E-Business Suite 11i on Database 11g: 1. Customers may encounter: 'ORA-29532: Java call terminated by uncaught Java exception: java.lang.NullPointerException' while using the DBMS_XMLQUERY package. This issue is tracked under bug 8814854 on My Oracle Support. Products where this issue has occurred are Oracle Labor Distribution (OLD) and Oracle iRecruitment (IRC). Workaround for this issue is available under Note 833237.1. 2. Customers will see the error: 'oracle.apps.fnd.oam.bobj.database.InitMetadataException: No matched database version found in the init.ora metadata for 11.2.0.1.0'. while accessing Database Init.ora settings for "Recommended/Mandatory Init.ora Parameters" in System Configuration Overview page from Oracle Applications Manager. Please review bug 8946396 on My Oracle Support for updated information on this issue.

3. Customers upgrading from 9i may encounter the issue mentioned in Note 1225653.1. It is recommended to set SGA to less than 1G. Change Log Date October 7, 2009 December 4, 2009 February 4, 2010 Description

First Posting

Modified references to OracleMetaLink to My Oracle Support. Created section for information on certified platforms. Added EBS patches 9320007, 5644137 Listed 8405205 as only required for Linux and Linux x86-64 Listed Solaris SPARC 10 in list of certified platforms Added EBS patch 6400762 Removed table of certified platforms as it is now available in Support. Removed ADI from list of unsupported products Removed DBI from list of unsupported products Added AutoConfig patch 9494547 Added Windows instructions for Windows 32 and x64 certification on 11.2.0.1 Added patch 8897784 Added AutoConfig patch 9835302. Removed AutoConfig patches 9320007 and 9494547 as they are included in TXK-U. Updated for 11.2.0.2 Added attention statement regarding forcedirectio mount

March 1, 2010

March 3, 2010 April 16, 2010

May 25, 2010

July 19, 2010

November 15, 2010

option.

Moved step to deregister Oracle home to "Database Upgrade" section Added steps related to Database Vault Added reference to 1147107.1 regarding PSU patch list. Added Attention statement to unset LOCAL_LISTENER. Changed Database Examples reference from Section 3 to Section 4. Added RDBMS patch 10229719. Added 11.2.0.2 Windows 32-bit and x64 certification. Changed pre-upgrade adgentns.pl step to post-upgrade fnd_conc_clone. Changed 6400762 to a conditional patch on iStore users. Added ODP to list of unsupported products. Added reference to note 1225653.1 under known issues section. Removed running of dminst.sql. Added statement to remove DMSYS schema. Added ATG patch 7456837 requirement. Changed Chapter 3 Oracle Database Installation Guide reference to Chapter 4.

December 10, 2010

February 24, 2011

May 19, 2011

Note 881505.1 by Oracle Applications Development Copyright 2009 Oracle Corporation Last updated: Thu May 19, 2011

Related Products

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

Errors ORA29532 Back to top