EBS Upgrade
EBS Upgrade
Upgrade Guide
Release 12.0 and 12.1 to 12.2
Part No. E73540-15
June 2021
Oracle E-Business Suite Upgrade Guide, Release 12.0 and 12.1 to 12.2
Primary Author: Kevin Brown, Clara Jaeckel, Elke Phelps, Sharath Vishwanath
Contributing Author: John Abraham, Sankar Akshathala, Aditya Bansal, Santiago Bastidas, Sanjay
Bheemasenarao, Jason Brincat, Richard Chang, Robert Farrington, Sandeep Goel, Kyle Harris, David Heisler,
Paul Holman, Kevin Hudson, Radha Kalakurthy, Hyun Kim, Pratima Mahtani, Dorothy Mak, Ruth Mamo,
Swathi Mathur, Anil Modwel, Udayan Parvate, Kavuri Ramanjaneyulu, Sreedhar Ramasahayam, Sudha Rao,
Scot Robson, Nitin Somani, Sujai Veerabhadraiah, Sriram Veeraraghavan, David Vickers, Millie Wang,
Melody Yang
This software and related documentation are provided under a license agreement containing restrictions on
use and disclosure and are protected by intellectual property laws. Except as expressly permitted in your
license agreement or allowed by law, you may not use, copy, reproduce, translate, broadcast, modify, license,
transmit, distribute, exhibit, perform, publish, or display any part, in any form, or by any means. Reverse
engineering, disassembly, or decompilation of this software, unless required by law for interoperability, is
prohibited.
The information contained herein is subject to change without notice and is not warranted to be error-free. If
you find any errors, please report them to us in writing.
If this is software or related documentation that is delivered to the U.S. Government or anyone licensing it on
behalf of the U.S. Government, then the following notice is applicable:
U.S. GOVERNMENT END USERS: Oracle programs, including any operating system, integrated software,
any programs installed on the hardware, and/or documentation, delivered to U.S. Government end users are
"commercial computer software" pursuant to the applicable Federal Acquisition Regulation and agency-
specific supplemental regulations. As such, use, duplication, disclosure, modification, and adaptation of the
programs, including any operating system, integrated software, any programs installed on the hardware,
and/or documentation, shall be subject to license terms and license restrictions applicable to the programs. No
other rights are granted to the U.S. Government.
This software or hardware is developed for general use in a variety of information management applications.
It is not developed or intended for use in any inherently dangerous applications, including applications that
may create a risk of personal injury. If you use this software or hardware in dangerous applications, then you
shall be responsible to take all appropriate fail-safe, backup, redundancy, and other measures to ensure its
safe use. Oracle Corporation and its affiliates disclaim any liability for any damages caused by use of this
software or hardware in dangerous applications.
Oracle and Java are registered trademarks of Oracle and/or its affiliates. Other names may be trademarks of
their respective owners.
Intel and Intel Xeon are trademarks or registered trademarks of Intel Corporation. All SPARC trademarks are
used under license and are trademarks or registered trademarks of SPARC International, Inc. AMD, Opteron,
the AMD logo, and the AMD Opteron logo are trademarks or registered trademarks of Advanced Micro
Devices. UNIX is a registered trademark of The Open Group.
This software or hardware and documentation may provide access to or information about content, products,
and services from third parties. Oracle Corporation and its affiliates are not responsible for and expressly
disclaim all warranties of any kind with respect to third-party content, products, and services unless
otherwise set forth in an applicable agreement between you and Oracle. Oracle Corporation and its affiliates
will not be responsible for any loss, costs, or damages incurred due to your access to or use of third-party
content, products, or services, except as set forth in an applicable agreement between you and Oracle.
For information about Oracle's commitment to accessibility, visit the Oracle Accessibility Program website at
http://www.oracle.com/pls/topic/lookup?ctx=acc&id=docacc.
Oracle customers that have purchased support have access to electronic support through My Oracle Support.
For information, visit http://www.oracle.com/pls/topic/lookup?ctx=acc&id=info or visit http://www.oracle.
com/pls/topic/lookup?ctx=acc&id=trs if you are hearing impaired.
Contents
Preface
iii
General Sizing Guidelines for the Database and Application Tier.............................. 3-12
JVM Parameter Settings for Java on WLS Web Tier.................................................... 3-14
Example Upgrade........................................................................................................ 3-15
Advanced Configuration................................................................................................... 3-18
Preparing Customizations....................................................................................................... 3-19
Customizing Help Files......................................................................................................3-22
Schemas Not Used by Oracle E-Business Suite Release 12.2.............................................. 3-22
Preparing External Integrations.............................................................................................. 3-24
Preparing Third-Party Integrations........................................................................................ 3-26
EBS 12.2 Upgrade Readiness Checker - Database Tier (EURC-DT).......................................3-26
iv
Backing Up Oracle E-Business Suite...................................................................................... 5-21
Secure Configuration.............................................................................................................. 5-21
System Maintenance Tasks..................................................................................................... 5-23
Oracle XML Publisher Tasks.................................................................................................. 5-25
Post-Upgrade Steps of Oracle E-Business Suite Release Update Pack for Release 12.2........5-26
Mandatory Post-Upgrade Steps for All Upgrade Customers................................................. 5-26
Additional Tasks..................................................................................................................... 5-27
Index
v
Send Us Your Comments
Oracle E-Business Suite Upgrade Guide, Release 12.0 and 12.1 to 12.2
Part No. E73540-15
Oracle welcomes customers' comments and suggestions on the quality and usefulness of this document.
Your feedback is important, and helps us to best meet your needs as a user of our products. For example:
• Are the implementation steps correct and complete?
• Did you understand the context of the procedures?
• Did you find any errors in the information?
• Does the structure of the information help you with your tasks?
• Do you need different information or graphics? If so, where, and in what format?
• Are the examples correct? Do you need more examples?
If you find any errors or have any other suggestions for improvement, then please tell us your name, the
name of the company who has licensed our products, the title and part number of the documentation and
the chapter, section, and page number (if available).
Note: Before sending us your comments, you might like to check that you have the latest version of the
document and if any concerns are already addressed. To do this, access the new Oracle E-Business Suite
Release Online Documentation CD available on My Oracle Support and www.oracle.com. It contains the
most current Documentation Library plus all documents revised or released recently.
Send your comments to us using the electronic mail address: [email protected]
Please give your name, address, electronic mail address, and telephone number (optional).
If you need assistance with Oracle software, then please contact your support representative or Oracle
Support Services.
If you require training or instruction in using Oracle software, then please contact your Oracle local office
and inquire about our Oracle University offerings. A list of Oracle offices is available on our Web site at
www.oracle.com.
vii
Preface
Intended Audience
Welcome to Release 12.0 and 12.1 to 12.2 of the Oracle E-Business Suite Upgrade Guide.
This book provides instructions for upgrading existing Oracle E-Business Suite Release
12.0 and 12.1 instances to Oracle E-Business Suite Release 12.2. This book also provides
instructions for upgrading an existing Oracle E-Business Suite Release 12.1.3 instance to
Oracle E-Business Suite Release 12.2 on Oracle Cloud infrastructure. This delivers the
unified driver that you use to upgrade the technology stack and products to Release
12.2.
This book is intended as a guide for the database administrator and the application
specialists who are responsible for upgrading to Release 12.2 of Oracle E-Business Suite.
See Related Information Sources on page x for more Oracle E-Business Suite product
information.
Documentation Accessibility
For information about Oracle's commitment to accessibility, visit the Oracle
Accessibility Program website at http://www.oracle.com/pls/topic/lookup?
ctx=acc&id=docacc.
ix
Structure
1 Overview of the Upgrade
2 Understanding Upgrade Impact and Changes
3 Planning and Performing Pre-Upgrade Tasks
4 Performing the Upgrade
5 Performing Post-Upgrade Tasks
A Managing Concurrent Processes
x
If you are looking for Refer to these documents...
information about...
Installation and upgrade Oracle E-Business Suite Installation Guide: Using Rapid Install
xi
* Available only on My Oracle Support.
Patch readme files may also contain information about additional recommended
documentation.
xii
1
Overview of the Upgrade
The following diagram describes the high-level overview of the tasks described in this
guide:
2. Lay Down the Oracle E-Business Suite Release 12.2 File System.
• Use Rapid Install to lay down the file system and technology stack
• Apply the latest Oracle E-Business Suite Release 12.2 Release Update Pack
(RUP)
Note: You must apply the 12.2.3 or later Release Update Pack
(RUP) to your existing Release 12.2 system for production use.
RUPs are released periodically. Each one is cumulative and
delivers error corrections and system updates, not only for the
most current release update pack, but also for all the RUPs that
precede it. Oracle highly recommends that when planning your
upgrade you plan to upgrade to the latest RUP available.
You can keep current on the latest release information, as well
as new RUP announcements and other updates that may affect
• Secure configuration
• DMZ configuration
The required steps are covered in detail in the following chapters in this upgrade guide:
• Performing the Upgrade
After you have optimized your upgrade plan and finalized testing, you will have an
estimate for the amount of time required to perform the upgrade in production. You
can then schedule the time required for the upgrade to your production environment.
• Forms services
In Release 12.2, Web and Forms services are provided by Oracle Application Server. They
are no longer servers in the sense of being a single process.
Web Services
The Web services component of Oracle Application Server processes requests received
over the network from the desktop clients, and includes the following major
components:
• Web Listener (Oracle HTTP Server powered by Apache)
The Web listener component of the Oracle HTTP server accepts incoming HTTP
requests (for particular URLs) from client browsers, and routes the requests to WLS.
When possible, the Web server services the requests itself. For example, returning the
HTML to construct a simple Web page. If the page referenced by the URL requires
advanced processing, then the listener passes the request on to the servlet engine which
contacts the database server as needed.
An important change in Release 12.2 is the employment of the Oracle WebLogic Server
for many system management and configuration tasks. Configuration using the Oracle
WLS Console in Release 12.2 supplements, but does not replace the traditional use of
• Oracle FMW 11g Java Required Files (JRF) libraries (except the use of ADF and
MDS 11g)
• JDK 7.0
• Oracle 10g (10.1.2) Applications Server for Oracle E-Business Suite Forms based
Applications
Online Patching
Oracle E-Business Suite Release 12.2 introduces Online Patching, a new feature that
greatly reduces the downtime that was needed in previous releases for application of
Release Update Packs (RUPs), Critical Patch Updates (CPUs), and other patches and
bug fixes of various kinds.
Key Features
• In Release 12.2, all patching operations are carried out while the applications are in
use and users are online.
• Patching is performed using the new adop (AD Online Patching) utility.
• A short period of downtime is required, but this amounts to little more than a
restart of the services: the time the applications are unavailable is measured in
minutes rather than hours, and this can be specified to be at the most convenient
time.
Principles
In essence, online patching is performed as follows:
1. A copy is made of the running system.
2. Patches are applied to the copy while users continue to access the running system.
This introduces the concept of a patching cycle that consists of several phases, in contrast
to the model used in previous releases. These phases are denoted prepare, apply,
finalize, cutover, and cleanup.
Note: For more information about online patching principles, see Oracle
Implementation
Any mechanism that uses a copy of the running application must take into account that
an Oracle E-Business Suite application comprises both code and data, stored in the file
system and database.
The file system is the easier of the two to cater for, simply requiring an additional copy
to be created and maintained. The resulting dual file system consists of one file system
that is used by the running system and another one that is either currently being
patched, or (as will be the case for most of the time) standing ready to be patched. The
two file systems swap roles at the end of each patching cycle, with the transition between
them being managed by AutoConfig.
Creating a copy of the database portion of the running applications system is more
complex. It has been accomplished by taking advantage of the Oracle Database 11g R2
Edition-Based Redefinition (EBR) feature. This allows an application to efficiently store
multiple copies (editions) of its application definition in the same database, and thereby
enables online upgrade of the database tier.
The database patch edition only comes into existence during a patching cycle, and
becomes the new run edition at end of the cycle. The former database run edition (the
old edition) and the obsolete objects it contains are discarded at the end of a patching
cycle, and the space reclaimed during the cleanup phase.
Tools
Patching is performed by running the new adop (AD online patching) tool. This tool
invokes the adpatch utility that was run directly in previous releases of Oracle E-
Business Suite.
The adop tool orchestrates the entire patching cycle, and can be used to run individual
phases as required.
Note: For full details of adop features and options, refer to the Patching
section of Oracle E-Business Suite Maintenance Guide.
Customizations
Customized environments require additional attention during an upgrade. The
instructions in this guide assume that you have followed the standards for customizing
Oracle E-Business Suite.
Oracle E-Business Suite 12.2 introduces a new set of compliance, code, and patching
standards that customizations must adhere to. The Online Patching Readiness Reports
provide a set of utilities that report any compliance issues.
• Full Compliance (Full) - These checks indicate whether an object can be patched
using Online Patching. Objects which do not meet full compliance may have
limitations in how they can be patched, or may need to be patched using downtime
patching. Full compliance also requires that all minimal compliance checks are
passed. Custom code that will only be patched using downtime patching does not
need to meet the full compliance level.
• Steps you can take to verify that all transactional data is upgraded as expected
Upgrade By Request
For some Oracle E-Business Suite products, upgrade planning includes choosing the
most active set of data for upgrade processing. Then, you can upgrade historical data
that was omitted from the upgrade at a later date, or when it is needed. For example,
you might include only the last fiscal year in the upgrade to Release 12.2, and then
Product Name
* Oracle CAD-View 3D
* Oracle HR Intelligence
* A migration plan exists for customers who have purchased these products in earlier
releases. Contact your Sales Representative or Account Manager for more information.
** Customers continuing to use Oracle Student Recruiting and Oracle Student Systems
should not upgrade to this release.
Support will be provided to existing customers on earlier releases, in accordance with
the Oracle Lifetime Support Policy.
*** Oracle's Daily Business Intelligence (DBI), Balanced Scorecard (BSC), and Embedded
Data Warehouse (EDW) are not offered with Oracle E-Business Suite Release 12.2.
Support will be provided to existing customers on Oracle E-Business Suite Release 12.1.
x, 12.0.x and older versions of DBI, BSC, and EDW according to Oracle's published
lifetime support policies.
The discussions of the functional aspects of the upgrade in this appendix are arranged
by products within the Financials and Procurement product family.
Subledger Accounting
This section is applicable to those scenarios where historical release 11i data was not
completely upgraded to release 12 during Oracle E-Business Suite Release 12.0 and
Release 12.1 upgrades. You can upgrade this data anytime, or after upgrading to
Release 12.2. For more information, refer to SLA: Upgrade Historical Subledger Transaction
Accounting Program (XLAONDEUPG) (Doc ID: 1376752.1) and Oracle E-Business Suite
Upgrade Guide - Release 11i to 12.2.
Advanced Collections
Changes to Oracle Advanced Collections in the upgrade are described in this section.
Multiple Level Strategy Support
Advanced Collections allows you to define different strategy levels by Operating Unit
separate from the System level. The strategy levels can also be overridden at Party level.
Advanced Collections supports the setting for certain Operating Units by Dunning and
certain Operating Units by Strategy.
Stage Dunning Support
Advanced Collections supports the Staged Dunning method separate from the Days
Overdue method. In addition, while creating Overdue Dunning Plans, you can specify
the Include Current, Include Disputed Items, Include Unapplied Receipts, and Use
Grace Days options.
Collections Manager Functionality
Collections Manager Functionality has been rewritten using OA Framework which
allows sorting and filtering for a particular account.
New Scoring Engines
A new scoring engine is seeded with Pre-delinquency status at Invoice level. In
addition, a Quick scoring engine has been added that only processes invoices closed in
Note: This appendix describes some of the ways the upgrade changes
your existing products. Oracle assumes that you have read about the
new features and products delivered in this release, which is included
in the product-specific Release Content Documents (RCDs) and TOI on
My Oracle Support.
The discussions of the functional aspects of the upgrade in this chapter are arranged by
products within the HRMS product family.
Oracle Payroll
Sparse Matrix
Sparse Matrix functionality is automatically enabled in Release 12.2. This effectively
prevents the creation of null run result values if all run result values are null for the
given run result. There is no need to run the ENABLE_SPARSE_MATRIX upgrade
program.
Review the Sparse Matrix Null Result Values Upgrade program.
It is enabled for each legislation and requires a row in the pay_upgrade_legislations
table for the definition SPARSE_MATRIX. The process purges old (null) run result
values that would not have been created if the Sparse Matrix functionality had been
used within the Payroll processes (such as Run, QuickPay, and so on.)
2. Suitability Matching
3. Talent Profile
The discussions of the functional aspects of the upgrade in this chapter are arranged by
products within the Supply Chain Management product family.
• Supply Type
• Subinventory
• Locator
You can choose to change these attributes when you create a new common structure,
change an existing common structure, or add or update a common structure when
using the Bill Import open interface program.
The profile option EGO: Enable Oracle Collaborative Development should not be
enabled from Release 12 onwards.
You can now only update structure and component attribute values using the Product
Workbench.
Advanced Search
The advanced search function has been enhanced so that searches using the operator
"contains" are now case-insensitive.
Web ADI Integration
Columns created within a Microsoft Excel spreadsheet during the information export
process now match the column formats of the display format selected.
Item Organization Assignments
In prior releases, when assigning items to organizations, some of the item primary
attributes were defaulted from the master item during organization assignment and
could not be changed. In this release, you can now edit the following attributes during
organization assignment:
• Tracking
• Pricing
• Defaulting
Additional Information
For additional information, refer to the Oracle Product Hub Implementation Guide and the
Oracle Product Hub User's Guide.
Language Status
Additional space for each non-American English language will be required in the
database to complete the upgrade. It is not possible to predict the amount of additional
space your system will need, because the space depends on factors such as the database
character set, the number of active languages other than American English, and in
particular the volume of transaction data in the system.
You must retain your existing Applications Release status until the entire upgrade
process (including the post-upgrade and finishing steps) is complete. The base language
must also remain the same, and new languages cannot be activated.
After the upgrade process is complete, you can activate new languages or change the
base language. Oracle does not support disabling or removing installed or enabled
languages.
Reference Information
It is very important that you read the documentation associated with this release. In
addition, you may also find it useful to review any presentation materials on upgrade
technology and white papers on Multi-org, and links to various Consulting services as
well as Oracle University training courses.
Application specialists and functional users should pay special attention to the Release
Content Documents (RCDs), Electronic Technical Reference Manuals (eTRMs), and
Transfer of Information (TOI) documentation for the products that are active in your
system. This information describes new features and functionality in Release 12.2.
• Oracle Reports
Operating System
Oracle E-Business Suite Release 12.2 requires a 64-bit operating system. If you have not
already done so, then you must plan for and upgrade the operating system of your
Oracle E-Business Suite application and database tiers to a 64-bit operating system.
Note: In this guide, the term "UNIX" refers to all variants of that
operating system, including Linux.
For all the nodes of a particular tier, either application tier nodes or database RAC
nodes, Oracle recommends that you use the same operating system kernel parameter
settings when using identical machines, or adjust the settings based on the machines'
load. Using the same operating system kernel parameter settings simplifies
management and maintenance.
Note: When you run Rapid Install as part of an upgrade, the upgrade
process is performed with only one application tier and one database
Networking
The key networking requirement is for the hosts file to include an entry for the
installation machine, formatted as follows:
<IP address> <host name>.<domain name> <host name>
Hardware Requirements
The following section describes hardware requirements for upgrading to Oracle E-
Business Suite Release 12.2.
CPU Requirements
Note: Unless explicitly noted otherwise, Oracle E-Business Suite
documentation uses the term "CPU" to mean an actual CPU core rather
than a logical core.
CPU requirements for running Oracle E-Business Suite for the database and application
tiers depend on the following factors, which are listed in no particular order:
• Required response times of the business
• Number of concurrent manager processes and the types of jobs that they are
running
The number of CPUs and cores needed to support Oracle E-Business Suite depends on
the specific platform implementation, and whether or not hyperthreading is in use.
Two useful formulae are:
• Actual Cores Count = Processor Count * CoresCountPerProcessor
Memory Requirements
Memory requirements for Oracle E-Business Suite depend on both the application and
database tiers.
• JVM Memory
• Forms Memory
• Resident Memory
• OS Kernel Memory
Aside from the stack, the two main contributors to the application tier memory are the
JVM memory and Forms memory (the frmweb process). For every 150 to 180 self-
service users, you should allow 2 GB of JVM heap and 2 CPUs. The Forms Processes
memory is equal to the (Number of Forms users) * 40 MB.
The memory required per machine also depends on the number of application
machines in your deployment. For general usage, it is not recommended that you
allocate very large heap sizes. Instead, add more managed instances in the cluster to
scale up to the target concurrency levels.
• Any non-Oracle software that has to run on the machine (this is not recommended)
When sizing the environment in which you will install Oracle E-Business Suite, you
should aim to allow for any expected growth in usage over the planned lifetime of your
system. It is, however, possible to scale up a system later to meet additional
requirements subsequent to installation, either by adding nodes (machines) to the
application tier or employing Oracle Real Application Clusters (Oracle RAC) on the
database tier.
Database node file system (Fresh install) 90 GB (includes database files and 12cR1
database Oracle home).
Database node file system (Vision Demo 200 GB (includes database files and 12cR1
database) database Oracle home).
Applications node file system (OracleAS 10.1.2 64 GB (for dual file system). Also, see Note
Oracle home, Oracle Fusion Middleware below for language (NLS) considerations.
Oracle home, COMMON_TOP, APPL_TOP,
and INST_TOP)
Stage Area
For a production database installation, running Rapid Install from a stage area requires
at least 48 GB to accommodate the file system and database files in the stage area. See
Setting Up the Stage Area, page 4-7.
Tip: Log and output files are not automatically purged. The size of
these files can increase quickly, which can impact the performance of
your system. Determine a strategy for archiving and purging these files
after the installation, particularly for files in the trace directories, and
monitor the disk space they consume to determine how much space
you may need in the future.
Other Files
The total disk space estimate must account for the requirements of files other than those
directly related to Oracle E-Business Suite. For example:
• Operating system software
• Online backups
To monitor the I/O performance, you should use OS tools like iostat or sar (Unix)
during your test upgrade. Use similar tools for other operating systems, for example
Performance Monitor for Windows. You can also monitor I/O performance on your
Database Size
Database sizing is dependent on the following main factors:
• Current user distribution along with transaction rates
You should ensure that proper planning is in place for database footprint management,
in conjunction with appropriate purge and archive policies defined as part of your
instance management strategy.
To estimate the increase in required disk space for upgrading, consider the products,
the number of languages being installed, and changes in the data model. For example,
in a test upgrade of the largest Oracle production system (oraprod), the database
increased 10-20 percent. In a test upgrade, the Vision database increased 5 percent.
Tablespace Sizing
Make sure you allocate sufficient tablespace.
Block Size
This release requires a database block size of 8K. In addition to providing significant
performance improvement, this setting accommodates the Oracle E-Business Suite
indexes that require this block size.
• Database and application tier sizing information, based on a test upgrade from
Oracle E-Business Suite Release 12.1.3 (with a 146 GB database) to Release 12.2.5
• You should always size your systems based on tests using representative data and
workloads for your own environments. The most reliable strategy to ensure that the
hardware is sized appropriately is to install a test environment, and then conduct a
benchmark test with a configuration, product mix, and user load that simulates
your own current and expected workloads. These conditions can help verify
performance before you install your production-ready environment.
• In addition to the memory needed based on the sizing guidelines given, you should
allow an extra 2 GB of free memory for the database tier machine, and an extra 3 GB
of free memory for the application tier machine (for Online Patching).
Note: The figures in this table do not take into account any Online
Patching requirements.
0-10 4 GB 2 6 GB 2
100-200 8 GB 2 8 GB 2
200-400 12 GB 4 10 GB 4
400-800 20 GB 8 14 GB 8
100 4 GB
200 8 GB
400 16 GB
800 32 GB
On the database tier, there is one Oracle Forms session per open form, and each of these
sessions requires approximately 30 MB of PGA memory.
The following table lists the memory required for different numbers of sessions:
100 3 GB
200 6 GB
400 12 GB
800 24 GB
• Only the value of Xmx has an effect on response time. Changing the value of Xms
does not have an effect.
• Each instance will be able to utilize a separate connection pool. In essence, you need
to maintain a balance between the allocated JVM heap size per instance and the
available connection pool for that instance.
Careful sizing is needed for the concurrent manager components, especially Java
concurrent programs. If you will be processing relatively large volumes of data, you
may need to increase the Xms/Xmx settings for the Java concurrent programs. This is
normally done via the options field of the define concurrent program screen. Note that
when you increase the number of workers, the memory requirements may increase
significantly: this is because each Java concurrent worker will require at least an amount
of memory specified by the value of Xms.
Example Upgrade
This section provides sample figures for an upgrade from Oracle E-Business Suite
Release 12.1.3 to Release 12.2.5. The figures were derived using Oracle's hardware and
networking infrastructure, and are provided for general guidance only.
Automatic Workload Repository Advisory sections from test runs should be used to
size relevant database memory components for the actual upgrade.
• Number of CPUs: 24
Note: The database tier and application tier are on the same machine in
this example.
• Shared pool: 1 GB
• PGA: 10 GB
• Log buffer: 30 MB
• job_queue_processes: 24
Note: During the upgrade of the Admin Tier, the batchsize and number
of workers used were 1000 and 24 respectively.
The reduction in database size is a result of obsolete schemas and objects being
removed from the upgraded system. See Schemas Not Used by Oracle E-Business Suite
Release 12.2, page 3-22.
• fs_ne (non-editioned file system) - Used to store data that is kept in the file system
(such as data import and export files, reports, and output and log files).
ORACLE_HOME 9 GB 9.3 GB
APPL_TOP 51 GB N/A
INST_TOP 27 MB N/A
fs_ne N/A 1 GB
Advanced Configuration
Optional advanced configurations for Oracle E-Business Suite are deployed after you
upgrade to Release 12.2. However, consideration of these options is a critical
component of planning your upgrading to Oracle E-Buisness Suite 12.2.
Your requirements for advanced configurations of Oracle E-Business Suite may include
the following:
• Scale up or scale out to address sizing and, or high availability requirements.
Conditional Action: Review the following for the required steps to plan
and set up your final Oracle E-Business Suite 12.2 deployment
architecture:
• Configuring Oracle E-Business Suite Release 12.x Using Logical
Host Names (Doc ID: 1968231.1)
Preparing Customizations
Oracle E-Business Suite Release 12.2 introduces a new set of compliance, code, and
patching standards that customizations must adhere to. This section describes the new
standards and tools available for preparing your customizations for the Release 12.2
upgrade.
• Application tier
Apply the latest Oracle E-Business Suite Online Patching Readiness and GSCC Report Patch
Action: Before you proceed with the following steps, you must apply
the Oracle E-Business Suite Online Patching Readiness and GSCC
Report Patch (Consolidate Standalone Readiness Report Patch)
applicable for Release 12.2 and higher by referring to Using the Online
Patching Readiness Report in Oracle E-Business Suite Release 12.2 (Doc ID:
1531121.1).
Windows
C:\> <APPL_TOP>\envshell<CONTEXT_NAME>.cmd
Note: The subsequent steps assume that you are running in the
same session which was initialized with this environment file. If
you need additional operating system level sessions, ensure that
you initialize the environment with this same environment file.
• ADZDPAUT.sql - This report lists all the objects with violations to the EBR
rules that will be fixed automatically from the enablement process. This report
is provided for information purposes and no action should be taken from this
report.
• SYSTEM
• CTXSYS
2. Oracle recommends that you perform the chosen fix by customizing template file
$AD_TOP/sql/ADZDPCUST.sql
3. Repeat the Run the Online Patching Enablement - Readiness Report step above until all
violations have been addressed.
ORASSO_DS
ORASSO_PA
ORASSO_PS
ORASSO_PUBLIC
ORAOCA_PUBLIC
WIRELESS
OWBSYS_AUDIT
DSROWNER
MTHUSER
MapViewer MVDEMO
BPEL 10g If you are using BPEL 10g, then you must
migrate to SOA Suite 11g.
SES 10g If you are using SES 10g, then you must
upgrade to SES 11g.
In addition, Release 12.2 provides an ISG Diagnostics and Designer script allowing
services to be upgraded from Oracle E-Business Suite Release 12.1. to Release 12.2.
• Can be used when upgrading to Oracle E-Business Suite Release 12.2 from any
previous release.
The system administration and other pre-upgrade technical steps in this guide have
been tagged as Supported in EURC-DT: Yes if the check is part of the EURC-DT tool.
You can run EURC-DT as part of planning, test upgrades, and production upgrade.
For more information about EBS 12.2 Upgrade Readiness Checker - Database Tier, refer
to My Oracle Support Knowledge Document 2749775.1, EBS 12.2 Upgrade Readiness
Checker - Database Tier (EURC-DT).
Note: Shut down the database with the NORMAL option. You may not
be able to restore it from the backup if you use the IMMEDIATE or
ABORT option.
In addition to the database files, back up the APPL_TOP, product customizations, and
customized help files (in HTML).
Note: The upgrade process does not save customizations. You should
copy all your customized files and put them in a safe place so you can
reapply the customizations after the upgrade.
Conditional Action: If you are planning to enable TLS 1.2 only, then
you must upgrade to database 12.1.0.2. Refer to the following for
additional details: Enabling TLS in Oracle E-Business Suite Release
12.2 (Doc ID: 1367293.1), Section 6.1.
2. Ensure that the required database patches for Oracle E-Business Release 12.2
have been applied.
Supported in EURC-DT: Yes
Required Action: For guidelines, see Oracle E-Business Suite Release 12.2:
Upgrade Sizing and Best Practices (Doc ID: 1597531.1).
To prepare the Oracle E-Business Suite Release 12.2 file system, you must first prepare
the system for installation using Rapid Install. You will then run Rapid Install to lay
down the Oracle E-Business Suite Release 12.2 file system.
Conditional Action: This note applies only if you are upgrading from
Oracle E-Business Suite Release 12.0 or 12.1. If you are planning to use a
logical hostname for the application tier, then you must refer to Section
5.4: Upgrading to Oracle E-Business Suite Release 12.2 Using Physical
and Logical Host Names on the Application Tier, and perform the steps
in Section 5.4.1: Verifying Logical Host Name Configurations Prior to
Upgrade to Oracle E-Business Suite Release 12.2, My Oracle Support
Knowledge Document 1968231.1, Configuring Oracle E-Business Suite
Release 12.x Using Logical Host Name.
In addition to meeting the prerequisites described in this book and in the platform-
specific notes, you should also ensure you understand the licensing agreement for your
organization.
Tip: Ensure that the directory has sufficient space for the downloaded
Suggested Reading: Before you download the files, read the Release
Notes for the specific release you are installing.
To download the required components of the Oracle E-Business Suite Release 12.2
software distribution:
1. Sign in to the Oracle Software Delivery Cloud with your My Oracle Support
credentials.
3. In the search results, select the latest Oracle E-Business Suite package for Release
12.2, such as Oracle E-Business Suite 12.2.10.0.0.
4. Choose Continue.
6. Select the platform for each of the selected releases, and choose Continue.
8. By default, all available files are selected. Update the file list to select only the
required files. You must download the following specific components of the Oracle
E-Business Suite Release 12.2 software distribution:
• Oracle E-Business Suite Release 12.2.0 Rapid Install Start Here (all parts)
• Oracle E-Business Suite Release 12.2.0 for <Platform> Rapid Install (all disks and
parts)
• Oracle E-Business Suite Release 12.2.0 for <Platform> Rapid Install Technology
one-off Patches
• Oracle Web Tier 11.1.1.9.0 Utilities (11g Patch Set 7) - Oracle Fusion Middleware
for <Platform>
10. If you are performing an Oracle E-Business Suite upgrade from Release 11i or
Release 12 to Release 12.2 on Oracle Cloud Infrastructure, you can download
software to your Oracle Cloud Infrastructure Compute VM over an internet
connection. For further instructions on downloading software or patches onto
Oracle Cloud Infrastructure, see Section 6.4.6: Downloading Software and Patches,
Getting Started with Oracle E-Business Suite on Oracle Cloud Infrastructure, My Oracle
Support Document 2517025.1.
11. Verify that you have downloaded all the required files, and only those files, into
your stage directory. Each zip file is identified as "<Part Number>_NofM". For the
complete set of files for a given Part Number, you need all the zip files from 1 to M.
For example, Oracle Part Number "V100060-01 " has been divided into three parts,
so you must download the three zip files V100060-01_1of3.zip, V100060-01_2of3.zip,
and V100060-01_3of3.zip.
12. After you have downloaded the components listed above, unzip only the "Oracle E-
Business Suite Release 12.2.0 Rapid Install StartHere" files, and proceed to run the
buildStage script as described in the next section.
UNIX
$ cd /u01/StageR122/startCD/Disk1/rapidwiz/bin
$ buildStage.sh
Windows
C:\>F:
F:\>cd StageR122\startCD\Disk1\rapidwiz\bin
F:\>buildStage.cmd
------------------------------------------------------
4. Exit menu
Note: When using startCD 12.2.0.51, you must choose option 1 to create
a new stage area. This startCD version delivers a later patch set of the
Oracle Fusion Middleware Web Tier Utilities than the patch set
delivered by earlier startCD versions. Consequently, you must not use
any existing stage area created with an earlier startCD version. Instead,
create a new stage area to obtain the currently required Oracle Fusion
Middleware Web Tier Utilities patch set.
On platforms other than Windows, choosing this option will display a submenu that
shows the available platforms:
Rapid Install Platform Menu
------------------------------------------------------
2. Linux x86-64
4. HP-UX Itanium
5. Exit Menu
Specify the platform on which you want to install Oracle E-Business Suite.
Note: For a stage area on Oracle Cloud Infrastructure, the only platform
you can choose is option 2, Linux x86-64.
On Windows, the platform submenu does not appear; instead, the script proceeds
directly to this prompt.
Enter the full path to the directory. The stage area will then be built for you.
Main Menu - Option 2. Copy new patches to current stage area
This option updates the technology one-off patches for an existing stage area.
On platforms other than Windows, choosing option 2 will display the submenu that
shows the available platforms:
Rapid Install Platform Menu
------------------------------------------------------
2. Linux x86-64
4. HP-UX Itanium
5. Exit Menu
Specify the applicable platform, and the buildStage script will stage the technology one-
off patches packaged with the startCD into the stage/TechPatches directory.
Note: For a stage area on Oracle Cloud Infrastructure, the only platform
you can choose is option 2, Linux x86-64.
On Windows, the platform submenu does not appear; instead, the script proceeds
directly to staging the patches.
Main Menu - Option 3. Display existing files in stage TechPatches
This option displays (in a tree format) the files in your stage/TechPatches directory:
Windows:
patchRIStage.cmd
When prompted for the location of the Rapid Install stage, enter the path to the
stage area you created for StartCD 12.2.0.51.
Tip: Run the script as the same user that you used to run the
buildStage script when creating the stage area.
5. For Oracle Solaris on SPARC (64-bit) and IBM AIX on Power Systems (64-bit) only,
you must incorporate additional platform-specific fixes into the stage area. To do
so, after you run the patchRIStage.sh script to patch the stage area, you must re-run
the buildStage.sh script with option 2, Copy new patches to current stage
area.
6. Apply additional Rapid Install Patch 31033613. You must have created the Rapid
Install stage area with StartCD 51 (Patch 22066363) and applied the patch for the
• Patch the Rapid Install stage area using the following commands:
UNIX:
sh patchRIStage.sh
Windows:
patchRIStage.cmd
When prompted for the location of the Rapid Install stage, enter the path to the
stage area you created for StartCD 12.2.0.51 (Patch 22066363).
• Patch the Rapid Install stage area using the following commands:
UNIX:
sh patchRIStage.sh
Windows:
patchRIStage.cmd
When prompted for the location of the Rapid Install stage, enter the path to the
stage area you created for StartCD 12.2.0.51 (Patch 22066363).
8. If you are running Rapid Install on Oracle Grid version 19c or later, then apply
additional patch 30627877 (Conditional).
• Patch 30627877 requires the latest version of Standalone CVU (Patch 30839369)
to be downloaded into the Rapid Install stage area. To download Patch
30839369, perform the following steps:
1. Create the cvu_shiphome directory in the <Rapid Install Stage
directory>/TechInstallMedia directory using the following
command:
mkdir -p <Rapid Install Stage directory>
/TechInstallMedia/cvu_shiphome
3. Unzip the contents of Patch 30839369 for the appropriate platform into the
<Rapid Install Stage directory>
/TechInstallMedia/cvu_shiphome directory.
• Patch the Rapid Install stage area using the following command:
UNIX:
sh patchRIStage.sh
When prompted for the location of the Rapid Install stage (<Rapid Install
Stage directory>), enter the path to the stage area you created for StartCD
12.2.0.51 (Patch 22066363).
The startCD directory contains Rapid Install itself (in a subdirectory called Disk1), plus
supporting files and documentation.
The EBSInstallMedia directory contains the following subdirectories:
• AppDB (Oracle E-Business Suite database)
Follow the instructions in the section Before You Install, Oracle E-Business Suite
Installation Guide: Using Rapid Install. Then complete the following tasks.
1. Start the Rapid Install wizard
Start the wizard by entering the command rapidwiz at the command prompt. The
Welcome screen appears.
This screen lists the components that are included in, or supported by, this release
of Oracle E-Business Suite. Use the scroll bar to bring all the components into view.
For an upgrade, Rapid Install creates an Oracle 12cR1 Database Oracle Home
without a database. You can use this Oracle Home to upgrade or migrate your
existing database to Oracle 12cR1. If you already have a suitable 11gR2 or 12cR1
Oracle Home, you can use it instead of using the one created by Rapid Install
(which you may remove).
This screen is for information only. No action is required. Click Next to continue.
Choose the option Upgrade to E-Business Suite Release 12.2.0 option to upgrade your
Oracle E-Business Suite products to the current version of Oracle E-Business Suite.
The Rapid Install screen flow presents two paths: one that lays down the file system
and installs the new technology stack, and one that configures servers and starts
services. In subsequent steps, you will enter information in the Rapid Install Wizard
for upgrading a system.
If submission of your details fails because no connection can be made, you are
presented with a pop-up screen prompting for proxy server information:
The actions associated with an upgrade are performed in separate Rapid Install
sessions, as follows:
• Create Upgrade File System
Choose this option to run Rapid Install as a pre-upgrade step. In the screen flow
associated with this option, the wizard collects configuration parameters for
your system and stores them in the Oracle E-Business Suite database. When
you run Rapid Install, AutoConfig uses these values to lay down the file system
structure and technology stack components for your configuration. When it
runs, it also creates a context file (<CONTEXT_NAME>.xml) that contains all
the parameters that describe your system. This context file is created and
managed by AutoConfig.
In the Database SID field, enter the database name, or service name, that you want
Rapid Install to use to identify your existing database. The database name must be
alphanumeric, must not exceed eight characters in length, must not start with a
number, and must not include any spaces. Rapid Install records this name in the
Net Services configuration and in the init<SID>.ora file.
If you want to use an existing ORACLE_HOME for the upgrade, check the "Use
Existing Oracle Home" check box.
You must also enter a valid domain name on this screen. This value, when
combined with a host (machine) name, must produce a fully qualified domain
name (FQDN). For example, a hostname of apps1 and domain name of example.
com make up an FQDN of apps1.example.com
Important: The host name for the database tier node must be no
longer than 30 characters.
The Rapid Install wizard displays a warning message if the fully
qualified domain name (FQDN) exceeds 30 characters. If the host
name for the database tier node is no longer than 30 characters,
then you can ignore the warning and proceed with the installation.
Otherwise you must update the host name before you proceed.
You enter your Oracle RAC nodes as a comma-delimited list, in the form <node1>,
<node2>.
After completing all required details, click Next to continue.
As shown on the screenshot, the usernames and their respective default passwords
are: APPS Username (APPS), APPS password (APPS), GWYUID username
(APPLSYSPUB), GWYUID Password (PUB), Guest username (GUEST), and Guest
password (ORACLE).
Complete the text fields to change all the passwords on this screen to match those in
your existing system. The wizard stores this information in the configuration file.
The languages you select determine the available options for the other NLS-related
configuration parameters (such as base language, territory, and character set) that
your system requires.
Double-click a language in the Available Languages box to move it into the Selected
Languages box or highlight it and click the right arrow (>). Highlight a language in
the Selected Languages box and click the left arrow (<) to remove it. To select or
deselect all languages in a single action, use the double arrows, >> or <<.
You may need to perform additional tasks to finish the language installation. See
Oracle E-Business Suite NLS Release Notes for details. You can register additional
languages any time after the initial installation or upgrade. See Registering
Languages in Oracle E-Business Suite Setup Guide.
This screen displays Rapid Install defaults, as described in the following
paragraphs.
Selected Languages: If you have other active languages in your existing system,
you can change the default, and add languages to reflect the existing database
character set.
Default Territory: This field is set to AMERICA, and should remain so during the
upgrade. Your system administrator can change this value after the upgrade, if
necessary.
Database character set and APPL_TOP character set: Defaults to a common
character set that is compatible with the active languages indicated on the Select
Additional Languages screen. If they are not the character sets in your existing
system, select the correct ones from the drop-down list.
IANA character set: The Internet Assigned Numbers Authority character set is the
Internet-assigned standard used by the Web server. For more information, see http:
//www.iana.org/assignments/character-sets.
If necessary, change this value to indicate the one used in your existing system.
Click Next to continue.
Rapid Install uses the values specified on the Global Settings screen to identify a
qualified domain name and to derive port settings that your system will use to
connect services and listeners.
The results of each test are labeled using an icon. There are three types:
• Check mark
The test succeeded. Click the mark to obtain details of the test performed.
• An x mark
All issues marked x must be resolved before you continue with the installation.
Click the x to see the errors. If you can resolve an issue by fixing the values
provided on the settings screen(s), click Back until you reach the appropriate
screen, and re-enter the values. Some tests must be resolved in the operating
system. In that case, you may have to restart the Rapid Install wizard after the
problem has been fixed.
• Database Version
You should therefore verify the results of all these tests manually.
Rapid Install lists the actions it will take during the installation process. The content
of the list varies, depending on your installation choices.
Click Next to continue. Rapid Install displays another alert screen asking you to
verify that you are ready to begin the installation. Click Yes to continue.
Rapid Install creates new file systems for the application tier, and the 12cR1 Oracle
Home for the database.
If the test does not succeed, review the errors listed on the screen. Click the Back
Finish screen
VALID
-------------------------------
Y
If 'N' is returned, then query the error message for more info:
SQL> select fnd_message.get from dual;
Advanced Collections:
Perform this task only if you are using Oracle Advanced Collections with Strategies.
1. Strategy Workflow checks
Applies to Release 12.0 and 12.1.
Apply the diagnostic scripts patch 13027498:R12.IEX.A when upgrading from R12.
0.X and apply 13027498:R12.IEX.B when upgrading from 12.1.X. This patch contains
scripts for Collection Strategy Workflow.
From the Collections Agent responsibility using the user name 'SYSADMIN', stop
any scheduled Workflow Background Process concurrent program request for the
following Item Types:
Subledger Accounting:
Perform this task if you are using Oracle Subledger Accounting.
1. Clean up Advance Queues from prior Create Accounting processes before
enabling Edition-Based Redefinition (EBR).
Applies to Release 12.0 and 12.1.
Apply patch 13420532:R12.XLA.A when upgrading from Release 12.0.x and apply
Patch 13420532:R12.XLA.B when upgrading from Release 12.1.x to clean up
temporary advance queues that were created by prior Create Accounting program
processes. Pending Advance Queues of completed Create Accounting processes do
not create upgrade issues, but must be cleaned up for EBR.
Note: You can perform this pre-upgrade step while the pre-
upgrade system is online.
Action: When all database objects have been identified, change the
datatype to CLOB. Refer to LONG to CLOB Conversion Procedures, Oracle
E-Business Suite Developer's Guide.
Install Base:
Perform these tasks if you are using Oracle Install Base.
1. Check for Possible Corruption on User-defined Installed Base Transaction
Order Management:
Perform these tasks if you are using Oracle Order Management.
1. Check for the Nullable Hold Entity ID
Applies to: Release 12.1
If you are upgrading from release 12.1, then you should check for the Nullable Hold
Entity ID and fix it to NOT NULL. Carefully follow the instructions in the readme
of Patch 14191792:R12.ONT.B.
Product Hub:
Perform these tasks if you are using Oracle Product Hub.
1. Using the Packing Hierarchy Structure Type
Applies to: Release 12.0
If you are upgrading from 12.0 and have used Packaging Hierarchy structure type,
then note that only the preferred packaging structure from this structure type is
migrated over in the upgrade process. If you have defined multiple packaging
structures and want to migrate all of them, then consider bringing them into the
system by transferring them into other structure types, at which time they will be
treated as regular structure types and not Packs.
• EGO_MTL_SY_ITEMS_EXT_TL
You can discard the backups when the upgrade is completed and the pre-upgrade
UDA data for items have been functionally verified. This is required only if you are
upgrading from Release 12.0 to Release 12.2.
If the above query returns '0' as the output, then perform the following steps:
1. Take backup of ego_mtl_sy_items_ext_b table
2. Refer to Doc ID: 953449.1 and run the script provided in the 'Identification
Script' column within the 'Solution - Datafix' section to identify duplicate
records.
If there are duplicate records, then run the scripts provided in the 'Fix' column
within the 'Solution - Datafix' section for the appropriate base version to delete
duplicate records.
Set the schema name to ALL to gather statistics for all Oracle E-Business Suite
schemas (those with an entry in the FND_PRODUCT_INSTALLATIONS table). In
addition to gathering index and table-level statistics, the program gathers column-
level histogram statistics for all columns listed in the FND_HISTOGRAM_COLS
table.
Depending on the size and number of changes to your database, gathering schema
statistics may take a long time. Using the 'GATHER AUTO' option can reduce the
overall time, as it uses an incremental approach.
Customers who gather schema statistics at 10% for all schemas and then again at a
higher percentage for specific schemas or tables should initially continue this
approach to avoid performance degradation. Review this process during the
performance test phase.
5. Synchronize values of APPLPTMP with Database Directories for PL/SQL File I/O
based Concurrent Requests (required)
Supported in EURC-DT: Yes
Important: After laying down the File System using Rapid Install, do
not change the password for any products. Doing so may result in the
following error: 'ORA-01017: invalid username/password; logon denied
occurred while executing the SQL statement: CONNECT JTF/*****'
If the password for a product is changed, then FNDCPASS should be
run to revert the password to the default value. Adpatch can be
resumed after the password is restored to the original value.
Important: You must turn off the Database Vault before upgrading to
• $ export ORACLE_PDB_SID=<EBS_PDB_Name>
Back up the Oracle E-Business Suite database. If you encounter problems during the
upgrade process, then you can use this backup to restore your system to the same
state before you began the upgrade.
Maintenance Mode restricts logins and the type of operations that the system can
perform. Ensure that Maintenance Mode is enabled before you continue.
1. Source the applications run file system environment file as found in the fs1 file
system appl_top.
3. The Change Maintenance Mode menu displays the current Maintenance Mode
status at the top of the page. The status should be Disabled at this point.
Download and unzip the AD Upgrade Patch for 12.2 (patch 10117518). Follow the
instructions in the patch readme to use AutoPatch to run it from the 12.2 Run File
System.
Caution: Ensure that the environment file from the 12.2 RUN File
System is sourced prior to applying this patch.
14. Apply the consolidated upgrade patch and run the 12.2.0 Upgrade (required)
The Consolidated Upgrade Patch (CUP) for Release 12.2.0 combines critical
upgrade error corrections and upgrade performance improvements from Release
11i/12.0/12.1 into a consolidated suite-wide patch.
1. Prerequisite: Apply the AD Upgrade Patch for Release 12.2 by merging it with
the latest Consolidated Upgrade Patch (CUP) for AD.
• The AD Upgrade Patch for Release 12.2 readme contains information about
the latest Consolidated Upgrade Patch (CUP) for AD.
• You must follow the Patch readme and apply it by merging it with the
latest Consolidated Upgrade Patch for AD, along with any other patches
mentioned in the Readme, as instructed in the readme and by referring to
the Upgrade Guides.
2. Apply the Consolidated Upgrade Patch (CUP) for Release 12.2.0 in pre-
installation mode on the Run Edition File System.
Note: Before applying the patch for the latest CUP in pre-
installation mode:
If you have applied any other patch previously in pre-
installation mode and do not intend to merge it with 12.2.0
upgrade driver u10124646.drv, clean up the directory
<APPL_TOP>/admin/<TWO_TASK>/preinstall on run file
system after taking the backup of the current directory.
$ adpatch preinstall=y
• Apply the pre-upgrade patches that were released after the Consolidated
Upgrade Patch.
Refer to My Oracle Support Knowledge Document 1448102.2 for the Oracle
E-Business Suite Release 12.2 Pre-install Patches Report. It provides a list of
essential patches that you must apply in pre-install mode before upgrading
from Release 11i/12.0/12.1 to Release 12.2. Follow the recommendations
within My Oracle Support Knowledge Document 1448102.2 and apply the
additional pre-install patches.
Individual pre-install patches that are listed in the Oracle E-Business Suite
Release 12.2 Pre-install Patches Report can be merged with the
Consolidated Upgrade Patch and applied together.
Maintenance mode controls the system downtime period by managing user logins.
To disable maintenance mode, use the Change Maintenance Mode menu in AD
Administration.
2. The Change Maintenance Mode menu displays the current Maintenance Mode
Perform a full Oracle E-Business Suite backup of the application and database.
On the application tier (as the APPLMGR user), log on to the APPL_TOP
environment (source the environment file) and run this perl script to create
appsutil.zip in <INST_TOP>/admin/out. Source the applications run file system
environment file as found in the fs1 file system appl_top.
$ perl <AD_TOP>/bin/admkappsutil.pl
On the database tier (as the ORACLE user), copy or FTP the appsutil.zip file to
the <DB ORACLE_HOME> and unzip the file. Change directory to DB Oracle
Home as follows:
$ cd <DB ORACLE_HOME>
• export
LD_LIBRARY_PATH=$ORACLE_HOME/lib:$ORACLE_HOME/ctx/lib
• export
TNS_ADMIN=$ORACLE_HOME/network/admin/<CONTEXT_NAME>
UNIX:
• PATH=$ORACLE_HOME/bin:$ORACLE_HOME/perl/bin:/usr/bin:
/usr/sbin:$ORACLE_HOME/appsutil/jre/bin:/bin:/usr/bin/X11:
/usr/local/bin:$PATH
• PERL5LIB=$ORACLE_HOME/perl/lib/[perl
version]:$ORACLE_HOME/perl/lib/site_perl/[perl
version]:$ORACLE_HOME/appsutil/perl
Windows:
• PATH=%ORACLE_HOME%/perl/bin;%ORACLE_HOME%/bin;%PATH%
(for Windows)
• PERL5LIB=%ORACLE_HOME%\perl\lib;%ORACLE_HOME%
\perl\site\lib;%ORACLE_HOME%\appsutil\perl
UNIX:
$ cd <DB ORACLE_HOME>/appsutil/bin
$ perl adbldxml.pl
Windows:
C:\> cd <DB ORACLE_HOME>\appsutil\bin
C:\> perl adbldxml.pl
Windows:
C:\> <DB ORACLE_HOME>\appsutil\bin\adconfig.cmd
contextfile=<context file created in step 5>
11. Configuring the Oracle E-Business Suite Release 12.2 Application Tier
You will now run Rapid Install to configure the application tier services.
Complete the directory path to point Rapid Install to the File System 1
Applications context file, $INST_TOP>/appl/admin/<CONTEXT_NAME>.
xml. For example,
/u01/R122_EBS/fs1/inst/apps/<CONTEXT_NAME>/appl/admin/<CONTEXT
_NAME>.xml. You may either enter the path directly in the box, or click
Click Finish to exit Rapid Install. This phase of the upgrade is now
complete.
This release uses Invoker Rights for most PL/SQL packages. Executing these
packages from custom schemas may require additional grants from, and synonyms
to, APPS schema objects. Oracle recommends that you explicitly declare Invoker
Rights or Definer Rights for custom PL/SQL packages. See the PL/SQL User's Guide
and Reference for more information.
Custom database objects must follow the naming standards for custom object
names to avoid conflict with Oracle E-Business Suite.
4. Apply the latest Oracle E-Business Suite Online Patching Readiness and GSCC
Report Patch
You must apply the Oracle E-Business Suite Online Patching Readiness and GSCC
Report Patch (Consolidate Standalone Readiness Report Patch) applicable for
Release 12.2 and higher by referring to Using the Online Patching Readiness Report in
Oracle E-Business Suite Release 12.2 (Doc ID: 1531121.1), before you proceed with the
following steps.
Refer to Using the Online Patching Readiness Report in Oracle E-Business Suite Release
12.2 (Doc ID: 1531121.1) for instructions on how to download these utilities.
You must run the following utility from the application tier APPL_TOP. It reports
EBR violations that include objects not complying with the EBR rule about Non-
Editioned Objects (data storage objects such as Tables and Materialized Views), and
referencing editioned objects (code objects such as: Packages, Triggers, Object
Types, and so on). This report also lists several naming standard violations that
must be fixed prior to applying the online patching enablement patch.
1. Initialize the Run File System environment:
$ source <RUN APPL_TOP>/<Instance SID>_<hostname>.env
Note: The subsequent steps assume that you are running in the
same session which was initialized with this environment file.
If you need additional operating system level sessions,
remember to initialize the environment with this same
environment file.
2. Create the online patching log file location and set it as the current directory:
$ mkdir $LOG_HOME/appl/op
$ cd $LOG_HOME/appl/op
• ADZDPAUT.sql - This report lists all the objects with violations to the EBR
rules that will be fixed automatically from the enablement process. This
report is provided for information purposes and no action should be taken
from this report.
6. Fix Violations Listed in the Online Patching Readiness Report that Require
Manual Intervention
The Online Patching Readiness Report contains sections with different violation
types.
1. Review all sections listed from the ADZDPMAN.sql report. Follow instructions
in each section to fix violations.
• CTXSYS
2. Oracle recommends that you perform the chosen fix by customizing template
file $AD_TOP/sql/ADZDPCUST.sql. The reports provide more details on this
step.
3. Repeat the Run the Online Patching Enablement - Readiness Report step above until
all violations have been addressed.
2. Set the HOSTNAME environment variable before executing the online patching
tool adop.
• Check to ensure the environment variable HOSTNAME is set by running
the following:
$ echo $HOSTNAME
• If the HOSTNAME environment variable is not set, then run the following:
$ export HOSTNAME=<your-hostname-without-domain>
• If the hostname is set but has the domain, then reset it without the domain.
For example:
$ echo $HOSTNAME
$ apcappsx2.au.oracle.com
$ export HOSTNAME=apcappsx2
3. Run the following report to retrieve the current tablespace free space:
$ perl $AD_TOP/bin/adzdreport.pl apps
• Add necessary space to the tablespaces if they do not contain the required free
space. Refer to Altering and Maintaining Tablespaces in Oracle Database
Administrator's Guide for details.
2. Run the report using the following command. Ensure that you verify any
invalid objects at this stage. Take special note to ensure that all online patching
objects (objects that match the pattern 'AD_ZD%') are valid:
$ sqlplus <apps username> @$AD_TOP/sql/ADZDEXRPT.sql
9. Ensure that all Application Tier Oracle E-Business Suite services are shut down
Verify that all application tier Oracle E-Business Suite services are shut down prior
to applying the Online Patching Enablement patch.
This report lists a count of the DDL statements that are required to EBR enable your
environment. The report is organized by outcome of execution: 'Successfully
Executed', 'Not Executed', and 'Failed Execution'. At the end of the patch
application the report should have a zero count in the sections: 'Not Executed' and
'Failed Execution'. If the report contains 'Not Executed' and 'Failed Execution' items,
then report these failures to Oracle Support. You will be asked to provide the
output from the report, the patch log and all worker logs, and the online patching
enablement status report output. If there is any worker failure during the Online
Enablement patch, you should not ignore or skip the failed error. The issue should
be addressed before restarting the worker. Ignoring or skipping the error can cause
database corruption.
12. Re-run the Online Patching Enablement Status Report after the Online Patching
2. Run the Status Report immediately after the enablement patch completes:
$ sqlplus <Apps Username> @$AD_TOP/sql/ADZDEXRPT.sql
The purpose of running this report at this stage is to identify and fix any errors that
occurred during the enablement process.
13. Re-run the Online Patching Enablement Readiness Report after the Online
Patching Enablement patch has been applied
1. Set the current directory to $LOG_HOME/appl/op:
$ cd $LOG_HOME/appl/op
$ mv adzdpsum.txt adzdpsum_post_dbprep.txt
$ sqlplus system @$AD_TOP/sql/ADZDPMAN.sql
$ mv adzdpman.txt adzdpman_post_dbprep.txt
$ sqlplus system @$AD_TOP/sql/ADZDPAUT.sql
$ mv adzdpaut.txt adzdpaut_post_dbprep.txt
The purpose of running this report at this stage is to ensure that all EBR
violations that could have appeared before enabling the online patching feature
are fixed.
14. Run the Online Patching Database Compliance Checker report to check for
coding standards violations
There are two levels of compliance that can be targeted:
• Minimal Compliance (Minimal) - These checks represent the minimum
requirement for correct operation of Oracle E-Business Suite Release 12.2.
• Full Compliance (Full) - These checks indicate whether an object can be patched
using Online Patching. Objects which do not meet full compliance may have
limitations in how they can be patched, or may need to be patched using
downtime patching. Full compliance also requires that all minimal compliance
checks are passed. Custom code that will only be patched using downtime
patching does not need to meet the full compliance level.
2. Run the Online Patching Database Compliance Checker report to check for
online patching database objects standards violations:
sqlplus <Apps Username> @$AD_TOP/sql/ADZDDBCC.sql
This utility reports all violations to the Online Patching Development Standards. All
Oracle E-Business Suite violations are fixed by the 12.2 upgrade. You must fix any
object listed in this report that is part of your custom code. If you do not fix the
violation, then you cannot leverage the online patching infrastructure to patch the
objects listed in this report.
The 'recyclebin' parameter must be turned off to allow the cleanup phase of the online
patching cycle to be performed without having to connect as SYS. This feature may still
be used at other times.
For example:
$ recyclebin=off
If the _SYSTEM_TRIG_ENABLED parameter is set to false, then system triggers are not
processed. The post Online Patching Enablement parameter must be set to true.
_SYSTEM_TRIG_ENABLED=true
$ _SYSTEM_TRIG_ENABLED=true
Note: Do not run adsplice when you are at the Oracle E-Business
Suite Release 12.2.0 level. Before running adsplice, you must
upgrade to R12.AD.C.Delta.5 and R12.TXK.C.Delta.5 Release
update packs or higher for AD and TXK.
This step is applicable only if you have custom products. If you have add-on
localization products installed (CLE, CLA, CLL, CLJ), then you must re-splice those
add-on localization products.
1. Running adsplice
For the custom products that already exist, you must run adsplice on the Run
File system to lay down the file system.
Action: You must apply the latest Oracle E-Business Suite Release
Update Pack. Follow the instructions in Oracle E-Business Suite RUP,
AD and TXK RUP Information, Release 12.2 (Doc ID: 1583092.1).
Tip: When applying the RUP, follow the steps in the associated readme
of the Oracle E-Business Suite Release Update Packfor preparation,
applying prerequisite patches, and applying the RUP. When you have
completed those steps in the Readme document, return to this guide
and continue with the following steps. Do not perform the Post-Uprade
steps for the RUP until instructed to do so in the Post-Uprade Steps of
Oracle E-Business Suite Release Update Pack for Release 12.2, page 5-26.
Note: This step should be executed only after completing the Verify
completion of concurrent programs post-upgrade task.
2. Oracle highly recommends that you enable TLS. You will enable TLS after you
upgrade to Oracle E-Business Suite 12.2. You must apply the prerequisite patch
requirements to enable TLS.
8.
9. Apply online help for Oracle E-Business Suite Release Update Pack
(recommended)
10. Apply mandatory interoperability patches (required for Oracle Database 19c)
If you have languages other than American English registered in your system, then
follow instructions in the following step.
If you have not already granted flexfield value set access in a previous version of
Release 12.2, then you must perform this step.
Note: Follow the required steps in the Flexfield Value Set Security
chapter in the Oracle E-Business Suite Flexfields Guide, Release 12.2.
13. Installing NLS upgrade patch driver and NLS Online Help (conditional)
For additional NLS languages active in the system, once the American English
upgrade and recommended Release Update Pack level have been applied, you can
then upgrade your NLS software for existing languages by performing either one of
the following steps:
1. Using the Translation Synchronization Patch followed by applying the NLS
Online Help patch if available.
During the upgrade, custom triggers or constraints may have been modified. If you
disabled these triggers and constraints, then identify any data updates that must be
made before you re-enable them.
If you dropped any custom indexes, then review the new data model to determine
if the index is necessary before you redefine it.
15. Manually add custom redirects and resources to configuration files (conditional)
The Allowed Redirects and Allowed Resources features are enabled by default after
your upgrade. Consequently, if you use custom redirects and resources, such as
JSPs and servlets, in your environment, then you must manually add these to your
configuration files for allowed redirects and allowed resources, respectively.
Verify that all custom responsibilities use the correct menu. From the System
Administrator responsibility, navigate to Security > Responsibilities. Query each
custom responsibility and update as necessary.
Before you copy custom code in the CUSTOM library to the new directory
structure, refer to the backup you previously created and verify that the
customizations are valid for the new version of Oracle E-Business Suite.
For valid customizations, place a copy of the new CUSTOM library (CUSTOM.pll)
in a safe place. It is located in the $AU_TOP/resource directory (UNIX), or the %
AU_TOP%\resource directory (Windows). Then, make a copy of the old Oracle
Forms CUSTOM library and place it in the new directory. Upgrade to Oracle Forms
Developer 10g by regenerating the library. Or, you can cut and paste the existing
custom code into the new library, and then regenerate it.
Note: See Using the CUSTOM Library in the Oracle E-Business Suite
Developer's Guide.
Copy custom shell scripts or reports to the custom application directories and re-
customize the copy as necessary.
22. Re-configure physical and logical host names on the application tier post
upgrade (conditional)
If the Oracle E-Business Suite system has been upgraded to Oracle E-Business Suite
Release 12.2 using the logical hostname for the application tier, then you must refer
to Configuring Oracle E-Business Suite Release 12.x Using Logical Host Names, (Doc ID:
1968231.1). Refer to section 5.4: Upgrading to Oracle E-Business Suite Release 12.2
Using Physical and Logical Host Names on the Application Tier, and section 5.4.2:
Reconfiguring Physical and Logical Host Names on the Application Tier Post Upgrade, and
complete the required steps.
Note: After the upgrade, the deployed WSDL URL information has
already been changed. Therefore, you may have to replace it with the
new WSDL URL and service location or address accordingly in Web
service clients while invoking the deployed Oracle E-Business Suite
service. To ensure the backward compatibility, the previous 12.1.X
service endpoint (services deployed in Oracle E-Business Suite) will
continue to work at run time after the upgrade. New service endpoint
from Oracle SOA Suite server will be shown in the interface detail page
and should be used for client programs.
Note: After the upgrade, the deployed WSDL URL for a generic XML
Gateway service will be changed. You may have to replace it with the
new WSDL URL and service location or address accordingly in Web
service clients while invoking the generic XML Gateway service. For
more information about XML Gateway Web services, see the Oracle
XML Gateway User's Guide.
Oracle Purchasing:
Conditional Action: Oracle Purchasing (available as part of Oracle
Procurement) is integrated with Oracle Transportation Management. If
you have licensed both Oracle Transportation Management and Oracle
Purchasing and will use Oracle Transportation Management with
Oracle Purchasing, then perform the post-update steps outlined in
About Oracle Transportation Management Integration with Oracle E-
Business Suite R12.2+ (Doc ID: 1362803.1).
Advanced Collections:
This task applies for customers using Advanced Collections with Strategies.
Human Resources:
1. Apply latest HRMS Legislative Updates (required)
Note: If you are using only Oracle HR Shared for use with another
Oracle E-Business Suite product, then DO NOT apply this
legislative data.
Payroll:
These tasks apply only to Oracle Payroll.
1. Install or Update Vertex for Payroll (required)
Action: Oracle Payroll uses the Vertex Quantum Payroll Tax Series
Projects Tasks
Conditional Action: Compile all Fast Formulas via FFXBCP (Refer Doc
ID: 167689.1). This step applies to all customers who are upgrading to
Release 12.2 and want to use the HR Rate by Criteria for labor rates, to
be used in forecast or labor cost distribution in the Projects application.
Applying Patches:
Download and apply patch 24610809:R12.PJT.C from My Oracle Support.
3. Select Security.
5. Review the certificate details on the General tab. Verify that the imported SSL
certificate is valid.
7. Click Export…
9. Save the certificate using the host name of the web service provider. For example, if
the host name is *.example.com, then save the certificate as: *.example.com.cer.
3. Use the put command to enter the certificate into the instance. For example, put *.
example.com.cer.
Note: The password is stored in the fnd vault and remains secured
from the end user when creating subscriptions. Users provide the
module and the key and must remember it for later use.
• Key: PA_MGMT_SERVICES_USA
• Value: Welcome1
• Subscription parameters:
• The service constructs the SOAP header and username token based on the
information provided.
• Payload information passed by the program at run time is appended to the header
prepared above as the soap body.
• oracle.apps.pa.coexist.projectplan.invoke
• oracle.apps.pa.coexist.update.task.invoke
• oracle.apps.pa.coexist.fileupload.invoke
5. Click GO.
6. Find your search result under the Results: Events section. Click Subscriptions.
8. In the Create Event Subscription page, enter the following subscription details:
1. System: <EBS Instance>
5. Status: Enabled
9. Click Next.
10. In the Select a WSDL Source section, enter the WSDL URL.
• The WSDL URL is the URL of the Oracle Fusion Cloud instance you are using
to register this event.
11. Click Next to select the service. The Service Name field is populated with
ProjectServiceV2 in the Select Service section.
13. Click Next and select the operation. In this example it is findProjectPlan.
Note: All services used for integration with Oracle E-Business Suite
are synchronous services.
14. Click Next to complete the subscription registry and link it with the predefined
business event.
15. In the Create Event Subscription – Invoke Web Service section. The application
provides the Subscription Parameters and User ID with access to the service and the
parameters to retrieve the password from the vault. For customizations in Service
Invocation, users can extend the default java class oracle.apps.fnd.wf.bes.
WebServiceInvokerSubscription and provide the extended class in place of Java
Rule Function.
16. Add the other three business events using the above steps 4 through 15. The
corresponding operations and service names for each business event include:
• EGO_MTL_SY_ITEMS_EXT_TL
Secure Configuration
This section applies to all users, regardless of which products are registered as active.
1. Review and Deploy Security Guidelines (Recommended for all Oracle E-
Business Suite releases)
• Follow the Secure Configuration Guidelines
2. Perform the following if you have upgraded to Release Update 12.2.6 or higher:
System Maintenance:
1. Delete obsolete product files (recommended)
Delete the product files for the previous release (if you have not done so already).
You may want to retain report output files or customized programs. Output files
are stored in the old log and output subdirectories under each product's top
directory, under the log and output directories you created, or under a common
directory.
To remove obsolete files for an old release, change to the top directory of that
release and enter the following command:
UNIX:
$ rm -rf <old APPL_TOP>
Here is an example:
$ rm -rf /d01/appl/r10
Windows:
C:\> rd /s /q <old APPL_TOP>
Here is an example:
C:\> rd /s /q \APPL110
By default, the Java Color Scheme profile option should be set to 'Standard' for all
sessions and optimal system response time. The upgrade process sets this default
value for all instances.
3. Update Java Color Scheme profile option for selected users (conditional)
By default, the Java Color Scheme profile option should be set to "standard" for all
sessions for optimal system response time. The upgrade process sets this default
value for all instances. However, setting this profile option to a different value may
work better for some systems. See Oracle E-Business Suite Setup Guide and Oracle E-
Business Suite User's Guide for more information.
To set the parameters, go to the Oracle Applications Manager Site Map and choose
AutoConfig > Applications Node > Edit Parameters. Then, use the Search field to
find OXTA. After you set the parameters, run AutoConfig to regenerate the wls.
properties file (INST_TOP/appl/admin/oafm_wls.properties).
Note: See Oracle XML Gateway User's Guide for more information.
Also, ensure that the following profile options are set at site level for Oracle XML
Gateway. If you have previously set these profile options, then no action is
necessary, as the upgrade preserves these values.
ECX: System Administrator Email Address Address to which Oracle XML Gateway
error notifications should be sent.
ECX: Server Time Zone Time zone the database server is running in.
Note: See Oracle XML Gateway User's Guide for more information.
For additional mandatory post-upgrade steps for Oracle Cloud Infrastructure (OCI),
refer to Getting Started with Oracle E-Business Suite on Oracle Cloud Infrastructure (Doc ID:
2517025.1). Refer to section 4.5 Upgrading to Oracle E-Business Suite Release 12.2 and
section 4.5.5.1 Performing Post-Upgrade Tasks.
Additional Tasks
This section points to additional tasks that may be necessary, and suggests
documentation that describes those tasks.
• Navigate to Reports > Run > Pick Single Request > Generate All Business Views.
If you don't have the Business Views Setup responsibility assigned to the SYSADMIN
user, then complete the following:
• Logon to Oracle E-Business Suite as SYSADMIN.
• Navigate to Security > User > Define and add responsibility Business Views Setup to
the SYSADMIN user.
When deploying multiple application tier nodes for an Oracle E-Business Suite
environment, you can use a Shared Application Tier Filesystem or replicate the
filesystem on every node in the environment.
Tip: Oracle highly recommends that you use a Shared Application Tier
Filesystem.
When directed in Using Load-Balancers with Oracle E-Business Suite Release 12.2 (Doc ID:
1375686.1), follow the steps in one of the following notes to create a new application tier
node:
• To create the Shared Application Tier file system and add new application tier
nodes, follow the steps in Sharing The Application Tier File System in Oracle E-Business
Suite Release 12.2 (Doc ID: 1375769.1).
• If you are using a distributed filesystem, then follow the steps in Cloning Oracle E-
Business Suite Release 12.2 with Rapid Clone (Doc ID: 1375769.1) to add new
application tier nodes.
Note: See the Oracle E-Business Suite Setup Guide. See also the Oracle E-
Business Suite User's Guide.
Overview
The downtime portion of the upgrade includes the automatic submission of several
concurrent programs. For a list of sample concurrent programs, refer to the Sample
Concurrent Programs, page A-4 section in this appendix.
In many cases, concurrent programs run in multiple threads, therefore, the total number
of concurrent requests that make up portions of the post-upgrade step can be high.
These upgrade programs are run by the concurrent manager once the system is up, and
processing will be mixed with ongoing concurrent jobs in the system.
You can define a separate concurrent manager queue to process only the post-upgrade
concurrent programs, therefore improving manageability of this situation. You can use
inclusion and exclusion rules to prevent other manager queues (such as the standard
manager) from picking up requests, and force this new manager queue to process
specific upgrade requests. This method lets you control the number of target processes
allocated to these post-upgrade concurrent programs, including dynamic processes
with the use of work shifts. For additional details on configuring new manager queues,
target processes, inclusion and exclusion rules, and work shifts, refer to the Oracle E-
Business Suite Setup Guide.
If you plan to isolate post-upgrade concurrent programs to a separate manager queue,
then you must create a new concurrent manager for these upgrade concurrent
programs before you shut down all services as part of the Perform the Upgrade, page 4-
47 tasks described in this guide. This procedure is needed to prevent existing Request
Processing Managers from picking up and executing requests when services are started
3. Include programs from the above list into this new program type.
4. Navigate to:
System Administrator > Concurrent: Program > Define
5. Search for the program 'Refresh Materialized Views' and enter or select: R12PUPT
3. Select or enter the following attributes to create the new concurrent manager:
Manager: R12_Post_Upgrade
Short Name: R12PU
Application: Application Object Library
Description: New manager queue for R12 post upgrade requests
Type: Concurrent Manager
Cache Size: 1
Program Library Name: FNDLIBR
Specialization Rules:
Include/Exclude: Include
Type: Request Type
Application: System Administration
Name: R12PUPT
Work Shifts:
Work Shift: Standard
Processes: Enter a Value, for example '4'
Sleep Second: 30
context file
A in an upgrade, 4-22
locating in an upgrade, 4-62
Additional Post Upgrade Tasks, 5-27
Copying and Re-customizing Modified Scripts or
Additional Tasks
Reports, 5-7
reapply customizations, 5-27
Copying Existing Custom Start Scripts, 5-7
Advanced Collections
CPU
financials upgrade impact, 2-11
requirements, 3-6
Advanced Configuration, 3-18
Customer Relationship Management Tasks, 4-39,
APPL_TOP
5-10
character set (upgrade), 4-28
Customizations, 2-6
Application DBA (AD) Tasks, 4-5
Customizing Help Files, 3-22
application tier
technology stack, 3-1
Applying AD 12.2 Upgrade Driver, 4-53 D
Apply latest AD and TXK for Release 12.2, 4-74 database
Apply Recommended Security Patches, 5-4 character set (upgrade), 4-28
Apply the Latest Oracle E-Business Suite Release Database
Update Pack for Release 12.2, 4-76 memory requirements, 3-8
AutoConfig Database and System Administration Tasks, 4-43,
in an upgrade, 4-21 5-1
Database Initialization Parameters, 4-73
B Database Node Configuration screen
using in an upgrade, 4-23
Backing Up Oracle E-Business Suite, 4-56, 5-21
database tier
Backing Up the Database, 4-52
technology stack, 3-1
Base directory
Data Model Changes, 3-22
definition, 4-30
default territory
choosing in an upgrade, 4-28
C
Disable AOL Audit Trail, 4-49
certification information Disabling Custom Triggers, Constraints, and
where to find, 3-2 Indexes, 4-50
character sets Disabling Maintenance Mode, 4-55
compatible, 4-28
Index-1
Dropping Dangling Synonyms, 5-3 using, 4-31
Global System Settings screen
E using, 4-22
Granting Flexfield Value Set Access, 5-5
Edition-Based Redefinition, 2-5
Enable PDF printing, 5-25
Enabling Online Patching, 4-65 H
Downloading and applying the Online HRMS Upgrade Impact
Patching Enablement patch, 4-71 about business impact and functional changes,
fixing violations listed in the Online Patching 2-13
Enablement - Readiness Report, 3-21, 4-68 HRMS, 2-13
running the Online Patching Database iRecruitment, 2-14
Compliance Checker report, 4-72 Payroll, 2-13
running the Online Patching Enablement - Performance Management, 2-14
Readiness Report, 3-20, 4-66 Succession Planning, 2-14
running the Online Patching Enablement - Human Resource Management Upgrade Impact,
Status Report, 4-70 2-13
shutting down middle-tier services, 4-70 Human Resources Tasks, 5-11
Verifying database and application tier
patches, 4-66 I
verifying database tablespace free space, 4-69
IANA
verifying the database version, 4-65
character set (upgrade), 4-28
Ensuring Maintenance Mode is Enabled, 4-53
Implementing Code Remediation, 3-21
eTRMs
Instance directory, 4-30
importance of, 2-18
Internationalization Settings screen
using in an upgrade, 4-27
F
file system J
creating for upgrade, 4-21
JVM Parameter Settings
Financials and Procurement Products
For 64-bit Java, 3-14
financials upgrade impact, 2-11
Financials and Procurement Tasks, 4-39, 5-9
L
Financials Upgrade Impact, 2-10
Finishing the 12.2.0 Upgrade, 4-56 Languages
Finish the Upgrade character sets, 2-18
configure applications client software, 5-8 language status, 2-17
configure the instance, 4-56 Lease and Finance Management
integrate custom objects, 4-65 financials upgrade impact, 2-12
re-enable custom triggers, 5-6 log files
Fusion Project Management disk space, 3-9
projects coexistence, 5-12 purging, 3-9
G M
General Information and Required Tasks Managing Concurrent Processes, A-1
upgrade overview, 2-18 Mandatory Steps
Global Settings screen all customers, 5-26
Manually Adding Custom Redirects and JSPs to
Index-2
Configuration Files, 5-6
Manual Steps P
in an upgrade, 1-2
passwords
Memory requirement for Oracle E-Business
changing upgrade defaults, 4-26
Suite, 3-6
for system upgrade, 4-26
Migrate Portlets Preferences Store, 5-27
patches
Migrating the CUSTOM Library, 5-7
disk space, 3-10
mount points
Performing the Upgrade, 4-1
application tier, 4-28
Performing the Upgrade to Release 12.2.0, 4-47
Perform the Upgrade
N disable AOL audit trail, 4-49
NLS Upgrade Considerations, 2-17 shutting down application tier listeners and
node-specific parameters screen concurrent managers, 4-49
in an upgrade, 4-28 Planning Deployment Architecture, 3-1
Post-install Checks screen
O using in an upgrade, 4-36
Post Upgrade Tasks
Obsolete Products in Release 12.2, 2-8
backing up Oracle E-Business Suite, 5-31
Obsolete Technology Integrations, 3-24
Customer Relationship Management tasks, 5-
OCM
10
See Oracle Configuration Manager
Financials and Procurement tasks, 5-9
Online Patching
Human Resources Tasks, 5-11
enabling online patching, 4-65
implementing new product and country-
Oracle Configuration Manager, 4-19
specific functionality, 5-29
Oracle E-Business Suite Architecture
logging On to Oracle E-Business Suite, 5-31
the application tier, 2-2
migrate portlets preferences store, 5-27
Oracle E-Business Suite Architecture: The
Oracle E-Business Suite Integrated SOA
Application Tier
Gateway, 5-8
installed components, 2-2
Oracle Environmental Accounting and
Oracle E-Business Suite Integrated SOA
Reporting, 5-10
Gateway, 3-25, 5-8
Oracle Purchasing, 5-9
Oracle Software Delivery Cloud
Oracle Shipping Execution, 5-20
downloading Oracle E-Business Suite from, 4-
Oracle Value Chain Planning, 5-20
8
Oracle Warehouse Management, 5-21
Oracle XML Gateway, 3-25, 5-9
Oracle XML Gateway, 5-9
Oracle XML Gateway Setup, 5-24
Product Hub, 5-17
Oracle XML Publisher Tasks, 5-25
Projects tasks, 5-12
other files
resizing the database, 5-29
disk space, 3-10
Supply Chain Management tasks, 5-17
output files
system maintenance tasks, 5-23
disk space, 3-9
understanding Oracle E-Business Suite System
purging, 3-9
Administration tasks, 5-29
Overview
Post-Upgrade Tasks, 5-1
general information and required tasks, 2-18
Pre-install Checks screen
Overview of the Upgrade
using in an upgrade, 4-32
supported upgrade paths, 1-1
Preparing Customizations, 3-19
Index-3
Preparing External Integrations, 3-24 customizations, 3-20
Preparing for an Upgrade
migrate or upgrade your database to Oracle S
11g Release 2 (11.2.0.4) or 12.1.0.2, 4-2
Sample Concurrent Programs, A-4
Preparing for the Upgrade
Scheduling Time for an Upgrade, 1-6
application DBA (AD) tasks, 4-5
Schemas Not Used by Oracle E-Business Suite
customer relationship management tasks, 4-39
Release 12.2, 3-22
financials and procurement tasks, 4-39
Secure Configuration, 5-21
gather schema statistics, 4-44
Select Upgrade Action screen
Human Resource Management (HRMS), 4-40
using, 4-21
install JRE on the database tier, 4-46
Select Wizard Operation screen
perform a system backup, 4-47
using, 4-18
supply chain management tasks, 4-41
using in an upgrade, 4-61
Preparing the Database for the Upgrade, 4-1
Shutting Down Application Tier Listeners and
Preparing the Oracle E-Business Suite Release
Concurrent managers, 4-49
12.2 File System, 4-5
software requirements
Preparing the System for Upgrade, 4-37
operating system, 3-3
Preparing Third-Party Integrations, 3-26
stage area, 4-7
Product Hub
directory structure, 4-15
advanced search, 2-16
Supply Chain Management Tasks, 4-41, 5-17
integration with Web ADI, 2-16
Supply Chain Management Upgrade Impact, 2-
item organization assignments, 2-16
14
structures, 2-15
Supply Chain Upgrade Impact
Product Patches
Oracle Product Hub, 2-15
applying latest, 5-5
Supported Upgrade Paths, 1-1
interoperability, 5-5
System Maintenance Post Upgrade Tasks, 5-23
progress bars
description of, 4-35
T
Projects Tasks, 5-12
Technical Impact and Changes, 2-1
R technology stack
required components, 3-1
Rapid Install
reviewing components, 4-18
role in upgrade, 1-2
Technology Stack Components, 2-3
Readiness Checker - Database Tier, 3-26
temporary directories
Reapplying Customizations, 5-27
disk space, 3-9
Reference Information
Temporary Directory for XML Publisher, 5-26
finding, 2-18
temporary files
Regenerating Business Views, 5-28
disk space, 3-9
Release 12.2 Architecture, 2-1
temporary space
Release Content Documents
required for installation, 3-9
importance of, 2-18
Testing the Upgrade, 1-6
Resetting init.ora Parameters, 4-43
TOIs
Review Application User Information screen
importance of, 2-18
using, 4-26
top-level directory
Reviewing User Responsibility Assignments, 5-8
RDBMS, 4-28
Running Online Patching Readiness Reports
Transport Agent Setup, 5-24
Index-4
U
Understand Business Impact and Functional
Changes, 2-7
Understanding Technical Impact and Changes, 2-
7
Understanding the Upgrade Flow and Process, 1-
2
Updating and Verifying Custom Responsibilities,
5-7
Updating init.ora with Upgrade Parameters, 4-49
Upgrade
business impact, 2-7
obsolete products, 2-8
Upgrade By Request, 2-7
upgraded installation
description of, 4-19
upgrade operations
choosing, 4-18
Upgrade Patch
installing NLS upgrade patch driver, 5-6
Upgrade Requirements
overview of upgrade requirements, 1-1
upgrades
configuring servers, 4-22
configuring services, 4-61
Database Oracle Home in, 4-18
Upgrading to the Latest Code Level, 4-74
V
Verifying Completion of Concurrent Programs,
5-1
W
Web Services, 2-2
Welcome screen
using, 4-17
Index-5