This action might not be possible to undo. Are you sure you want to continue?
Oracle E-Business Suite Release 11i with Oracle Database 11g Release 2 (11.2.0)
This note is the master document describing the use of Oracle E-Business Suite Release 11i with Oracle Database 11g Release 2 (11.2.0.x), where x denotes the patch set level (currently 3). 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: 126.96.36.199 Interoperability Notes 188.8.131.52 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.
0) Follow the instructions in this section if you plan to upgrade the database server and instance to Oracle Database 11g Release 2 (11.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. Verify software versions The following software component versions must exist in your environment. Software Oracle Database Enterprise Edition Minimum Version Tier Database Details Read the "Determine the Upgrade Path" subsection in Chapter 2 of the Oracle Database Upgrade Guide 11g Release 2 (11.0). Oracle Database 11g Release 1 (11.2).2. Section 1: Upgrading an E-Business Suite 11i Database to Oracle Database 11g Release 2 (11.2.Attention You can obtain the 11. Oracle 10g Release 1 (10.2.1.2. Before the Database Installation: 1. .2. Section 3: Known Issues This section lists known issues with Oracle E-Business Suite Release 11i on Oracle Database 11g.0). Make sure that direct upgrade is supported from your current release.2.1. or earlier versions of Oracle Database 11g Release 2 (11.3 patch set from patch 10404530 on My Oracle Support.0).0.0) Instructions for upgrading an Oracle E-Business Suite Release 11i database server and instance from Oracle9i Release 2 (9.2. Oracle 10g Release 2 (10.2.0).0).0) to the latest version of Oracle Database 11g Release 2 (11. This document contains the following sections: • Section 1: Upgrading an E-Business Suite 11i Database to Oracle Database 11g Release 2 (11.
See Complying with Daylight Saving Time (DST) and Daylight Database tier Time Zone Rule Changes in E-Business Suite on My Saving changes Oracle Support for instructions.10 (8815204) o Patch 5644137 o Oracle E11.0. apply TXK RUP-U (or a later version of TXK) then apply the interoperability patch before running AutoConfig. then the existing Oracle Portal functionality must be migrated to Oracle Portal 10g to ensure compatibility with Oracle Database 11g. 4. 3. apply patch 6815663. If your patch set level is earlier than patch set 18.5. apply Developer 6i Patch set 18 Application the latest certified patch set. Latest See Using AutoConfig to Manage System Configurations AutoConfig version with Application with Oracle Applications 11i on My Oracle Support for 9835302 instructions.9 is not certified with Oracle Database 11g. If you plan to continue using Oracle Portal with Oracle E-Business Suite 11i. Also apply patch 7456837. Attention The interoperability patch requires TXK RUP-U. in order to ensure that any custom Portal data is successfully migrated. . Implement AutoConfig or upgrade to the latest version.9 from E-Business Suite Release 11i on My Oracle Support.Apply 11.5. Migrate to Oracle Portal 10g (conditional) Oracle Portal 3.0. This ensures that you have the right code level when running AutoConfig. use Database tier the Windows update tool to upgrade to DirectX 9.5. Oracle Portal 3. You must run AutoConfig on both the database and application tiers. You may remove Oracle Portal 3. See Upgrading Developer 6i with Oracle Applications 11i on My Oracle Support. Apply GL patch 6815663 (conditional) If the Applications tier is on the Windows platform. Also apply patch 9835302.9 and any dependencies from Oracle E-Business Suite by performing the steps in Remove Oracle Portal 3.0. If you receive a DirectX 9. When performing the instructions implementing AutoConfig.0b.0b ONLY generic error opening the display adapter information. run the DirectX diagnostics tool customers DxDiag.exe in c:\windows\system32. Windows On Windows.10 E-Business Suite Consolidated Update 2 o 11g Release 2 interoperability patch for 11.9 should be removed only after the upgrade to Oracle Portal 10g.0.10 CU2 Application Business Suite If you are using Oracle iStore (IBE) Patch 6400762 o ATG Rollup Patch 6 Application Apply patch 5903765. Read and follow instructions in Installing Oracle Applications Server 10g with Oracle E-Business Suite Release 11i on My Oracle Support.
Update application tier context file with new database listener port number (conditional) The new 11.2) for your platform. are set for the new Oracle home you are about to create. 6. Read Chapters 1 and 2 of the Oracle Database Installation Guide 11g Release 2 (11.0 Oracle home The 11.3 software Log in to the database server node as the owner of the Oracle RDBMS file system and database instance. Database Installation: 5. Doing so will cut off the entire application tier from the database instance until after the upgrade is complete. Perform all the steps in Chapter 4. choose a disk to install the 11g Oracle home separate from the database files.0 configuration: Variable Name Value s_dbhost New database hostname s_dbdomain New database domain name s_db_serv_sid New database SID s_dbport New database listener port s_apps_jdbc_connect_descriptor NULL 6.0 Oracle home uses its own database listener for the database instance.2).0.0 Oracle home must be installed on the database server node in a different directory than the current Oracle home. Attention For HP Itanium and HP PA RISC platforms using the NFS file system.2) for your platform. Make sure you thoroughly understand the installation and upgrade processes.2. The 11g Oracle home (or any other binaries) must not include the forcedirectio mount option. Ensure that environment settings. The mount options of the disk containing the database files must include forcedirectio. such as ORACLE_HOME. and not for any existing Oracle homes on the database server node. 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. . Prepare to create the 11. Perform any step that is relevant for your environment.2.2.2. 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. Attention Do not run AutoConfig on the application tier once the context file has been updated. 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. Install the 11. "Installing Oracle Database" of the Oracle Database Installation Guide 11g Release 2 (11. Also read Chapter 1 and the "System Considerations and Requirements" section of Chapter 3 of the Oracle Database Upgrade Guide 11g Release 2 (11.5. replacing the current database listener.
apply RDBMS patches o o o o 9858539 12942119 12960302 13004894 For Windows platforms.0.pl script to create the $ORACLE_HOME/nls/data/9idata directory. Choose the Enterprise Edition installation type. perform the tasks in section 4. select the options not to upgrade an existing database and to install the database software only. 7. In the subsequent windows.3 RDBMS patches For UNIX/Linux platforms. o 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. as the owner of the Oracle RDBMS file system and database instance. The PATH environment variable includes $ORACLE_HOME/bin and the directory where the new perl executable is located (usually $ORACLE_HOME/perl/bin). In the Installation Types window. 64-bit or a later patch set. run the $ORACLE_HOME/nls/data/old/cr9idata.2. 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. o The LD_LIBRARY_PATH environment variable includes $ORACLE_HOME/lib.In the Installation Types window. Attention While not mandatory for the interoperability of Oracle E-Business Suite with the . Create nls/data/9idata directory On the database server node.32-bit. 9. "Download Oracle Database Examples" in the Oracle Database Examples Installation Guide. Apply additional 11. apply RDBMS patches o o 9858539 Patch 1 . After the installation. Install Oracle Database 11g Products from the 11g Examples CD On the database server node.0 Oracle home. use the Product Languages button to select any languages other than American English that are used by your Applications database instance. use the Product Languages button to select any languages other than American English that are used by your Applications database instance. as the owner of the Oracle RDBMS file system and database instance. o o After creating the directory. make sure that: The ORACLE_HOME environment variable points to the new 11.2.
In Oracle Database 11g. On the database tier server node.2) Chapters 3 and 4. it is recommended to .1 on My Oracle Support to disable Database Vault.1 ('Database Patch Set Update Overlay Patches Required for Use with PSUs and Oracle E-Business Suite') on My Oracle Support for more information.2). Attention (Windows only) Make sure that the Services applet window is closed on the database server node. Take note of the section pertaining to the Database Upgrade Assistant (DBUA). Drop SYS.2 pre-upgrade tool has been extended to include a warning that the DMSYS schema should be dropped.Oracle Database. If so. If this warning is reported. perform steps 1 to 6 of Part 2 of document 1091086. Prepare to upgrade Read Chapter 2 of Oracle Database Upgrade Guide 11g Release 2 (11. SQL> drop table sys.ENABLED$INDEXES (conditional) If the SYS. 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.enabled$indexes. Attention Do not apply any of the patch special instructions. The scripts will be run after the upgrade. the DMSYS schema is no longer used.ENABLED$INDEXES table exists. please see Document 1147107. 16. Upgrade the database instance The instructions for the database upgrade are outlined in Oracle Database Upgrade Guide 11g Release 2 (11. Database Upgrade: 10. The Data Mining option is installed in the SYS schema. 12. customers may choose to apply Database Patch Set Updates (PSU) on their Oracle E-Business Suite Database. 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. You cannot remove the current database instance service during the upgrade if this window is open. shut down all server processes or services. The 11. Shut down Applications server processes and database listener On each application tier server node. 15. Disable Database Vault (conditional) If you have Database Vault installed. 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. use SQL*Plus to connect to the database as SYSDBA and running the following command to drop it: 13. 14.
SQL> @$ORACLE_HOME/olap/admin/olap. Note There are many ways to generate the parameter file (for example.ora parameter file). APPLSYS. If you plan to change the PL/SQL compilation mode. use SQL*Plus to connect to the database as SYSDBA and run the following command: 23. 17. Database Initialization Parameters (init. SQL> connect / as sysdba. ignore the initialization parameters that pertain to the native compilation of PL/SQL code. upgrades. this step is needed to prevent errors while performing installations. then you do not have OLAP installed. If the query does not return AMD. copying and updating an old init. 19. that needs to be upgraded. Install OLAP Note Restricted use licences for OLAP is included with Oracle Database Enterprise Edition for the purposes of upgrading existing E-Business Suite databases.drop the schema as per the Oracle Data Mining Administrator's Guide 11g Release 2 (11.sql SYSAUX TEMP . note that Oracle E-Business Suite has only one statistics table. When upgrading all statistics tables. Set autoextend on for the SYSAUX tablespace.ora settings) in Oracle Applications Release 11i on My Oracle Support as a guideline: o Common database initialization parameters o Release-specific database initialization parameters for 11gR2 o Database initialization parameter sizing If native compilation of PL/SQL code is disabled in your database instance. or patching of database objects. While not all EBS products use the OLAP schema. Removing the DMSYS schema has no effect on the functioning of Data Mining. The interdependence of products and database objects in the Oracle E-Business Suite require that this step be performed.2). 18. SQL> connect / as sysdba. We recommend that you use 500 MB as the SYSAUX tablespace size. Ensure that the temporary tablespace is properly defined. 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. 21. SQL> select comp_id from dba_registry where comp_id='AMD'. You are not confined to using the parameter files generated by the database upgrade assistant.1. disable the compilation of objects.FND_STATTAB. To install OLAP. 24. Follow the instructions in the Temporary Tablespace Setup section. Modify initialization parameters Use the following sections in Note 216205. 22.
ora and tnsnames.sql (or adgrants_nt. you must also update AutoConfig on the database tier and deregister the current database server node. host. 26. 'public').1.set_parameter('file_access_role'.2) for more information. 31. $ sqlplus "/ as sysdba" 30. and run drkorean. 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. $ sqlplus "/ as sysdba" @$ORACLE_HOME/ctx/sample/script/drkorean. Deregister the current database server (conditional) If you plan to change the database port. Run adgrants. See the Oracle Database Net Services Administrator's Guide. 22.25. SQL> exec ctxsys. Start the new database listener (conditional) If the Oracle Net listener for the database instance in the new Oracle home has not been started.sql using the following command: 20. Attention Set the TNS_ADMIN environment variable to the directory where you created your listener. [APPS schema name] Note Verify the usage of adgrants. or database name parameter on the database server. [SYSTEM password] CTXSYS 28.sql require the APPLSYS schema name parameter to be passed instead of APPS. 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.sql (adgrants_nt. 25. Use SQL*Plus to connect to the database as SYSDBA and run the script using the following command: 23. $ sqlplus "/ as sysdba" @adgrants.sql Copy $APPL_TOP/admin/adgrants. you must start it now.sql for Windows) from the administration server node to the database server node. start the listener with the lsnrctl executable (UNIX/Linux) or Services (Windows). Since AutoConfig has not yet been implemented. Set CTXSYS parameter Use SQL*Plus to connect to the database as SYSDBA and run the following command: 29. Use SQL*Plus to connect to the database as APPS and run the script using the following command: 26.sql 21.sql \ 27. 11g Release 2 (11.ora files. $ sqlplus apps/[APPS password] @adctxprv. . SID. Older versions of adgrants. Perform patch post-install instructions Run all the patch post install instructions. use the R12 version of the file. Grant create procedure privilege on CTXSYS Copy $AD_TOP/patch/115/sql/adctxprv.sql script. use SQL*Plus to connect to the database as SYSDBA.0 or previous releases.sql) 24.sql from the administration server node to the database server node.2).sql in the adgrants. Fix Korean lexers (conditional) If you upgraded from 10. If you are upgrading to R12. After the Database Upgrade: 19.ctx_adm.
Use SQL*Plus to connect to the database as SYSDBA and use the following commands to restart the database in restricted mode. SQL> select db_link from dba_db_links. 38. 33. 39.2. SQL> startup. 40. If you are upgrading to R12. you must also run AutoConfig on each application tier server node to update the system with the new listener. and restart the database in normal mode: 34. Note that adstats. $ sqlplus apps/[apps password] 43. Gather statistics for SYS schema Copy $APPL_TOP/admin/adstats. $ sqlplus "/ as sysdba" SQL> shutdown normal. SQL> @adstats. use the R12 version of the file.sql. you must re-create any custom self-referential database links that exist in the Applications database instance. should have been updated with the new port number by AutoConfig in the previous step. The EDW_APPS_TO_WH and APPS_TO_APPS database links. use SQL*Plus on the database server node to connect to the Applications database instance as APPS and run the following query: 42.Use SQL*Plus to connect to the database as APPS and run the following command: $ sqlplus apps/[APPS password] SQL> exec fnd_conc_clone. if they exist. 41. run adstats. See Using AutoConfig to Manage System Configurations with Oracle Applications 11i on My Oracle Support for instructions on how to implement and run AutoConfig. Re-create custom database links (conditional) If the Oracle Net listener in the 11. and restart them to load the new environment settings. To check for the existence of database links. 32.5 GB of free default temporary tablespace. 36. SQL> exit. Shut down all processes.sql has to be run in restricted mode. use the following commands to drop and re-create them: $ sqlplus apps/[apps password] .0 Oracle home is defined differently than the one used by the old Oracle home. 37. Note Make sure that you have at least 1. SQL> startup restrict.sql from the administration server node to the database server node. If the database listener of the new Oracle home is defined differently than the old Oracle home. If you have custom self-referential database links in the database instance. including the database and the listener. Implement and run AutoConfig Implement and run AutoConfig in the new Oracle home on the database server node. 35.setup_clean.sql SQL> shutdown normal.
SQL> drop database link [custom database link]. Users may return to the system. Customers may encounter: 'ORA-29532: Java call terminated by uncaught Java exception: java. need to be started in the 11. Enable Database Vault (conditional) If you disabled Database Vault. you must re-create the grants and synonyms in the APPS schema.1 on My Oracle Support. 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])))'. and [ORACLE_SID] reflect the new Oracle Net listener for the database instance. enable it by performing step 7 of Part 2 of document 1091086. [port number]. 45. 44. 4. as well as the database instance itself. 3. Apply Oracle Human Resources (HRMS) patch 7721754 (conditional) If you are using Oracle HRMS. Re-create grants and synonyms Oracle Database 11g Release 2 (11. run AD Administration and select the "Recreate grants and synonyms for APPS schema" task from the Maintain Applications Database Objects menu. as the owner of the Applications file system. Oracle Demand Planning (ODP) Oracle Enterprise Planning and Budgeting (EPB) Oracle Enterprise Data Warehouse (EDW) Oracle Balance Scorecard Expert (BSC Expert). [user].2 Oracle home. [password].2) contains new functionality for grants and synonyms compared to previous database releases. Remember that the Oracle Net listener for the database instance. Restart Applications server processes (conditional) Restart all the Application tier server processes that you shut down previously. 46. 47. On the administration server node. apply patch 7721754. [hostname]. Section 3: Known Issues The following are known issues with E-Business Suite 11i on Database 11g: 1. where [custom database link].NullPointerException' . As a result.lang. Section 2: Unsupported Products The following products are not supported with E-Business Suite 11i on Database 11g: 1. 2.
1.ora metadata for 11. Please review bug 8946396 on My Oracle Support for updated information on this issue.bobj.0.oam. Workaround for this issue is available under Note 833237.1.database.InitMetadataException: No matched database version found in the init.apps. This issue is tracked under bug 8814854 on My Oracle Support.while using the DBMS_XMLQUERY package. Products where this issue has occurred are Oracle Labor Distribution (OLD) and Oracle iRecruitment (IRC).0'. 2.fnd. .ora Parameters" in System Configuration Overview page from Oracle Applications Manager. while accessing Database Init.2. Customers will see the error: 'oracle.ora settings for "Recommended/Mandatory Init.