Copyright (c) 2023, Oracle. All rights reserved. Oracle Confidential.

Interoperability Notes: Oracle E-Business Suite Release 12.0 or 12.1 with Oracle Database 11g
Release 2 (11.2.0) (Doc ID 1058763.1)

This note is the primary document describing the use of Oracle E-Business Suite Release 12 (12.0.x and 12.1.x) with Oracle
Database 11g Release 2 (11.2.0.x), where x denotes the patch set level (currently 4). It may refer to related interoperability
notes, which you should review if they apply to your specific release of the Oracle Database.

The most current version of this document is document 1058763.1 on My Oracle Support. There is a change log at the end of
this document.

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

11.2.0.2 Interoperability Notes

11.2.0.3 Interoperability Notes

Attention: Check My Oracle Support to make sure that your platform and environment configuration are certified to
work 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 12 on My Oracle Support.

This document contains the following sections:

Section 1: Upgrading an R12 Database to Oracle Database 11g Release 2 (11.2.0)

Instructions for upgrading an Oracle E-Business Suite Release 12 database server and instance from 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 12 on Oracle Database
11g Release 2 (11.2.0).

Section 3: Known Issues

This section lists known issues with Oracle E-Business Suite Release 12 on Oracle Database 11.2.0.4.

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.4 software from Patch 13390677 on My Oracle Support.
Section 1: Upgrading an R12 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 the latest version of 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.

Minimum
Software Tier Details
Version

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

If you are on E-Business Suite Release 12.0, apply

Patch 6435000 - Oracle E-Business Suite 12.0.4
Patch 8623536 - 11g Release 2 interoperability patch for
Release 12.0.4
Patch 9868229
If you are on E-Business Suite Release 12.1, apply
Patch 7303030 - Oracle E-Business Suite 12.1.1
Oracle E- Patch 9062910 - 11g Release 2 interoperability patch for
12.0.4 or
Business Application Release 12.1
12.1.1
Suite Patch 8919489 - 12.1 TXK Delta 3 patch
Patch 9868229
Patch 10163753
Patch 11071569
Patch 18843706 - apply only if you have applied a
Recommended Patch Collection (RPC) patch
Patch 31893621 - apply only if you have TXK Delta 4 or a
later version

Demand
If you are using Demand Signal Repository (DSR), apply
Signal 12.1.2 with
Application Patch 7303033 - Oracle E-Business Suite 12.1.2
Repository 9182368
Patch 9182368
(conditional)

If you are using Oracle Warehouse Builder (OWB) 11g Release 2,

apply OWB 11g Release 2 (11.2.0.1) and Patch 9403153. The
Oracle
11.2.0.1 following E-Business Suite Release 12 products use OWB 11g
Warehouse Warehouse Builder
with Release 2:
Builder Database
9403153 Oracle Demand Signal Repository (DSR)
(conditional)
Oracle Manufacturing Operations Center (MOC)
Oracle Balance Scorecard (BSC)

Implement AutoConfig or upgrade to the latest version. See Using

AutoConfig to Manage System Configurations with Oracle E-
Latest Business Suite Release 12 on My Oracle Support for instructions. If
version you are on Oracle E-Business Suite Release 12.1, apply patches
with Patch 9738085 and Patch 9852070.
9852070,
AutoConfig Application
9738085, If you are on the IBM Linux on System Z platform and on Oracle
11692965, E-Business Suite Release 12.1, apply Patch 11692965.
and
12686610 Apply Patch 12686610 (for Oracle E-Business Suite Release 12.0
and 12.1).
 The downgrade of Daylight Saving Time (DST) patches are not
supported. 11.2.0.4 contains DST patch 14. If the source
environment has a higher DST patch, the 11.2.0.4 Oracle home
needs to be patched with an appropriate DST patch. See
Complying with Daylight Saving Time (DST) and Time Zone Rule
Changes in E-Business Suite 12 on My Oracle Support for more
information.
Daylight
Saving N/A Database tier On Windows, the database uses
changes %ORACLE_HOME%\oracore\zoneinfo\readme.txt to see the DST
patch version. However, for patch 15 and onwards, the readme is
shipped as readme_[patch number].txt. If you are applying DST
patch 15 or higher, copy
%ORACLE_HOME%\oracore\zoneinfo\readme_[patch number].txt
to %ORACLE_HOME%\oracore\zoneinfo\readme.txt after the
patch installation.

On Windows, run the DirectX diagnostics tool DxDiag.exe in

Windows
c:\windows\system32. If you receive a generic error opening the
DirectX 9.0b customers ONLY
display adapter information, use the Windows update tool to
- Database tier
upgrade to DirectX 9.0b.

Attention: The interoperability patch for 12.0.4 requires R12.TXK.A.delta.6. When performing the instructions
implementing AutoConfig, apply R12.TXK.A.delta.6 (or a later version of TXK) then apply the 12.0.4
interoperability patch with 11g Release 2 before running AutoConfig. This ensures that you have the right code
level when running AutoConfig.

2. Apply patch 6400501 (conditional)

If you are on a UNIX/Linux platform, apply the 10.1.0.5 version of Patch 6400501 to the iAS 10.1.2 Applications tier
Oracle home.

Note: For Linux x86-64 environments, download the Linux 32-bit version of the patch as the Applications tier
Oracle home is 32-bit.

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

See Using AutoConfig to Manage System Configurations with Oracle E-Business Suite Release 12 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:

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

5. Install the 11.2.0.4 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, "Installing Oracle Database"
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.

Note:

1. When installing 11.2.0.4 on Oracle Linux 7 or Red Hat Linux 7, ignore the warning regarding missing
package 'pdksh-5.2.14' during pre-requisite checks.

2. When installing 11.2.0.4 on Oracle Linux 7 or Red Hat Linux 7 and encountering the installer error in
invoking target 'agent nmhs' of makefile with the log file showing an undefined reference to symbol
'B_DestroyKeyObject', users should review and implement the workaround noted in the document
Installation of Oracle 11.2.0.4 Database Software on OL7 fails with "undefined reference to symbol
'B_DestroyKeyObject'" error".

6. Install Oracle Database 11g Products from the 11g Examples CD (mandatory)

On the database server node, as the owner of the Oracle RDBMS file system and database instance, perform the tasks
in the "Install Oracle Database Examples" section 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:

a. The ORACLE_BASE environment variable must be set accordingly.

b. The ORACLE_HOME environment variable points to the new 11.2.0 Oracle home.

c. The PATH environment variable includes $ORACLE_HOME/bin and the directory where the new perl executable is
located (usually $ORACLE_HOME/perl/bin).
 d. The LD_LIBRARY_PATH environment variable includes $ORACLE_HOME/lib.

e. The PERL5LIB environment variable points to the directories where the new perl libraries are located
($ORACLE_HOME/perl/lib/[perl version] and $ORACLE_HOME/perl/lib/site_perl/[perl version] for UNIX/Linux,
$ORACLE_HOME/perl/lib and $ORACLE_HOME/perl/site/lib for Windows)

7. Create nls/data/9idata directory

On the database server node, as the owner of the Oracle RDBMS file system and database instance, run the following
command to create the $ORACLE_HOME/nls/data/9idata directory.

$ perl $ORACLE_HOME/nls/data/old/cr9idata.pl

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.

8. Apply additional 11.2.0.4 RDBMS patches

Apply the following patches:

For all UNIX/Linux platforms:

Patch 4247037
Patch 17402822
Patch 17468141
Patch 17501296
Patch 17892268
Patch 19393542
Patch 22731026
Patch 25136212

For all Windows platforms:

Windows patch 11 - Patch 20043415 or higher

Patch 4247037
Patch 19156765
Patch 22731026
Patch 25136212

Attention: For Oracle Exadata customers, see Oracle E-Business Suite Release 11i & R12 Patches Required with
Oracle Database 11g Release 2 (11.2.0) on Exadata for more information on patches to apply.

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.

Do not run any of the post install instructions as those will be done after the upgrade.

Database Upgrade:

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

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

SQL> drop table sys.enabled$indexes;

11. Disable Database Vault (conditional)

If you have Database Vault installed, perform steps 1 to 6 of Part 2 of document 1091083.1 on My Oracle Support to
disable Database Vault.

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

Note: Ensure that the oratab file contains an entry for the database to be upgraded.

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.

13. 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 pre-upgrade 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.

Disregard warnings related to Network ACLs. AutoConfig manages all the E-Business Suite Network ACLs.

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.

14. Modify initialization parameters

Use the following sections in document 396009.1, Database Initialization Parameter Settings for Oracle Applications
Release 12 on My Oracle Support as a guideline:

a. Common database initialization parameters

b. Release-specific database initialization parameters for 11gR2

 c. Database initialization parameter sizing

Attention: If you encounter the error:

ORA-04030: out of process memory when trying to allocate 822904 bytes (pga heap, kco buffer)
ORA-07445: exception encountered: core dump [dbgtfdFileWrite()+48]
then set the _pga_max_size initialization parameter to a larger value as follows:
_pga_max_size=104857600
Restart your database.

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.

15. Perform patch post-install instructions

Run all the patch post install instructions.

16. Natively compile PL/SQL code (optional)

You can choose to run Oracle E-Business Suite 12.1 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:

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

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

19. Grant create procedure privilege on CTXSYS

Copy $AD_TOP/patch/115/sql/adctxprv.sql from the administration server node to the 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] @adctxprv.sql \
[SYSTEM password] CTXSYS

20. Set CTXSYS parameter

Use SQL*Plus to connect to the database as SYSDBA and run the following command:

$ sqlplus "/ as sysdba"

SQL> exec ctxsys.ctx_adm.set_parameter('file_access_role', 'public');

21. Validate Workflow ruleset

On the administration server node, use SQL*Plus to connect to the database as APPS and run the
$FND_TOP/patch/115/sql/wfaqupfix.sql script using the following command:

$ sqlplus [APPS user]/[APPS password] @wfaqupfix.sql\

[APPLSYS user] [APPS user]

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

23. 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 E-Business Suite Release 12 on My Oracle Support
for instructions on how to implement and run AutoConfig. Section 3.2 explains how to generate a context file on the
database tier.

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

Attention: For Windows customers, after creating the XML context file, ensure that the variable s_dlsnname has
the proper listener service name.

Attention: After creating the XML context file, ensure the variable s_jretop points to $ORACLE_HOME/jdk/jre and
is not altered to any other value.

24. Apply post-upgrade ECX patch

If you are on E-Business Suite Release 12.0, apply ECX Patch 9922442. If you are on E-Business Suite Release 12.1,
apply Patch 9151516.

25. 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 run adstats.sql in restricted mode:

$ sqlplus "/ as sysdba"

SQL> alter system enable restricted session;
SQL> @adstats.sql
$ sqlplus "/ as sysdba"
SQL> alter system disable restricted session;
SQL> exit;

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

26. Create Demantra privileges (conditional)

If you are using Demantra, perform the steps in document 730883.1 on My Oracle Support.

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

$ sqlplus apps/[apps password]

SQL> select db_link from all_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.

28. Enable Database Vault (conditional)

If you disabled Database Vault, enable it by performing step 7 of Part 2 of document 1091083.1 on My Oracle Support.

29. Restart Applications server processes

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.

30. Synchronize Workflow views

Log on to Oracle E-Business Suite with the "System Administrator" responsibility. Click Requests > Run > Single
Request and the OK button. Enter the following parameters:

Request Name = Workflow Directory Services User/Role Validation

 Batch Size = 10000
Fix dangling users = Yes
Add missing user/role assignments = Yes
Update WHO columns in WF tables = No

Click "OK" and "Submit".

Section 2: Unsupported Products

The following EBS products are currently not supported with E-Business Suite Release 12 on Oracle Database 11g Release 2
(11.2.0):

Oracle Enterprise Data Warehouse (EDW)

Oracle Enterprise Planning and Budgeting (EPB)

Section 3: Known Issues

The following are known issues with E-Business Suite 12.0 and 12.1 on Database 11.2:

1. PLS-00306: wrong number or types of arguments in call to 'SYNCRN'

is encountered when trying to create sales contacts. More information may be found in bug 17441178.

2. FRM-99999: Error 408 occurs when trying to modify HRMS contact information. More information may be found in bug
17446933.

Change Record

The following sections were changed in this document.

Date Summary of Changes

24-Dec-
Initial release
2009
Added AutoConfig patches 8966480, 9161926
4-Feb-2010
Replaced Interoperability Note number from 881506.1 to 1058763.1
Replaced patch 9161926 with 9366993
1-Mar-2010
Added note to ensure entry for the database to be upgraded is in oratab
6-Apr-2010 Modified AutoConfig patch requirement to 9366993 and 9439555 as 12.0 TXK delta 7 is out.
Removed DSR from unsupported products.
16-Apr-2010 Added 12.1.2 with 9182368 requirement for DSR.
Added OWB 11gR2 with patch 9403153 requirement for DSR.
30-Apr-2010 Removed Database Vault from list of unsupported products
25-May-
Added Windows 32 and x64 instructions for the 11.2.0.1 certification.
2010
9-Jul-2010 Added patches 8328200, 9318214, 9657344, 9719541, 9756939.
Added HP PA RISC and HP Itanium instructions for NFS file system users to include the forcedirectio mount
option.
19-Jul-2010 Added AutoConfig patches 9852070 and 9738085.
Removed AutoConfig patches 9366993 and 9439555 as they are included in latest AutoConfig patch.
Modified Windows patch 1 requirement to Patch 3.
20-Aug- Added patches 8993052, 9081430, 9500046, 9535951, 9644960
2010 Modified Windows patch 3 to patch 4.
26-Aug-
Modified Windows patch 4 to patch 5.
2010
Updated to 11.2.0.2.
Moved step to deregister Oracle home to "Database Upgrade" section
Added steps related to Database Vault
15-Nov-
Replaced 12.1 TXK Delta 2 patch to 12.1 TXK Delta 3.
2010
Removed setting of _disable_fast_validate=TRUE as fix is in 11.2.0.2.
Added EBS patches 9868229 and 10024524.
Added reference to 1147107.1 regarding PSU patch list.
23-Nov-
Removed references to patch 9218789.
2010
Added RDBMS patch 10229719.
10-Dec- Added EBS patch 10163753.
2010 Changed Database Examples reference from Section 3 to Section 4.
Added Attention statement to unset LOCAL_LISTENER.
Added 11.2.0.2 Windows 32-bit and x64 certification.
Removed 10024524 as fix is not related to database interoperability.
24-Feb- Added TXK patch 11071569 for 12.1.
2011 Changed pre-upgrade adgentns.pl step to post-upgrade fnd_conc_clone.
Removed MOC from list of unsupported produts.
Added MOC to list of products using OWB.
Changed Chapter 3 Oracle Database Installation Guide reference to Chapter 4.
Added statement to remove DMSYS schema.
2-May-2011
Removed BSC from list of unsupported products.
Added patch 11692965 for IBM zLinux certification.
Added RDBMS patch 9776940.
6-Jul-2011 Replaced Windows patch 1 to patch 4.
Modified wording of AutoConfig s_jretop setting.
11-Nov-
Updated to 11.2.0.3
2011
13-Dec-
Added AutoConfig patch 12686610
2011
Added ECX patches 9151516, 9922442
9-Mar-2012
Added mandatory to Examples CD installation step
14-Mar-
Added required Windows patches
2012
3-Apr-2012 Added RDBMS patches 12985184, 13001379, 13258936, 13366268
Moved 9151516/9922442 to a post-upgrade step from pre-upgrade
4-Jul-2012
Added EPB to list of unsupported products
Added paragraph to disregard Network ACLs during upgrade
15-Jan-2013 Modified instructions to install Examples CD as it is already part of 11.2.0.3
Fixed all links to other My Oracle Support documents and patch references
20-Sep-
Updated to 11.2.0.4
2013
10-Oct-2013 Modified patch 16702016 to 17468141
3-Dec-2013 Added RDBMS patch 17501296
5-Feb-2014 Added RDBMS patch 17892268
14-Mar- Added RDBMS patch 17402822
2014 Added reference for Exadata patches
2-Jun-2014 Added Windows patch information
 Added Windows information for DST patches
26-Sep- Modified Windows patch 3 to patch 6
2014 Added EBS patch 18843706
Modified Windows patch 6 to patch 11
19-Mar-
Added RDBMS patch 19393542
2015
Made 18843706 conditional on RPC patch
Added note on OEL7 and RHEL7 installation errors
25-Jan-2016
Removed Re-create grants and synonyms step
29-Mar- Added Windows RDBMS patch 19156765
2016 Removed RDBMS patch 17501296 for Windows
7-Nov-2016 Added RDBMS patch 22731026
4-Sep-2020 Added RDBMS patch 25136212
13-Apr-2021 Modified Oracle Database document links
11-Aug-
Made minor changes to meet publication standards
2021
14-Jun-2022 Added EBS patch 31893621

My Oracle Support Knowledge Document 1058763.1 by Oracle E-Business Suite Development

Copyright © 2009, 2022, Oracle and/or its affiliates.

REFERENCES
NOTE:1091083.1 - Integrating Oracle E-Business Suite Release 12 with Oracle Database Vault 11gR2
NOTE:1147107.1 - Database Patch Set Update Overlay Patches Required for Use with PSUs and Oracle E-Business Suite
NOTE:396009.1 - Database Initialization Parameters for Oracle E-Business Suite Release 12
NOTE:1058763.1 - Interoperability Notes EBS 12.0 and 12.1 with Database 11gR2

Didn't find what you are looking for?