Database Preparation Guidelines for an E-Business Suite Release 12.1.1 Upgrade [ID 761570.1]

  Modified 21-MAR-2011     Type BULLETIN     Status PUBLISHED

 

Database Preparation Guidelines for an Oracle E-Business Suite Release 12.1.1 Upgrade

Last updated March 21, 2011

In this Document

Overview Oracle E-Business Suite Configurations

Upgrade Paths

References

Appendix: Upgrade Flow Diagram

Change Record

Overview

This document details the database preparation process for Oracle E-Business Suite Release 11i customers planning to upgrade to Release 12.1.1 with the 10.2.0.3 to 11.2.0.2 versions of the database. If you have previously saved or printed a copy of this document, note that it may be updated periodically. Before you begin the tasks, always ensure that you have the most current version of My Oracle Support document 761570.1.

This document is also used by 12.0 customers applying a Maintenance Pack (MP) to upgrade to 12.1.1 or by 12.1.1 customers upgrading to 12.1.2 or 12.1.3 using a Release Update Pack (RUP) for the purpose of finding particular patches required for upgrades with database versions 10.2.0.3 and higher.

Attention: Users referencing this document as part of the 12.1.1 Maintenance Pack (MP) to upgrade from 12.0 to 12.1.1 or as part of the Oracle E-Business Suite Release 12.1.2 or 12.1.3 Release Update Pack (RUP) to upgrade from 12.1.1 to 12.1.2 or 12.1.3 should review the required patches listed in Path D (10.2.0.3, 10.2.0.4, 10.2.0.5) or Path E (11.1.0.6, 11.1.0.7, 11.2.0.1, 11.2.0.2) below.

Attention: The Release 12.1.1 Rapid Install delivers the 11.1.0.7 RDBMS. Upgrading the database to version 11.1.0.7 or higher is not required for an E-Business Suite upgrade to 12.1.1. An upgrade of Oracle E-Business Suite from 11i to 12.1.1 with database versions from 10.2.0.3 to 11.2.0.2 is currently supported, with users having the option to stay on these versions of the database with 12.1.1.

Attention: Database desupport schedules have important operational and planning implications for E-Business Suite environments. Oracle strongly recommends that customers review the following documents

detailing the latest database support policies and desupport schedules:

Database, FMW, EM Grid Control, and OCS Software Error Correction Support Policy (My Oracle Support Note 209768.1) Release Schedule of Current Database Patch Sets (My Oracle Support Note 742060.1)

The process of upgrading the Oracle E-Business Suite from Release 11i to Release 12 is a simpler process relative to past E-Business Suite upgrades. The R12 upgrade process includes replacing the Release 11i applications technology stack with an updated Fusion Middleware technology stack.

The primary utilities used in the R12 upgrade process are Rapid Install and AutoPatch. Rapid Install installs the new R12 technology stack and AutoPatch upgrades the E-Business Suite database to Release 12. The upgrade no longer requires a two-step approach of upgrading the E-Business Suite database by running AutoUpgrade and AutoPatch. The upgrade is a one step approach of updating the data model by using the R12 AutoPatch tool.

The requirement for upgrading to Release 12.1.1 is that the E-Business Suite version be at 11.5.9 or later. E-Business Suite systems on Releases 11.5.1 to 11.5.8 must be upgraded to at least 11.5.9; however, Oracle strongly recommends upgrading to 11.5.10.2. For all E-Business Suite systems, the database must be upgraded to at least 10.2.0.3 either before or during the R12 upgrade process and prior to running AutoPatch to upgrade the data model to R12.

This document assumes the Release 11i E-Business Suite system is running a version of the 9iR2, 10g, or 11g database. Customers running 8.1.7 will need to upgrade their database accordingly.

Oracle E-Business Suite Configurations

Oracle E-Business Suite systems running releases 11.5.9 or greater can be categorized into two groups. The first group includes systems that are currently running Release 11.5.9 (base or CU1), or 11.5.10 (base or CU1). The second group is systems running Release 11.5.9 CU2 or 11.5.10.2.

Note: Release 11.5.10.2 includes systems installed with Rapid Install 11.5.10.2 and those upgraded by using the 11.5.10 CU2 maintenance pack.

For the first group of systems, there is no interoperability of running the Release 11i E-Business Suite system with a 10.2.0, 11.1.0, or 11.2.0 database, therefore, the database must be upgraded (to 10.2.0, since 11.1.0 or 11.2.0 upgrades for these systems are not supported) during the R12 upgrade downtime. This means there will be a prolonged upgrade downtime because the E-Business Suite upgrade to R12 must include the necessary downtime to upgrade the database. If customers in this first group eventually want to go to 11.1.0 or 11.2.0, they may do so after completing the R12 upgrade (including the upgrade to 10gR2) process.

For the second group of systems (those on 11.5.9 CU2 or 11.5.10.2) there is interoperability between those versions of the E-Business Suite and 10.2.0, 11.1.0, or 11.2.0 of the database. Therefore, the upgrade of the database can take place prior to the R12 upgrade downtime or during the R12 upgrade downtime. By upgrading the database prior to the R12 upgrade downtime, the requisite downtime can be separated into two separate and distinct downtimes. In this scenario, the database upgrade is performed independently of the R12 upgrade and the 11i E-Business Suite system can be made available to users between the two downtimes.

Upgrade Paths

There are five possible database upgrade preparation paths. The first category of systems described in the prior section has one available upgrade path in regard to upgrading the database to 10.2.0 and the E-Business Suite system to R12. The second group of systems has five available database preparation paths. This section details each of the available paths.

The following table lists the paths available for each of the E-Business Suite 11i releases supported for an upgrade to R12. For convenience, these paths are labeled Path A, Path B, Path C, Path D, and Path E.

E-Business Suite Releases Available Paths

11.5.9 (base or CU1) with 9.2.0.x or 10.1.0.x database Path A

11.5.9 CU2 with 9.2.0.x or 10.1.0.x database Path A

11.5.9 CU2 with 10.2.0.2 database Path A

11.5.9 CU2 with 10.2.0.3 database Path D

11.5.9 CU2 with 10.2.0.4 database Path D

11.5.10 (base or CU1) with 9.2.0.x or 10.1.0.x database Path A

11.5.10.2 with 9.2.0.x or 10.1.0.x database Path A, Path B, or Path C

11.5.10.2 with 10.2.0.2 database Path B or Path C

11.5.10.2 with 10.2.0.3 database Path B, Path C, or Path D

11.5.10.2 with 10.2.0.4 database Path B, Path C, or Path D

11.5.10.2 with 10.2.0.5 database Path C or Path D

11.5.10.2 with 11.1.0.6 or 11.1.0.7 database Path C or Path E

11.5.10.2 with 11.2.0.1 or 11.2.0.2 database Path E

Path A: Standard Upgrade Path

Path A is applicable to any E-Business Suite system of Release 11.5.9 or later with database versions 9.2 or 10.1. However, Path A is the only path available to systems running releases 11.5.9 (base or CU1), 11.5.9 CU2 on 10.2.0.2 or prior database versions, or 11.5.10 (base or CU1) - it is the standard upgrade path and involves upgrading the database to the latest version of 10.2.0 during the R12 upgrade process, that is, during the critical system downtime. This path requires an extended R12 upgrade downtime because the upgrade of the database to 10.2.0 must take place during the critical downtime for the R12 upgrade.

Path A follows the R12 upgrade path as documented in the Oracle Applications Upgrade Guide: Release 11i to Release 12.1.1. In Chapter 2 of the Oracle Applications Upgrade Guide, you run Rapid Install to install the applications technology stack, which also includes a 11.1.0 Oracle Home - users will not use this Oracle Home for the upgrade, since an upgrade to 11.1.0 is not supported for these systems. Complete the steps in the Interoperability Notes to install a 10.2.0 Oracle Home and upgrade the database - users should then perform the additional database specific steps documented in the Special Instructions section of the database patch readme files. Once these steps are complete, use the AutoPatch utility to upgrade the data model to R12.

Here are the steps for Path A:

1. Plan Upgrade to 12.1.1Follow the standard 12.1.1 upgrade path as documented in the Oracle Applications Upgrade Guide: Release 11i to Release 12.1.1. Perform all requirements documented in Chapter 1 and all applicable steps in Chapter 2.

2. Upgrade Database to 10.2.0During the 'Migrate database to at least Oracle10g Release 2' step in Chapter 3 of the Oracle Applications Upgrade Guide, reference theInteroperability Notes: Oracle Applications Release 11i with Oracle Database 10g Release 2 (10.2.0) (My Oracle Support Note 362203.1) to upgrade the database to 10.2.0. 

Omit the following steps in the Interoperability Notes.

Section 1:o Verify software versionso Run adgrants.sql

o Implement and run Autoconfig

o Re-create grants and synonyms

o Apply Oracle Receivables patch

o Restart Applications server processes

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

Section 2:o Apply Oracle Receivables patcho Enable Database Vault

o Restart Applications server processes

3. Apply Database Patches

For all UNIX/Linux platforms:

o 4247037 o 9726739

o 9870614

For all Windows platforms:

o 4247037 o Windows Patch 1 (or latest patch) - 32-bit, 64-bit

Note: Perform all post-install steps documented in the database patch readme files.

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.

4. Apply Oracle Service Patch 5880762 (conditional) If you are on Release 11.5.10, apply patch 5880762.

5. Complete the R12 upgradePerform the remaining steps in Chapter 3 and all applicable steps in Chapter 4 to complete the upgrade to R12.|

Path B: Upgrade Path for Systems with 11.5.10.2 to a 10.2.0.5 Database

Path B is a modified path for 11.5.10.2 systems with the database not yet on the latest 10.2.0 patchset. Path B breaks out the R12 upgrade downtime window into two separate downtimes as opposed to one extended downtime. This path is available for 11.5.10.2 systems running either 9iR2, 10gR1, or prior 10gR2 versions of the database.

Path B follows the R12 upgrade path as documented in the Oracle Applications Upgrade Guide: Release 11i to Release 12.1.1. Either prior to beginning the R12 upgrade preparation process or during the 'Migrate or upgrade your database to at least Oracle 10g Release 2' step in Chapter 2, use the process documented in the Interoperability Notes: Oracle Applications Release 11i with Oracle Database 10g Release 2 (10.2.0) to upgrade the database to 10.2.0. 

At this time, you can bring the E-Business Suite 11i system back on line and make it available to users while continuing to plan for the other phases of the R12 upgrade process. Once you are ready to perform the full upgrade to R12, perform all necessary steps in the Oracle Applications Upgrade Guide. During the 'Migrate database to at least Oracle10g Release 2' step in Chapter 3, apply database patches to the 10.2.0 Oracle home and perform all tasks documented in the patch readmes, before continuing with the standard R12 upgrade process.

Here are the steps for Path B:

1. Plan Upgrade to 12.1.1 Follow the standard 12.1.1 upgrade path as documented in the Oracle Applications Upgrade Guide: Release 11i to Release 12.1.1. Perform all requirements documented in Chapter 1 and all applicable steps in Chapter 2.

2. Upgrade Database to 10.2.0During the 'Migrate or upgrade your database to at least Oracle 10g Release 2' step in Chapter 2, reference the Interoperability Notes: Oracle Applications Release 11i with Oracle Database 10g Release 2 (10.2.0) (My Oracle Support Note 362203.1) to upgrade the database to 10.2.0. 

If you plan to use the Release 11i system with the 10.2.0 database, perform all steps in the Interoperability Notes. If the database upgrade is part of the R12 upgrade, perform all the steps in the Interoperabity Notes except those listed in Path A, Step 2   .

Note: The database upgrade can also be performed prior to Step 1: Plan Upgrade to R12.3.

4. Continue with the R12 Upgrade or Use the 11i/10.2.0 SystemAt this point you have the option of allowing users back on the system, thereby, splitting the upgrade downtime into two shorter downtimes, or continuing with the R12 upgrade. 

5. Apply Database PatchesDuring the 'Migrate database to at least Oracle10g Release 2' step in Chapter 3 of the Oracle Applications Upgrade Guide, apply the following database patches to the existing 10.2.0 Oracle home. 

Note: Perform all steps documented in the database patch readme files.

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. For all UNIX/Linux platforms:

o 4247037

o 9726739

o 9870614

For all Windows platforms:

o 4247037 o Windows Patch 1 (or latest patch) - 32-bit, 64-bit

8. Apply Oracle Service Patch 5880762 (conditional) If you are on Release 11.5.10, apply patch 5880762.

9. Complete the R12 upgradePerform the remaining steps in Chapter 3 and all applicable steps in Chapter 4 of the Oracle Applications Upgrade Guide to complete the upgrade to R12.

Path C: Upgrade Path for Systems with 11.5.10.2 to an 11.1.0.7 or 11.2.0.2 Database

Path C is a modified path for 11.5.10.2 systems with the database not yet on the latest 11.1.0 or 11.2.0 patchset. Path C breaks out the R12 upgrade downtime window into two separate downtimes as opposed to one extended downtime. This path is available for 11.5.10.2 systems running either 9iR2, 10gR1, 10gR2, or 11gR1 versions of the database. Path C follows the R12 upgrade path as documented in the Oracle Applications Upgrade Guide: Release 11i to Release 12.1.1. Either prior to beginning the R12 upgrade preparation process or during the 'Migrate or upgrade your database to at least Oracle 10g Release 2' step in Chapter 2, use the process documented in the Interoperability Notes: Oracle Applications Release 11i with Oracle Database 11g Release 1 (11.1.0) to upgrade the database to 11.1.0 orInteroperability Notes: Oracle Applications Release 11i with Oracle Database 11g Release 2 (11.2.0) to upgrade the database to 11.2.0.

At this time, you can bring the E-Business Suite 11i system back on line and make it available to users while continuing to plan for the other phases of the R12 upgrade process.�Once you are ready to

perform the full upgrade to R12, perform all necessary steps in the Oracle Applications Upgrade Guide. During the 'Migrate database to at least Oracle10g Release 2 step' in Chapter 3, apply database patches to the 11.1.0 Oracle home and perform all tasks documented in the patch readmes, before continuing with the standard R12 upgrade process.

Here are the steps for Path C:

1. Plan Upgrade to 12.1.1 Follow the standard 12.1.1 upgrade path as documented in the Oracle Applications Upgrade Guide: Release 11i to Release 12.1.1. Perform all requirements documented in Chapter 1 and all applicable steps in Chapter 2.

2. Upgrade Database to 11.1.0 or 11.2.0During the 'Migrate or upgrade your database to at least Oracle 10g Release 2' step in Chapter 2, reference the Interoperability Notes: Oracle Applications Release 11i with Oracle Database 11g Release 1 (11.1.0) to upgrade the database to 11.1.0 or Interoperability Notes: Oracle Applications Release 11i with Oracle Database 11g Release 2 (11.2.0) to upgrade the database to 11.2.0.

If you plan to use the Release 11i system with the 11.1.0 or 11.2.0 database, perform all steps in the Interoperability Notes. If the database upgrade is part of the R12 upgrade, perform all the steps in the Interoperabity Notes except the following steps:

o Verify software versions

o Run adgrants.sql

o Implement and run Autoconfig

o Re-create grants and synonyms

o Restart Applications server processes

o Apply Oracle Human Resources (HRMS) patch 7721754

Note: The database upgrade can also be performed prior to Step 1: Plan Upgrade to R12.

Attention: You may use the 11.1.0.7 Oracle home provided as part of the 12.1.1 Rapid Install. Once the Rapid Install Oracle home is installed, roll back the Daylight Savings Time (DST) patches 7708501 and 7580744 by performing the following instructions:

o Go to the 11.1.0.7 Oracle home/inventory/oneoffs/7708501 directory.o Run "opatch rollback -id 7708501" to roll back 7708501.

o Go to the 11.1.0.7 Oracle home/inventory/oneoffs/7580744 directory.

o Run "opatch rollback -id 7580744" to roll back 7580744.

After the database upgrade, see Complying with Daylight Saving Time (DST) and Time Zone Rule Changes in E-Business Suite 12 on My Oracle Support for instructions to apply an appropriate DST patch.

3. Continue with the R12 Upgrade or Use the 11i/11g SystemAt this point you have the option of allowing users back on the system, thereby, splitting the upgrade downtime into two shorter downtimes, or continuing with the R12 upgrade. 

4. Apply Database PatchesDuring the 'Migrate database to at least Oracle10g Release 2' step in Chapter 3 of the Oracle Applications Upgrade Guide, apply the following database patches to the existing 11g Oracle home. 

Note: Perform all steps documented in the database patch readme files.

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.

6. A) For users upgrading to 11.1.0.7:

Attention: If you used the 12.1.1 Rapid Install 11.1.0.7 Oracle home and rolled back the DST patches as indicated in Step 2 above, apply only patches 6460304, 7111245, 8639653, 8940108, 9066130, 9554727, and 9743057 (for UNIX/Linux), 8935979 (for HP Itanium), 9346232 (for HP PA-RISC), or the latest Windows Rollup Patch (currently 32) (for Windows).

7.For all UNIX/Linux platforms

o 6460304

o 7111245  - 7684818 also includes 7111245 but this is a later version of the patch. Disregard errors related to 7111245 being installed when applying 7684818.

o 7211965

o 7330434

o 7486407

o 7627743

o 7639602

o 7684818

o 8199107

o 8639653

o 8940108

o 9066130

o 9554727

o 9743057

For HP Itanium platforms apply patch 8935979

For HP PA-RISC platforms apply patch 9346232

For all Windows platforms

o 4247037 o 7243270

o Windows Patch 32 (or latest patch) - 32-bit, 64-bit

Attention: For Linux x86-64, patch 7319922 contained within 7684818 was packaged incorrectly. The new version of patch 7319922 has to be applied. Perform the following instructions:

o Go to the 11.1.0.7 Oracle home/inventory/oneoffs/7319922 directory.o Run "opatch rollback -id 7319922" to rollback patch 7319922.

o Download the new version of patch 7319922 on My Oracle Support.

o Go to the patch 7319922 directory.

o Run "opatch apply".

B) For users upgrading to 11.2.0.2:

For all UNIX/Linux platforms

o 4247037 o 10149223

o 10229719

For all Windows platforms

o Windows patch 1 - 32-bit, 64-bito 4247037

8. Apply Oracle Service Patch 5880762 Apply patch 5880762.

9. Modify Initialization ParametersUse the following sections in document 396009.1, Database Initialization Parameter Settings for Oracle Applications Release 12 on My Oracle Support as a guideline for the required modifications in the Attention boxes below::

a. Common database initialization parametersb. Release-specific database initialization parameters for 11gR1 (or 11gR2)c. Database initialization parameter sizing

Attention:For 11gR1 and 11.2.0.1 databases, before performing any Applications upgrade or maintenance operations, customers must add the following to the database intialization file to disable fast validation for PL/SQL recompilations:_disable_fast_validate=TRUEThe line should be commented out during the normal operation of the Applications system. 

10.

Attention:Customers using Oracle iRecruitment on Oracle Database 11gR1 must add the following line to their database initialization file::event="31151 trace name context forever, level 0x100"Setting this event provides a fix for the issue reported in bug 6952870.

11.

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]

set the _pga_max_size initialization parameter to a larger value as follows: _pga_max_size=104857600and restart your database. 

12.

13. Complete the R12 upgradePerform the remaining steps in Chapter 3 and all applicable steps in Chapter 4 of the Oracle Applications Upgrade Guide to complete the upgrade to R12.

14. Apply Workflow Interoperability Patch 8291541Apply patch 8291541 as a post-upgrade task. 

15. Reset Initialization Parameters (conditional)If the "_disable_fast_validate" parameter was set up in Step 6 above, comment it out.

Path D: Upgrade Path for Systems with 11.5.9 CU2 or 11.5.10.2 with a 10.2.0.3, 10.2.0.4, or 10.2.0.5 Database

Path D is applicable for E-Business Suite systems already on either 11.5.9 CU2 or 11.5.10.2 and currently running a 10gR2 database. Systems in this category have databases already upgraded to 10.2.0.3, 10.2.0.4, or 10.2.0.5.

Path D follows the R12 upgrade path as documented in the Oracle Applications Upgrade Guide: Release 11i to Release 12.1.1. During the 'Migrate database to at least Oracle10g Release 2' step in Chapter 3, apply database patches to the existing 10gR2 Oracle home and perform all tasks documented in the patch readmes, before continuing with the standard R12 upgrade process.

Here are the steps for Path D:

1. Plan Upgrade to 12.1.1 Follow the standard 12.1.1 upgrade path as documented in the Oracle Applications Upgrade

Guide: Release 11i to Release 12.1.1. Perform all requirements documented in Chapter 1 and all applicable steps in Chapter 2.

2. Apply Database PatchesDuring the 'Migrate database to at least Oracle10g Release 2' step in Chapter 3, apply the following database patches.

Note: Perform all steps documented in the database patch readme files.

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.

A) For users choosing to remain on 10.2.0.3:

For all platforms:

o 6319846

Attention: For all UNIX/Linux (except Linux x86) upgrades please note the following. The 11i requirements may have included patch 5871314. This particular patch conflicts with another patch (4932527) in the above required database patch 6319846. In order to avoid this conflict during patch application, the affected upgrade users need to perform the following:

1) Download and unzip the bundled patch 6319846. 2) Remove or move 4932527 from the 6319846 directory. 3) Download and unzip 6674948. Move 6674948 into the 6319846 directory. 4) Apply opatch napply as stated in the patch 6319846 Readme.

o 6110331

For all Linux x86-64 platforms:

o 5240469

For all Windows platforms:

o 6867054  (Patch 20 or higher).o 4247037

B) For users on 10.2.0.4:

For all UNIX/Linux platforms:

o 4247037 o 6084656

o 6600051

o 6870937

o 6991626

o 7014646

For IBM Linux on system z platforms:

o 8333097

For all Windows platforms:

o 4247037 o Windows Patch 13 (or latest patch) - 32-bit, 64-bit

C) For users choosing to remain on 10.2.0.5 (applicable to 11.5.10.2 only):

For all UNIX/Linux platforms:

o 4247037 o 9726739

o 9870614

For all Windows platforms:

o 4247037 o Windows Patch 1 (or latest patch) - 32-bit, 64-bit

3. Apply Oracle Service Patch 5880762 (conditional) If you are on Release 11.5.10, apply patch 5880762.

4. Complete the R12 upgradePerform the remaining steps in Chapter 3 and all applicable steps in Chapter 4 of the Oracle Applications Upgrade Guide to complete the upgrade to R12.

Path E: Upgrade Path for Systems with 11.5.10.2 with a 11.1.0.6, 11.1.0.7, 11.2.0.1, or 11.2.0.2 Database

Path E is applicable for E-Business Suite systems already on either 11.5.10.2 and currently running an 11g database. Systems in this category have databases already upgraded to 11g (11.1.0.6, 11.1.0.7, 11.2.0.1, or 11.2.0.2) by using the process documented in the Interoperability Notes: Oracle Applications Release 11i with Oracle Database 11g Release 1 (11.1.0) or Interoperability Notes: Oracle Applications Release 11i with Oracle Database 11g Release 2 (11.2.0).

Path E follows the R12 upgrade path as documented in the Oracle Applications Upgrade Guide: Release 11i to Release 12.1.1. During the 'Migrate database to at least Oracle10g Release 2' step in Chapter 3, apply database patches to the existing 11g Oracle home and perform all tasks documented in the patch readmes, before continuing with the standard R12 upgrade process.

Here are the steps for Path E:

1. Plan Upgrade to 12.1.1 Follow the standard 12.1.1 upgrade path as documented in the Oracle Applications Upgrade Guide: Release 11i to Release 12.1.1. Perform all requirements documented in Chapter 1 and all applicable steps in Chapter 2.

2. Apply Database PatchesDuring the 'Migrate database to at least Oracle10g Release 2' step in Chapter 3, apply the following database patches.

Note: Perform all steps documented in the database patch readme files.

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.

A) For users on 11.1.0.6:

For all platforms apply OPatch 11.1.0.0.0. This is the same as OPatch 11.1.0.6.2 required by patch 6778860.

For all UNIX/Linux platforms:

o 6266400 o 6598432

o 6778860

o 6815733

o 6991626

o 7253531

o 7272286

o 7377378

Note: When applying patch 7377378 via opatch, you will see warnings that some patches are not required as they are a subset of the patches in the Oracle Home, and that several of the patches will be rolled back. These messages can safely be ignored, as this patch contains later versions of several of the patches that were included in patch 6778860. However, if you receive any warnings of a conflict when applying patches, contact Oracle Support.

For all Windows platforms:

o 7313129  (Patch 7 or higher).o 4247037

B) For users on 11.1.0.7:

For all UNIX/Linux platforms

6460304 7111245  - 7684818 also includes 7111245 but this is a later version of the patch.

Disregard errors related to 7111245 being installed when applying 7684818.

7211965

7330434

7486407

7627743

7639602

7684818

8199107

8639653

8940108

9026927

9066130

9554727

9743057

For HP Itanium platforms apply patch 8935979

For HP PA-RISC platforms apply patch 9346232

For all Windows platforms

4247037 7243270

Windows Patch 21 (or latest patch) - 32-bit, 64-bit

Attention: For Linux x86-64, patch 7319922 contained within 7684818 was packaged incorrectly. The new version of patch 7319922 has to be applied. Perform the following instructions:

Go to the 11.1.0.7 Oracle home/inventory/oneoffs/7319922 directory. Run "opatch rollback -id 7319922" to rollback patch 7319922.

Download the new version of patch 7319922 on My Oracle Support.

Go to the patch 7319922 directory.

Run "opatch apply".

C) For users on 11.2.0.1:

For all UNIX/Linux platforms

8328200 8993052

9081430

9218789

9318214

9500046

9535951

9644960

9657344

9719541

9756939

For all Windows platforms

Windows patch 5 - 32-bit, 64-bit 4247037

8790561

8888178

9140891

9193873

9644960

D) For users on 11.2.0.2:

For all UNIX/Linux platforms

4247037 10149223

10229719

For all Windows platforms

Windows patch 1 - 32-bit, 64-bit 4247037

3. Apply Oracle Service Patch 5880762 Apply patch 5880762.

4. Modify Initialization ParametersUse the following sections in document 396009.1, Database Initialization Parameter Settings for Oracle Applications Release 12 on My Oracle Support as a guideline for the required modifications in the Attention boxes below::

a. Common database initialization parametersb. Release-specific database initialization parameters for 11gR1c. Database initialization parameter sizing

Attention:For 11gR1 and 11.2.0.1 databases, before performing any Applications upgrade or maintenance operations, customers must add the following to the database intialization file to disable fast validation for PL/SQL recompilations:_disable_fast_validate=TRUEThe line should be commented out during the normal operation of the Applications system. 

5.

Attention:Customers using Oracle iRecruitment on Oracle Database 11gR1 must add the following line to their database initialization file::event="31151 trace name context forever, level 0x100"Setting this event provides a fix for the issue reported in bug 6952870.

6.

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]

set the _pga_max_size initialization parameter to a larger value as follows: _pga_max_size=104857600and restart your database. 

7.

8. Complete the R12 upgradePerform the remaining steps in Chapter 3 and all applicable steps in Chapter 4 of the Oracle Applications Upgrade Guide to complete the upgrade to R12.

9. Apply Workflow Interoperability Patch 8291541 (conditional)If you are on Oracle Database 11gR1 version 11.1.0.7, apply patch 8291541 as a post-upgrade task. 

10. Reset Initialization ParametersIf the "_disable_fast_validate" parameter was set up in Step 4 above, comment it out.

References

Oracle Applications Release Notes, Release 12.1.1 Oracle Applications Upgrade Guide: Release 11i to Release 12.1.1

Interoperability Notes: Oracle Applications Release 11i with Oracle Database 10g Release 2 (10.2.0) (My Oracle Support Note 362203.1)

Interoperability Notes: Oracle Applications Release 11i with Oracle Database 11g Release 1 (11.1.0) (M Oracle Support Note 452783.1)

Interoperability Notes: Oracle Applications Release 11i with Oracle Database 11g Release 2 (11.2.0) (My Oracle Support Note 881505.1)

Appendix: Upgrade Flow Diagram

The following flow diagram depicts the processes and paths documented in this note.

Note: Chapter references are for the Oracle Applications Upgrade Guide: Release 11i to Release 12.1.1.

Change Record

Date Description

21-Mar-2011

Added 10.2.0.5 RDBMS patch 9870614 Removed 11.5.9 CU2 with 10.2.0.5 combination as it is not certified

7-Mar-2011

Fixed references to correct URL for patches; added hyperlinks for paths

25-Feb-2011

Added 11.2.0.2 patch 10229719 Added 11.2.0.2 Windows patch information Added 11.1.0.7 patch 6460304 Removed 11.1.0.7 patch 9026927 Modified 11.1.0.7 patch 21 to 32 Added note to ignore errors related to 7111245 already installed Added attention statement to refer to 1147107.1 when applying PSUs

15-Nov-2010

Added 11.2.0.2 references

5-Oct-2010

Added 10.2.0.5 Windows patch information

26-Aug-2010

Replaced 11.2.0.1 Windows patch 4 to Patch 5

20-Aug-2010

Added 11.2.0.1 patches 8993052, 9081430, 9500046, 9535951, 9644960 Replaced 11.2.0.1 Windows patch 3 to Patch 4

19-Jul-2010

Replaced 11.2.0.1 Windows patch 1 to Patch 3

9-Jul-2010

Changes required for 12.1.3 RUP Added 11.1.0.7 patches 7111245, 9554727, 9743057 Replaced 11.1.0.7 patch 7630760 to 9346232 Added 11.1.0.7 patch 8935979 Removed OPatch 11.1.0.0.0 requirement for 11.1.0.7 Added 11.2.0.1 patches 8328200, 9318214, 9657344, 9719541, 9756939 for UNIX/Linux. Added 11.2.0.1 patches for Windows Windows patch 1, 4247037, 8790561, 8888178, 9193873, 9140891.

2-Jul-2010

Added 10.2.0.5 references

30-Apr-2010

Added instructions for use of 11.1.0.7 Rapid install Oracle home in Path C

3-Mar-2010

Added Attention statement to reapply patch 7319922 for Linux x86-64 platforms

24-Dec-2009

Added 11.2.0.1 references

18-Dec-2009

Updated 10.2.0.4 patches by adding 8333097, 6084656, Windows patch 13 requirement. Updated 11.1.0.7 patches by adding 8638653, 8940108, 9026927, 9066130 and removing 8338798. Replaced Windows Patch 10 requirement to 21. Updated Workflow patch from 7664946 to 8291541 Added 12.1.2 references

11-Nov-2009

Fixed incorrect link to the 12.1.1 Upgrade Guide in References section

27-Apr-2009

Initial Release for 12.1.1.

Note 761570.1 by Oracle Applications DevelopmentCopyright 2009 Oracle Corporation Last modified: Monday, March 21, 2011

 Attachments

 flow_upg_1211_with_11201.jpg (46.34 KB) Related

Products

Oracle E-Business Suite > Applications Technology > Lifecycle Management > Oracle Application Install

Keywords

UPGRADE TO 12.1.1; UPGRADE PREPARATION; UPGRADE DATABASE; E-BUSINESS

Errors

ORA-7445[EXCEPTION]; ORA-7445; ORA-4030; ORA-7445[EXCEPTION]

Back to top