We continue to release updates to EBS 12.2 technology stack (TXK) and
Applications Database (AD) components. We released the first set of updates
in March 2014, the second set in May 2014
, the third set in July 2014
, the fourth set in October 2014
, the fifth set in November 2014
, and have now made available a sixth set of critical updates.
If you are on Oracle E-Business Suite Release 12.2, we strongly
recommend that you apply these two newly-released patch collections at your earliest
You must always keep your AD and TXK codelevels synchronized. See the following Note for an additional FND patch needed, as well as complete installation instructions:
What's new in these updates?
- Online Patching support for single file system on development or test systems
- Integration of EBS Technology Consistency Checker (ETCC) with ADOP
- Simplification and enhancement of adop console messages
- Performance improvements in adop operations
- Improved error reporting by Online Patching Log Analyzer utility
- Change to default password for spliced products
- Ability to deregister a custom application
- Elimination of certain context variables
- Support for Managed Server Independence Mode
- Enhancements to Delete Application Tier Node
- Minimize failures by pre-checking the availability of required ports during cutover phase
- Removed dynamic generation of portlet.xml file used by Oracle E-Business Suite portlet producer
- Provision to change passwords during rapid clone
- Provision for txkSetAppsConf.pl to accept new arguments
What's changed in these updates?
- Enhanced Rapid Clone
- Improvements in handling when running ADOP on multiple nodes
- Improvements to single sign-on functionality
- Improvements to JVM and Admin server heap size
- Improved ADOP flow
- Improvements in ADOP flow communications handling
- Improvements on Integrated SOA Gateway scripts
- Support for unlimited number of application tier nodes
What Is a Codelevel?
Oracle E-Business Suite Release 12 patches are grouped into codelines.
A codeline begins with a point release (for example, Release 12.0) and
progresses to include all the patches created to maintain that point
Patches associated with codelines implement a set of
features for a point release, and also provide fixes for that set of
features. Such a unique set of product features for a point release is
referred to as a a codelevel. You can think of it as the code you
get when you apply a set of patches: in other words, it is defined by
the patches that deliver it. Codelevels are cumulative, with each
containing the initial set of features plus all the fixes created for
Benefits of the Latest Codelevel
There are several important reasons you should adopt this latest recommended AD/TXK codelevel:
- It includes a number of significant fixes and improvements.
- New patches to implement code fixes will only be appliable to the latest AD/TXK codelevel.
- No code fixes will be created for earlier AD/TXK codelevels.
How Can I Get To the Latest Codelevel?
Installation instructions are here:
Further information about these updates can be found here: