12/15/2016 Document 1617461.

Applying the Latest AD and TXK Release Update Packs to Oracle E­Business Suite Release 12.2
(Doc ID 1617461.1)

This document describes how to apply the latest Oracle Applications DBA (AD) and Oracle E­Business Suite Technology Stack
(TXK) release update packs (RUPs) to Oracle E­Business Suite Release 12.2.

Note: The latest RUPs are R12.AD.C.Delta.8 (Patch 21841299) and R12.TXK.C.Delta.8 (Patch 21830810).

You should periodically check this Document 1617461.1 on My Oracle Support for updates, which are made as required. For
example, new bundled fixes or critical one­off patches may become available, or the release update packs may be superseded
by newer versions.

The change log will help you identify amendments.

Note: Oracle strongly recommends that you always apply the latest version of the AD and TXK release update packs at
your earliest convenience. New AD and TXK code fixes require the codelevel documented here as a prerequisite.

If for some specific reason you need to use an older version for a limited period, refer to My Oracle Support
Knowledge Document 1903052.1, Applying A Non­Current Version of the AD and TXK Release Update Packs to
Oracle E­Business Suite Release 12.2 .

In this Document

Section 1: Preparation
Section 2: Apply Required Database Patches and Update Database Initialization Parameters
2.1 Apply Required Database Patches
2.2 Set Database Parameter (Conditional)
Section 3: Apply the R12.AD.C.Delta.8 and R12.TXK.C.Delta.8 Release Update Packs
3.1 Path A — Upgrade and New Installation Customers
3.2 Path B — Existing Release 12.2 Customers (Below AD­TXK Delta 8 Codelevel)
Section 4: Apply Additional Critical Patches
4.1 Critical AD Patches
4.2 Critical TXK Patches
4.3 Product Interoperability Patches
Section 5: Migrate Latest Code to Database Tier
Change Log

Section 1: Preparation
In Release 12.2.0 and higher, patching is performed by running the new adop (AD Online Patching) utility. You must use adop
instead of the adpatch utility that was provided in previous releases. Download and unzip all the patches to the default patch
location for Release 12.2 ($PATCH_TOP). The PATCH_TOP location must be accessible to all application tier nodes in an
application tier configuration. For more information about the adop utility, refer to Oracle E­Business Suite Concepts
(Part No.
E22949) and Oracle E­Business Suite Maintenance Guide, Release 12.2 (Part No. E22954).

For changes from AD­TXK Delta.7 to Delta.8, refer to My Oracle Support Knowledge Document 2159750.1, Oracle E­Business
Suite Applications DBA and Technology Stack Release Notes for R12.AD.C.Delta.8 and R12.TXK.C.Delta.8
.

Section 2: Apply Required Database Patches and Update Database Initialization

Parameters

2.1 Apply Required Database Patches

https://support.oracle.com/epmos/faces/DocumentDisplay?_adf.ctrl­state=e97om08b0_96&id=1617461.1 1/13
12/15/2016 Document 1617461.1

Before you apply the AD and TXK Delta 8 release update packs (RUPs), you must run the latest version (available via Patch
17537119) of the EBS Technology Codelevel Checker (ETCC)
. Use the command checkDBpatch.sh (on UNIX) or
checkDBpatch.cmd (on Windows).

Running the latest version is required in order to:

1. Check that all the required database patches have been applied. To learn more about the prerequisite
database patches needed for applying the Delta 8 RUPs, refer My Oracle Knowledge Document 1594274.1, Oracle E­
Business Suite Release 12.2: Consolidated List of Patches and Technology Bug Fixes.
2. Ensure all the required ETCC database objects will be found by the Delta 8 RUP installation process. This
means that even if you already have all the required database patches installed, you must still run the latest version of
ETCC on your database.

2.2 Set Database Parameter (Conditional)

Oracle Database 12c Release 1 uses cost based optimization. If you are using Oracle Database 12.1.0.2, the following
optimizer parameter should always be set to 'false'. This setting should be completed before proceeding with the next steps
and should not be changed thereafter.

optimizer_adaptive_features=false

You can verify the parameter was set correctly by running the following command, which should return the value FALSE:

SQL>show parameter optimizer_adaptive_features

For more information about database initialization parameters, refer to My Oracle Support Knowledge Document 396009.1,
Database Initialization Parameters for Oracle E­Business Suite Release 12.

Section 3: Apply the R12.AD.C.Delta.8 and R12.TXK.C.Delta.8 Release Update Packs

If you are... Follow this path...

i
Upgrading to Oracle E­Business Suite Release 12.2 from Release 11 , 12.0, or 12.1 Path A

Installing a new Oracle E­Business Suite system Path A

Already using Oracle E­Business Suite Release 12.2

Path B
(below AD­TXK Delta 8 codelevel)

Note: The note box at the start of the instructions for each path will help you determine if that path is the correct one for
you. Decide which path you need to follow before commencing application of the AD and TXK Delta 8 release update
packs.

3.1 Path A — Upgrade and New Installation Customers

Note: Follow Path A if any of the following conditions apply:

i
You are upgrading to Release 12.2 from Release 11 /12.0.x/12.1.x.
You are performing a new installation.
You are in the process of upgrading to Release 12.2 and have applied previous AD/TXK Delta but not applied the E­
Business Suite Release Update Pack.

3.1.1 Prerequisite: Run ETCC

If you do not execute the latest version of ETCC (see Section 2), the patch application procedure will fail.

https://support.oracle.com/epmos/faces/DocumentDisplay?_adf.ctrl­state=e97om08b0_96&id=1617461.1 2/13
12/15/2016 Document 1617461.1

Upgrade Customers

If you are upgrading to Release 12.2 using an existing Oracle database version's ORACLE_HOME, you must check that
you have all the required database one­off patches by running the codelevel checker utility checkDBpatch.sh
(checkDBpatch.cmd on Microsoft Windows) before you run Rapid Install to create the upgrade file system. After you
have executed Rapid Install, run the middle tier checker utility checkMTpatch.sh (checkMTpatch.cmd on Microsoft
Windows) to identify and apply any missing patches.

If you are upgrading to Release 12.2 from a pre­12.2 Installation, review My Oracle Support Knowledge Document
1349240.1, Database Preparation Guidelines for an Oracle E­Business Suite Release 12.2 Upgrade as well as My Oracle
Support Knowledge Document 1594274.1, Oracle E­Business Suite Release 12.2: Consolidated List of Patches and
Technology Bug Fixes , and apply all technology patches for your database versions (prior to the upgrade) and middle
tier versions (after running Rapid Install).

New Installation Customers

If you are a new installation customer, you should also run the codelevel checker utility (checkDBpatch.sh and
checkMTpatch.sh or checkDBpatch.cmd and checkMTpatch.cmd, respectively for Linux and Windows) to identify and
apply any missing patches (for example, ones that may have become available after release of the startCD).

In addition, you must review My Oracle Support Knowledge Document 1594274.1, Oracle E­Business Suite Release
12.2: Consolidated List of Patches and Technology Bug Fixes
and apply all technology patches for your database and
application tier versions.

After you have run ETCC as applicable, proceed to the installation steps below.

3.1.2 Run Installation Steps

1. Source the run edition environment file.

UNIX:

$ . <RUN_BASE>/EBSapps/appl/APPS<CONTEXT_NAME>.env

Windows:

C:\><RUN_BASE>\EBSapps\appl\envshell<CONTEXT_NAME>.cmd

2. Apply the latest application tier technology patches to the run file system. Refer to My Oracle Support Knowledge
Document 1355068.1, Oracle E­Business Suite 12.2 Patching Technology Components Guide for instructions on how to
do this.

Note: This path (A) uses hot patching, which means that the patches (in this case, application tier technology
patches) are applied directly to the run file system outside an online patching cycle. Unless specifically directed
otherwise, you should not apply any application tier technology patches to the patch file system. Nor should you
invoke any adop actions such as finalize, cutover, cleanup, or fs_clone: these actions are executed in later steps, as
mentioned in the appropriate parts of this document.

The application tier technology patches you need to apply are listed in 'Section 4: Application Tier Technology Patches
and Bug Numbers' of My Oracle Support Knowledge Document 1594274.1, Oracle E­Business Suite Release 12.2:
Consolidated List of Patches and Technology Bug Fixes .

Note: This AD­TXK codelevel has a dependency on Oracle Fusion Middleware:

11.1.1.6: Patch 20642039
11.1.1.7: Patch 20756887
If you are applying Delta 8 to a system on a pre­Delta 7 AD­TXK codelevel, you must apply the Oracle Fusion
Middleware patch before proceeding with the AD and TXK patches. If you do not apply this patch, application of the
TXK patch will fail.

https://support.oracle.com/epmos/faces/DocumentDisplay?_adf.ctrl­state=e97om08b0_96&id=1617461.1 3/13
12/15/2016 Document 1617461.1

3. Start up only the Oracle Weblogic Admin Server on the run edition application tier file system.

UNIX:

$ sh $ADMIN_SCRIPTS_HOME/adadminsrvctl.sh start

Windows:

C:\>%ADMIN_SCRIPTS_HOME%\adadminsrvctl.cmd start

4. Unzip patches and run adgrants.

a. Download and unzip the following patches:
Patch 21841299 (R12.AD.C.Delta.8)
Patch 21830810 (R12.TXK.C.Delta.8)

Note: You should also download and unzip any applicable patches from Section 4: Apply Additional Critical
Patches.

b. Execute adgrants by following the instructions in the readme of Patch 21841299 (R12.AD.C.Delta.8).

5. a. On the run edition application tier file system, apply Patch 21841299 (R12.AD.C.Delta.8) in hotpatch mode.

UNIX:

$ adop phase=apply patches=21841299 hotpatch=yes

Windows:

C:\>adop phase=apply patches=21841299 hotpatch=yes

b. As per subsection 4.1 Critical AD Patches, apply any applicable AD patches as a comma­separated list of
patches. Ensure that you also add "merge=yes" to the end of your command, if there is more than one patch.

UNIX:

$ adop phase=apply patches=<Your First AD Patch>,<Your Second AD Patch Number>

hotpatch=yes merge=yes

Windows:

C:\>adop phase=apply patches=<Your First AD Patch>,<Your Second AD Patch Number>

hotpatch=yes merge=yes

Note: The above patches must be applied in the order mentioned above.

6. On the run edition application tier file system, use hotpatch mode to apply Patch 21830810 (R12.TXK.C.Delta.8) (plus
any additional critical patches – see note box).

$ adop phase=apply patches=21830810 hotpatch=yes

Note: As per subsection 4.2 Critical TXK Patches, you should also add any applicable TXK patches as a comma­
separated list of patches to this command. Ensure that you also add "merge=yes" to the end of your command, as
shown here:

$ adop phase=apply patches=21830810,<Your First TXK Patch>,<Your Second TXK Patch Number>
hotpatch=yes merge=yes

https://support.oracle.com/epmos/faces/DocumentDisplay?_adf.ctrl­state=e97om08b0_96&id=1617461.1 4/13
12/15/2016 Document 1617461.1

7. Source the run edition environment file.

UNIX:

$ . <EBS_ROOT>/EBSapps.env run

Note: <EBS_ROOT> represents the Oracle E­Business Suite base install directory. For example, /u01/oracle.

Windows:

C:\><RUN_BASE>\EBSapps\appl\envshell<CONTEXT_NAME>.cmd

8. Update database tier with latest patches. Refer to Section 5: Migrate Latest Code to Database Tier, for instructions.

3.2 Path B — Existing Release 12.2 customers (Below AD­TXK Delta 8 Codelevel)

Note: Follow Path B if your system has been upgraded to Oracle E­Business Suite Release 12.2 and you have applied an
earlier AD­TXK delta, but not yet applied R12.AD.C.Delta.8 and R12.TXK.C.Delta.8.

3.2.1 Prerequisite: Run ETCC

You must complete the tasks in Section 2 before performing the installation steps. You must execute the latest version of ETCC
on your database and the middle tier or the patch application procedure will fail. AD­TXK Delta 8 requires a number of
database bug fixes, to install and operate correctly. Failure to install critical database patches before applying AD­TXK Delta 8
may cause data dictionary corruption.

1. Run the ETCC MT checker (checkMTpatch.sh/checkMTpatch.cmd) on the E­Business Suite middle­tier nodes. Make a
note of any missing middle­tier patches.
2. Obtain any missing middle­tier patches but do not apply them yet. Missing middle­tier patches will be applied in the next
subsection 3.2.2 Run Installation Steps, step 3.

After you have run ETCC as applicable, proceed to the installation steps below.

3.2.2 Run Installation Steps

1. Source the run edition environment file.

UNIX:

$ . <EBS_ROOT>/EBSapps.env run

Windows:

C:\><RUN_BASE>\EBSapps\appl\envshell<CONTEXT_NAME>.cmd

2. Start a new online patching cycle.

$ adop phase=prepare

3. Apply the latest embedded application tier technology patches on the patch file system.

a. From a separate session, source the patch edition environment file.

UNIX:

$ . <PATCH_BASE>/EBSapps/appl/APPS<CONTEXT_NAME>.env

https://support.oracle.com/epmos/faces/DocumentDisplay?_adf.ctrl­state=e97om08b0_96&id=1617461.1 5/13
12/15/2016 Document 1617461.1

Windows:

C:\><PATCH_BASE>\EBSapps\appl\envshell<CONTEXT_NAME>.cmd

b. On the patch file system, apply the latest application tier technology patches documented in 'Section 4:
Application Tier Technology Patches and Bug Numbers' of My Oracle Support Knowledge Document 1594274.1,
Oracle E­Business Suite Release 12.2: Consolidated List of Patches and Technology Bug Fixes . Refer to My Oracle
Support Knowledge Document 1355068.1, Oracle E­Business Suite 12.2 Patching Technology Components Guide
for instructions on how to apply technology patches.

Note: The latest AD­TXK codelevel has a dependency on Oracle Fusion Middleware:
11.1.1.6: Patch 20642039
11.1.1.7: Patch 20756887
If you are applying Delta 8 to a system on a pre­Delta 7 AD­TXK codelevel, you must apply the Oracle Fusion
Middleware patch before proceeding with the AD and TXK patches. If you do not apply this patch, application
of the TXK patch will fail.

Note: If you are on Release 12.2.4 or lower and have applied the R12.AD.C.Delta.7 and R12.TXK.C.Delta.7
Release Update Packs and you are also moving to AD and TXK Delta 8 in preparation for Release 12.2.5 (or
above), part of the upgrade to Release 12.2.5 (or above) requires an upgrade to FMW 11.1.1.7 or above.
Therefore, the only patch that should be applied to the 11.1.1.6 webtier or oracle_common tier is Patch
20642039. If you are on AD and TXK Delta 6, Patch 20642039 should already be applied.

Note: You are applying the application tier technology patches to the patch file system because there is an
active patching cycle. This is in contrast to cases of applying patches in hotpatch mode, where they are
applied to the run file system.

If you have run the prepare phase in Step 2 above and you need to apply technology patches, you should
therefore apply them to the patch file system. However, you should not invoke any other adop actions such
as finalize, cutover, cleanup, or fs_clone in the patching cycle; these actions are executed in later steps, as
mentioned in the appropriate parts of this document.

c. Source the run edition environment file.

UNIX:

$ . <EBS_ROOT>/EBSapps.env run

Windows:

C:\><RUN_BASE>\EBSapps\appl\envshell<CONTEXT_NAME>.cmd

4. Unzip patches and run adgrants.

a. Download and unzip the following patches:
Patch 21841299 (R12.AD.C.Delta.8)
Patch 21830810 (R12.TXK.C.Delta.8)

Note: You should also download and unzip any applicable patches from Section 4: Apply Additional Critical
Patches.

b. Execute adgrants by following the instructions in the readme of Patch 21841299 (R12.AD.C.Delta.8).

5. Apply Patch 21841299 (R12.AD.C.Delta.8) (plus any additional critical patches – see note box).

https://support.oracle.com/epmos/faces/DocumentDisplay?_adf.ctrl­state=e97om08b0_96&id=1617461.1 6/13
12/15/2016 Document 1617461.1

Note: You will apply Patch 21841299 (R12.AD.C.Delta.8) in this step, and Patch 21830810 (R12.TXK.C.Delta.8) in
Step 6 below. You must apply them both in the same online patching cycle.

UNIX:

$ adop phase=apply patches=21841299

Note: As per subsection 4.1 Critical AD Patches, you should also add any applicable AD patches as a comma­
separated list of patches to this command. Ensure that you also add "merge=yes" to the end of your command, as
shown here:

$ adop phase=apply patches=21841299,<Your First AD Patch>,<Your Second AD Patch Number>

merge=yes

Windows:

C:\>adop phase=apply patches=21841299

Note: As per subsection 4.1 Critical AD Patches, you should also add any applicable AD patches as a comma­
separated list of patches to this command. Ensure that you also add "merge=yes" to the end of your command, as
shown here:

C:\>adop phase=apply patches=21841299,<Your First AD Patch>,<Your Second AD Patch Number>

merge=yes

6. Apply Patch 21830810 (R12.TXK.C.Delta.8) (plus any additional critical patches – see note box).

$ adop phase=apply patches=21830810

Note: As per subsection 4.2 Critical TXK Patches, you should also add any applicable TXK patches as a comma­
separated list of patches to this command. Ensure that you also add "merge=yes" to the end of your command, as
shown here:

$ adop phase=apply patches=21830810,<Your First TXK Patch>,<Your Second TXK Patch Number>
merge=yes

7. Apply Patch 19259764:R12.FND.C.

Note: This patch is not applicable if you are at

i. Oracle E­Business Suite Release 12.2.4 or above
ii. R12.ATG_PF.C.Delta.4 Release Update Pack (Patch 17909318) or above

UNIX:

$ adop phase=apply patches=19259764

Windows:

C:\>adop phase=apply patches=19259764

8. Complete the online patching cycle by running the following commands in the order shown.

UNIX:

https://support.oracle.com/epmos/faces/DocumentDisplay?_adf.ctrl­state=e97om08b0_96&id=1617461.1 7/13
12/15/2016 Document 1617461.1

$ . <EBS_ROOT>/EBSapps.env run
$ adop phase=finalize
$ adop phase=cutover
$ . <EBS_ROOT>/EBSapps.env run
$ adop phase=cleanup

Windows:

C:\><RUN_BASE>\EBSapps\appl\envshell<CONTEXT_NAME>.cmd
C:\>adop phase=finalize
C:\>adop phase=cutover
C:\><EBS_ROOT>\EBSapps.cmd run
C:\>adop phase=cleanup

9. Synchronize file systems

If you applied application­tier technology patches in Step 3, then you must synchronize the file systems using the
command shown below. This action copies the new run edition code and configuration to the other file system.

$ adop phase=fs_clone

Note: If you are running Oracle HTTP Server on a privileged port, then you must perform additional tasks after
running fs_clone. See: Requirements When Running Oracle HTTP Server on a Privileged Port, Oracle E­Business
Suite Maintenance Guide .

10. Update database tier with latest patches. Refer to Section 5: Migrate Latest Code to Database Tier, for instructions.

Section 4: Apply Additional Critical Patches

You should periodically check this Document 1617461.1 on My Oracle Support for updates.

4.1 Critical AD Patches

Patch 24578455:R12.AD.C
Patch 24494551:R12.AD.C
Patch 25025325:R12.AD.C

4.2 Critical TXK Patches

Patch 18525466:R12.TXK.C
Patch 23569114:R12.TXK.C
Patch 23705992:R12.TXK.C

4.3 Product Interoperability Patches

If you use the products and features listed in the table below, you must apply the product interoperability patches before using
them.

Product Feature Product Interoperability Patches — Required

R12.SCP_PF.C.delta.6 or Release 12.2.5 customers

Patch 24965740:R12.MSC.C
R12.SCP_PF.C.delta.4 or Release 12.2.4 customers
Oracle Patch 24966675:R12.MSC.C
SPP inline
Service
forecasting Note that you do not need to apply this patch if both of the following are true:
Parts
function
Planning You are an existing Release 12.2, new installation or upgrade customer.
https://support.oracle.com/epmos/faces/DocumentDisplay?_adf.ctrl­state=e97om08b0_96&id=1617461.1 8/13
12/15/2016 Document 1617461.1

Before using the SPP inline forecasting function, you will be applying a patch or release
update pack that includes R12.SCP_PF.C.Delta.7 (or higher). For example,
R12.SCM_PF.C.Delta.6 (or higher) or Release 12.2.6.

Section 5: Migrate Latest Code to Database Tier

Update all database tier nodes with the latest code, by performing the following steps:

1. On the Application Tier (as the APPLMGR user):

a. Source the environment variables for Oracle E­Business Suite.

UNIX

$ . ./<APPL_TOP>/APPS<CONTEXT_NAME>.env

Windows

C:\><APPL_TOP>\envshell<CONTEXT_NAME>.cmd

b. Execute the admkappsutil.pl utility to create the appsutil.zip file in <INST_TOP>/admin/out.

$ perl <AD_TOP>/bin/admkappsutil.pl

2. On the Database Tier (as the ORACLE user):

a. Source the environment variables for RDBMS ORACLE_HOME.

UNIX

$ cd <RDBMS ORACLE_HOME>
$ . ./<RDBMS ORACLE_HOME>/<CONTEXT_NAME>.env

Windows

C:\><RDBMS ORACLE_HOME>\<CONTEXT_NAME>.cmd

b. Copy or FTP the appsutil.zip file to <RDBMS ORACLE_HOME>.

c. Uncompress appsutil.zip, under <RDBMS ORACLE_HOME>.

$ cd <ORACLE_HOME>
$ unzip ­o appsutil.zip

d. Run AutoConfig on <RDBMS ORACLE_HOME>.

Note: For more details, refer to Oracle E­Business Suite Setup Guide, Release 12.2.
3. Run AutoConfig on the run file system.

On the Application Tier (as the APPLMGR user):

Run AutoConfig on the run file system.

Note: Before running AutoConfig, customers using the AutoConfig Customizations feature must merge any
customizations with the AutoConfig templates provided via this patch.

https://support.oracle.com/epmos/faces/DocumentDisplay?_adf.ctrl­state=e97om08b0_96&id=1617461.1 9/13
12/15/2016 Document 1617461.1

Note: For exact details on how to run AutoConfig and how to create appsutil.zip, refer to the Oracle E­
Business Suite Setup Guide, Release 12.2.

Change Log

Date Description of Change

2016­
Added Patch 25025325:R12.AD.C to subsection 4.1 Critical AD Patches
12­07

2016­
Updated the table within subsection 4.3 Product Interoperability Patches
11­18

2016­
Added Patch 24494551:R12.AD.C to subsection 4.1 Critial AD Patches
11­07

2016­
Added Patch 23569114:R12.TXK.C and Patch 23705992:R12.TXK.C to subsection 4.2 Critical TXK Patches
10­25

2016­ Added Patch 24578455:R12.AD.C to subsection 4.1 Critical AD Patches

09­23 Added Patch 18525466:R12.TXK.C to subsection 4.2 Critical TXK Patches

2016­ Replaced R12.AD.C.Delta.7 and R12.TXK.C.Delta.7 content with R12.AD.C.Delta.8 and R12.TXK.C.Delta.8
09­15 content.

2016­ Minor grammatical and syntax updates through­out the document.

07­12 Updated change log date formatting.

2016­
Removed patches 22503374:R12.AD.C and 22567833:R12.AD.C from subsection 4.1 Critical AD Patches.
04­01

2016­
Added critical patch 22700342:R12.AD.C to subsection 4.1 Critical AD Patches.
03­31

2016­
Added to critical patches to subsection 4.1 Critical AD Patches.
03­08

2016­
Changed reference in Section 3.2.2, Step 6, from Patch 21846184:R12.TXK.C to Patch 22363475:R12.TXK.C.
02­22

2016­ Updated document for the release of StartCD 12.2.0.51 (Patch 22066363, RAPID INSTALL STARTCD
02­18 12.2.0.51) and Patch 22495069:R12.TXK.C.

2016­
Updated subsection 3.3.1 Prerequisite: Run ETCC.
01­27

2016­
Revised step 5, within subsection 3.1.2 of Path A.
01­14

https://support.oracle.com/epmos/faces/DocumentDisplay?_adf.ctrl­state=e97om08b0_96&id=1617461.1 10/13
12/15/2016 Document 1617461.1

2016­ Added subsection 3.3 Path C ­ Existing Release 12.2 Customers (On AD­TXK Delta 7 Codelevel).
01­13 Replaced all occurrences of Patch 21841288 with Patch 22123818.
Replaced all occurrences of Patch 21846184 with Patch 22363475.

2015­
Added Patch 22217317:R12.TXK.C to subsection 4.2 Critical TXK Patches.
11­20

2015­ Replaced R12.AD.C.Delta.6 and R12.TXK.C.Delta.6 content with R12.AD.C.Delta.7 and R12.TXK.C.Delta.7
10­14 content.

Added the following subsections regarding ETCC:

2015­
3.1.1 Prerequisite: Run ETCC
08­26
3.2.1 Prerequisite: Run ETCC

2015­ Replaced Patch 20976867:R12.FND.C with Patch 19259764:R12.FND.C in subsection 3.2 Path B ­ Existing
08­17 Release 12.2 customers (Below AD­TXK Delta 6 Codelevel).

Updated Step 4 in subsection 3.1 Path A — Upgrade and New Installation Customers and subsection 3.2 Path
B ­ Existing Release 12.2 customers (Below AD­TXK Delta 6 Codelevel).
2015­
Replaced Patch 19259764:R12.FND.C with Patch 20976867:R12.FND.C in subsection 3.2 Path B ­ Existing
08­13
Release 12.2 customers (Below AD­TXK Delta 6 Codelevel).
Added Section 5: Known Issues.

2015­ In Section 3, replaced Oracle Fusion Middleware patch 19462638 with 11.1.1.6 patch 20642039 and 11.1.1.7
08­06 patch 20756887.

2015­
Added critical patch 20864702:R12.TXK.C to subsections 3.1 and 3.2.
08­03

2015­
Minor copyright update was made at the bottom of the document.
07­01

2015­
Added a critical patch to subsection 4.1 Critical AD Patches.
06­18

2015­
Updated step 6 in both Paths A and B to include patch 20677045:R12.TXK.C.
06­08

2015­ Removed step 7 of subsection 3.1 Path A — Upgrade and New Installation Customers. This step was to apply
05­11 Patch 19259764:R12.FND.C.

2015­
Minor update to the 2nd paragraph within Section 1: Preparation.
04­23

2015­
Added a critical patch to subsection 4.1 Critical AD Patches.
03­19

2015­ Updated the document number for Oracle E­Business Suite Applications DBA and Technology Stack Release
03­18 Notes for R12.AD.C.Delta.6 and R12.TXK.C.Delta.6.
https://support.oracle.com/epmos/faces/DocumentDisplay?_adf.ctrl­state=e97om08b0_96&id=1617461.1 11/13
12/15/2016 Document 1617461.1

2015­
Replaced content with R12.AD.C.Delta.6 and R12.TXK.C.Delta.6 content.
03­17

2014­
Slightly modified the title of Section 2.
12­08

2014­
Added Patch 19803392:R12.TXK.C and Patch 20158287:R12.TXK.C to steps 4 and 6 in paths A, B, and C.
12­05

Amended text in introductory note box at start of document.

2014­ Amended text of Section 2.
12­02 Slightly amended the wording of the note boxes that start subsections 3.1, 3.2, and 3.3.
Added new ETCC note boxes (same content in each) just after start of subsections 3.1, 3.2, and 3.3.

2014­
Corrected several references from Patch 20034256:R12.AD.C.Delta.5 to Patch 20034256:R12.AD.C.
12­01

Added a note at the top of Section 3.

Replaced Patch 19581770 with Patch 20034256.
2014­ Replaced Patch 19445058 with Patch 20043910.
11­26 Replaced Patch 18283295 with Patch 20034256 in adgrants execution steps, as Oracle is shipping a new
version of the adgrants.sql.
In Path C, added step 4b to execute adgrants.

2014­ In Section 3, moved note about latest AD­TXK codelevel having a dependency on Oracle Fusion Middleware
10­28 Patch 19462638 above existing note.

Republished document to accommodate release of AD and TXK Delta 5 bundle fixes (19581770:R12.AD.C
and 19445058:R12.TXK.C respectively).
Removed database version numbers from Section 2: Apply Required Technology Patches.
2014­ Added subsection 3.3 Path C — Existing Release 12.2 Customers (On AD­TXK Delta 5 Codelevel).
10­20 Added a note to the step to apply the latest embedded application tier technology patches on the patch file
system, in all paths.
Removed Windows­specific patches from paths A and B.
Removed step 9 of 3.1 Path A — Upgrade and New Installation Customers.

2014­
Made various updates to wording throughout document.
10­16

2014­
Updated subsection 4.1 Critical AD Patches with instruction to periodically check the document for updates.
10­06

2014­
Updated UNIX code of step 1 of 3.1 Path A — Upgrade and New Installation Customers.
09­15

2014­
Added a note to step 9 of 3.1 Path A — Upgrade and New Installation Customers.
09­04

2014­
Updated step 4 to include Patch 19259764:R12.FND.C.
09­02

https://support.oracle.com/epmos/faces/DocumentDisplay?_adf.ctrl­state=e97om08b0_96&id=1617461.1 12/13
12/15/2016 Document 1617461.1

2014­ Added critical Patch 18942757:R12.TXK.C to Section 4.2 Critical TXK Patches.
08­20

Updated the first paragraph in Section 2: Apply Required Technology Patches.

2014­
Updated step 7 in path A (Section 3: Apply the R12.AD.C.Delta.4 and R12.TXK.C.Delta.4 Release
07­24
Update Packs) to make it conditional and added a Note to specify the condition.

2014­ Added step to apply Patch 19259764:R12.FND.C to all paths, in Section 3: Apply the R12.AD.C.Delta.4
07­22 and R12.TXK.C.Delta.4 Release Update Packs.

2014­
Added the second paragraph in Section 1: Preparation.
07­21

2014­
Updated step 8 in Section 3.1 Path A — Upgrade and New Installation Customers.
07­18

Added Step 8 (Synchronize the file systems) to Section 3.1 Path A — Upgrade and New Installation
2014­ Customers.
07­17 Removed note at the top of the document, indicating that Oracle doesn't support Windows. Added critical
Windows platform patches to Path A and Path B.

2014­
Retitled document and published with R12.AD.C.Delta5 and R12.TXK.C.Delta.5 content.
07­15

My Oracle Support Knowledge Document 1617461.1 by Oracle E­Business Suite Development

Copyright © 2014, 2015, 2016, Oracle and/or its affiliates. All rights reserved.

Didn't find what you are looking for?

https://support.oracle.com/epmos/faces/DocumentDisplay?_adf.ctrl­state=e97om08b0_96&id=1617461.1 13/13