Steven Chan

Subscribe to Steven Chan feed
The latest news directly from E-Business Suite Development
Updated: 2 hours 39 min ago

Which Oracle Database Patchsets Can Be Used With EBS?

Tue, 2016-11-01 02:05

Oracle versions numbers can be very long.  Complicating matters further, different product families within Oracle use the version hierarchy differently.  This can make it confusing to determine whether a specific product update has been certified with Oracle E-Business Suite.

Oracle Database update numbers can be daunting.  However, it might be reassuring to learn that the fifth-level digit in Oracle Database version is not relevant to E-Business Suite certifications.  In other words, you can apply any database patchsets that have been certified at the fourth-level digit. 

For example, we have certified EBS 12.2 with Database 12.1.0.2. All of the following Oracle Database patchsets will work with EBS 12.2:

  • Oracle Database 12.1.0.2.0 (documented certification)
  • Oracle Database 12.1.0.2.160419 (April 2016 Database Proactive Bundle Patch)
  • Oracle Database 12.1.0.2.160719 (July 2016 Database Proactive Bundle Patch)

This is sometimes shown in our documentation in either of the following ways:

  • Oracle Database 12.1.0.2
  • Oracle Database 12.1.0.2.x

The absence of a fifth-digit or the presence of an 'X' in the fifth digit's place means any fifth-digit level updates may be applied to an Oracle Database for EBS 12.2 without requiring a new certification.  This applies to all environments, including test and production environments.

Related Articles

Categories: APPS Blogs

Upgrading to EBS 12.2 With a Non-APPS Schema

Mon, 2016-10-31 02:06

An Oracle database stores the objects associated with a single installation of Oracle E-Business Suite. Product code objects are stored in the APPS schema; product data objects are stored in the relevant base product schemas. Product code objects include packages, procedures, functions, triggers, views, materialized views, java classes, and queues.

EBS APPS schema

What does the APPS schema do?

The APPS schema has access to the complete Oracle E-Business Suite data model. Oracle E-Business Suite responsibilities connect to an APPS schema, and the environment variable FNDNAM is set to the name of the APPS schema. The APPS schema owns all the code objects for the Oracle E-Business Suite, and has access to all data objects. There is one APPS schema for every product installation group.

Utilizing a single schema that has access to all objects avoids cross-product dependencies, and creates a hub-and-spoke access model rather than the spider web model that would otherwise be needed. The APPS schema also improves the reliability of and reduces the time needed for installation, upgrading, and patching, by eliminating the need for cross-product grants and synonyms.

It wasn't always "APPS"

Older versions of EBS were delivered with a different default schema name: APPS_FND.  Some older versions even allowed you to override the default name of the schema prior to installation.

Recent versions of Oracle E-Business Suite use the APPS schema by default.  It is not possible to change the name of the APPS schema.

Hardcoded references to APPS are not permitted

We have many upgrade-related scripts, tools, and utilities.  All of these standard EBS tools are required to handle any EBS schema name, regardless of whether it is named APPS, APPS_FND, or something else.  There should be no hardcoded references to, say, the APPS schema. This development standard is enforced by regular automated scans of the entire EBS source code.

Earlier versions of some EBS upgrade scripts may have had hardcoded references to APPS.  Running an upgrade to, say, EBS 12.2 against an EBS environment with an EBS schema named APPS_FND would fail in certain circumstances.  This is not expected behavior.  We would regard that as a bug that needs to be fixed immediately.

All E-Business Suite scripts with hardcoded APPS schema references have since been superceded by later versions that can handle any EBS schema names.  To avoid issues with non-standard schema names, make sure that you're using the latest Rapid Install and AD/TXK utilities.  Click on the "Upgrade Recommendations" link in the sidebar of this site for pointers to the latest utilities.

Known issues

It is possible to integrate E-Business Suite environments with Oracle Identity Manager (OIM), which offers connectors that handle user provisioning.  Those OIM connection scripts still contain hardcoded references to the APPS schema (bug 24613821). 

Getting support

If you encounter any issues with non-standard EBS schema names, please log a formal Service Request with Oracle Support. You are welcome to drop me a line or post a comment here, too, if your schema-related SR gets stuck in the pipeline for some reason.

References

Categories: APPS Blogs

Installing Developer 10g 32-bit on 64-bit Windows versions

Fri, 2016-10-28 02:04

E-Business Suite 12.1 and 12.2 require Forms Developer 10g and Reports Designer 10g.  Forms Developer 10g and Reports Designer 10g are part of Oracle Developer Suite 10g.  Oracle Developer Suite 10g is a 32-bit program certified with Windows Vista, 7, 8.1, and 10.

Forcing 32-bit programs to run on 64-bit Windows

Although Windows 32-bit programs will not install by default on 64-bit versions of Windows, there are three possible workarounds:

Workaround 1: You can run the Developer 10g setup.exe installer in Windows compatibility mode > Windows XP (Service Pack 2) or Windows XP (Service Pack 3).  See Section 6 in Note 277535.1.

Workaround 2: You can let Windows determine how to install it automatically via the "Program Compatibility Assistant".  See Section 6 in Note 277535.1.

Windows Program Compatibility Assistant

Workaround 3: Install some additional patches and run the Developer 10g installer with the -ignoreSysPrereqs command line parameter.  See Note 1292919.1 for more details.

Related Articles
Categories: APPS Blogs

New OA Framework 12.2.5 Update 7 Now Available

Thu, 2016-10-27 02:04

Web-based content in Oracle E-Business Suite 12 runs on the Oracle Application Framework (OAF or "OA Framework") user interface libraries and infrastructure.  Since the release of Oracle E-Business Suite 12.2 in 2013, we have released several cumulative updates to Oracle Application Framework to fix performance, security, and stability issues. 

These updates are provided in cumulative Release Update Packs, and cumulative Bundle Patches that can be applied on top of the Release Update Pack. "Cumulative" means that the latest RUP or Bundle Patch contains everything released earlier.

The latest OAF update for EBS 12.2.5 is now available:

Screenshot EBS 12.2.5 OAF Bundle Patch 7

Where is the documentation for this update?

Instructions for installing this OAF Release Update Pack are here:

Who should apply this patch?

All EBS 12.2.5 users should apply this patch.  Future OAF patches for EBS 12.2.5 will require this patch as a prerequisite. 

What's new in this update?

This bundle patch is cumulative: it includes all fixes released in previous EBS 12.2.5 bundle patches.

This latest bundle patch includes new fixes for the following critical issues:

  • The number values in Total column in the Budget table are partially hidden after applying some set of ATG and Mobile Application patches.
  • Failed to return to the base page after submitting the popup due to client side validation.
  • The rawtext with style class set to OraInstrcutionText under HideShowHeader with style class OraHeaderSub does not word-wrap.
  • Tables are not get rendered properly when scrolling when there are more than 300 records in the table.
  • Page/form image icons are not aligned on home page with the function name links in Navigator and Favorites regions in Chrome and Firefox browsers.
  • The document catalog column was displayed on inline attachment popup windows even if document catalog option was disabled.
  • In HTTPS-enabled environments, navigating to 3-Frame JSP page shows a blank page since the request to load mixed active content has been blocked.
Related Articles
Categories: APPS Blogs

Quarterly EBS Upgrade Recommendations: October 2016 Edition

Tue, 2016-10-25 02:05

We've previously provided advice on the general priorities for applying EBS updates and creating a comprehensive maintenance strategy.   

Here are our latest upgrade recommendations for E-Business Suite updates and technology stack components.  These quarterly recommendations are based upon the latest updates to Oracle's product strategies, latest support timelines, and newly-certified releases

You can research these yourself using this Note:

Upgrade Recommendations for October 2016


EBS 12.2
 EBS 12.1
 EBS 12.0
 EBS 11.5.10
Check your EBS support status and patching baseline

Apply the minimum 12.2 patching baseline
(EBS 12.2.3 + latest technology stack updates listed below)

In Premier Support to September 30, 2023

Apply the minimum 12.1 patching baseline
(12.1.3 Family Packs for products in use + latest technology stack updates listed below)

In Premier Support to December 31, 2021

In Sustaining Support. No new patches available.

Upgrade to 12.1.3 or 12.2

Before upgrading, 12.0 users should be on the minimum 12.0 patching baseline

In Sustaining Support. No new patches available.

Upgrade to 12.1.3 or 12.2

Before upgrading, 11i users should be on the minimum 11i patching baseline

Apply the latest EBS suite-wide RPC or RUP

12.2.6
Sept. 2016

12.1.3 RPC5
Aug. 2016

12.0.6

11.5.10.2
Use the latest Rapid Install

StartCD 51
Feb. 2016

StartCD 13
Aug. 2011

12.0.6

11.5.10.2

Apply the latest EBS technology stack, tools, and libraries

AD/TXK Delta 8
Sept. 2016

FND
Aug. 2016

EBS 12.2.5 OAF Update 6
Sept. 2016

EBS 12.2.4 OAF Update 11
Jul. 2016

FMW 11.1.1.9

12.1.3 RPC5

OAF Bundle 5
Note 1931412.1
Jun. 2016

JTT Update 4
Oct. 2016



Apply the latest security updates

Oct. 2016 Critical Patch Update

SHA-2 PKI Certificates

SHA-2 Update for Web ADI & Report Manager

Switch from SSL to TLS

Sign JAR files

Oct. 2016 Critical Patch Update

SHA-2 PKI Certificates

SHA-2 Update for Web ADI & Report Manager

Switch from SSL to TLS

Sign JAR files

Oct. 2015 Critical Patch Update
April 2016 Critical Patch Update
Use the latest certified desktop components

Use the latest JRE 1.8, 1.7, or 1.6 release that meets your requirements

Upgrade to IE 11

Upgrade to Firefox ESR 45

Upgrade Office 2003 to later Office versions (e.g. Office 2016)

Upgrade Windows XP and Vista to later versions (e.g. Windows 10)

Use the latest JRE 1.8, 1.7, or 1.6 release that meets your requirements

Upgrade to IE 11

Upgrade to Firefox ESR 45

Upgrade Office 2003 to later Office versions (e.g. Office 2016)

Upgrade Windows XP and Vista to later versions (e.g. Windows 10)



Upgrade to the latest database Database 11.2.0.4 or 12.1.0.2 Database 11.2.0.4 or 12.1.0.2 Database 11.2.0.4 or 12.1.0.2 Database 11.2.0.4 or 12.1.0.2 If you're using Oracle Identity Management

Upgrade to Oracle Access Manager 11.1.2.3

Upgrade to Oracle Internet Directory 11.1.1.9

Migrate from Oracle SSO to OAM 11.1.2.3.0

Upgrade to Oracle Internet Directory 11.1.1.9



If you're using Oracle Discoverer
Migrate to Oracle Business Intelligence Enterprise Edition (OBIEE), Oracle Business Intelligence Applications (OBIA), or Discoverer 11.1.1.7. Migrate to Oracle Business Intelligence Enterprise Edition (OBIEE), Oracle Business Intelligence Applications (OBIA), or Discoverer 11.1.1.7.

If you're using Oracle Portal
Migrate to Oracle WebCenter  11.1.1.9
Migrate to Oracle WebCenter 11.1.1.9 or upgrade to Portal 11.1.1.6.



Categories: APPS Blogs

New OA Framework 12.2.6 Update Now Available

Mon, 2016-10-24 02:04

Web-based content in Oracle E-Business Suite 12 runs on the Oracle Application Framework (OAF or "OA Framework") user interface libraries and infrastructure.  Since the release of Oracle E-Business Suite 12.2 in 2013, we have released several cumulative updates to Oracle Application Framework to fix performance, security, and stability issues. 

These updates are provided in cumulative Release Update Packs, and cumulative Bundle Patches that can be applied on top of the Release Update Pack. "Cumulative" means that the latest RUP or Bundle Patch contains everything released earlier.

The latest OAF update for EBS 12.2.x is now available:

Where is the documentation for this update?

Instructions for installing this OAF Release Update Pack are here:

Who should apply this patch?

All EBS 12.2.6 users should apply this patch.  Future OAF patches for EBS 12.2.6 will require this patch as a prerequisite. 

I'm on an earlier EBS release.  Can I apply this patch?

Yes. This patch can be applied to all EBS 12.2.3 to 12.2.5 environments that have AD/TXK Delta 8 and ATG Delta 6 installed.

What's new in this update?

This bundle patch is cumulative: it includes all fixes released in previous EBS 12.2.x OAF bundle patches.

This latest bundle patch includes fixes for the following critical issues along with security :

  • Table scroll navigation issue when navigating to previous records
  • Javadoc for Layered Layout component
  • Reset icon in Personalization workbench not loading few times
  • UI distortion on the page after adding records in table in the last range
  • Worklist Font issue in Tree mode on Homepage
  • KFF combinations update event  was not getting processed for KFF inside table
  • Profile option name for profile FND_SHOW_INSTANCE_NAME changed to FND: Show Instance Name

Related Articles

Categories: APPS Blogs

Reminder: EBS 12.2 Minimum Patching Baselines and Dates

Fri, 2016-10-21 02:05

Oracle E-Business Suite 12.2 is now covered by Premier Support to September 30, 2023. This is documented here:

Oracle Lifetime Support table for EBS

Premier Support includes new EBS 12.2 patches for:

  • Individual product families (e.g. Oracle Financials)
  • Quarterly security updates released via the Critical Patch Update process
  • New technology stack certifications with server-based components
  • New certifications for end-user desktops and mobile devices

What are the minimum patching baselines for EBS 12.2?

The minimum patching baselines for EBS 12.2 have not changed.  New EBS 12.2 patches are created and tested against the minimum patching baseline documented in Section 4.1, "E-Business Suite 12.2 Minimum Prerequisites" in this document:

All EBS 12.2 customers must apply the minimum patch prerequisites to be eligible for Premier Support. Those patches include the suite-wide EBS 12.2.3 Release Update Pack and a small number of technology stack infrastructure updates.

Instead of applying the minimum baseline

Many new updates have been released since that patching baseline was originally published.  These new patches contain stability, performance, and security-related updates and are strongly recommended for all customers. 

If you haven't applied any of those updates yet, the simplest solution would be to apply the latest suite-wide EBS 12.2.6 Release Update Pack (RUP).  That way, you get all of the 12.2 minimum patching requirements and the latest updates simultaneously.

If you've reached this blog article via a search engine, it is possible that a new Release Update Pack has been released since this article was first published.  Click on the "Certifications" link in the sidebar for a pointer to the latest EBS 12.2 RUP.

Related Articles

Categories: APPS Blogs

EBS 12.2.6 OA Extensions for Jdeveloper 10g Now Available

Thu, 2016-10-20 02:06
Jdeveloper logoWhen you create extensions to Oracle E-Business Suite OA Framework pages, you must use the version of Oracle JDeveloper shipped by the Oracle E-Business Suite product team. 

The version of Oracle JDeveloper is specific to the Oracle E-Business Suite Applications Technology patch level, so there is a new version of Oracle JDeveloper with each new release of the Oracle E-Business Suite Applications Technology patchset.

The Oracle Applications (OA) Extensions for JDeveloper 10g are now available for E-Business Suite Release 12.2.6.  For details, see:

The same Note also lists the latest OA Extension updates for EBS 11i, 12.0, 12.1, and 12.2.

Related Articles

Categories: APPS Blogs

JRE 1.8.0_111/112 Certified with Oracle EBS 12.1 and 12.2

Wed, 2016-10-19 11:01

Java logo

Java Runtime Environment 1.8.0_111 (a.k.a. JRE 8u111-b14) and its corresponding Patch Set Update (PSU) JRE 1.8.0_112 and later updates on the JRE 8 codeline are now certified with Oracle E-Business Suite 12.1 and 12.2 for Windows desktop clients.

All JRE 6, 7, and 8 releases are certified with EBS upon release

Our standard policy is that all E-Business Suite customers can apply all JRE updates to end-user desktops:

  • From JRE 1.6.0_03 and later updates on the JRE 6 codeline
  • From JRE 1.7.0_10 and later updates on the JRE 7 codeline 
  • From JRE 1.8.0_25 and later updates on the JRE 8 codeline
We test all new JRE releases in parallel with the JRE development process, so all new JRE releases are considered certified with the E-Business Suite on the same day that they're released by our Java team. 

You do not need to wait for a certification announcement before applying new JRE 6, 7, or 8 releases to your EBS users' desktops.

What's new in this release?

Oracle now releases a Critical Patch update (CPU) at the same time as the corresponding Patch Set Update (PSU) release for Java SE 8.

  • CPU Release:  JRE 1.8.0_111
  • PSU Release:  JRE 1.8.0_112
Oracle recommends that Oracle E-Business Suite customers use the CPU release (JRE 1.8.0_111) and only upgrade to the PSU release (1.8.0_112) if they require a specific bug fix.  For further information and bug fix details see Java CPU and PSU Releases Explained.

32-bit and 64-bit versions certified

This certification includes both the 32-bit and 64-bit JRE versions for various Windows operating systems. See the respective Recommended Browser documentation for your EBS release for details.

Where are the official patch requirements documented?

All patches required for ensuring full compatibility of the E-Business Suite with JRE 8 are documented in these Notes:

For EBS 12.1 & 12.2

EBS + Discoverer 11g Users

This JRE release is certified for Discoverer 11g in E-Business Suite environments with the following minimum requirements:

Implications of Java 6 and 7 End of Public Updates for EBS Users

The Oracle Java SE Support Roadmap and Oracle Lifetime Support Policy for Oracle Fusion Middleware documents explain the dates and policies governing Oracle's Java Support.  The client-side Java technology (Java Runtime Environment / JRE) is now referred to as Java SE Deployment Technology in these documents.

Starting with Java 7, Extended Support is not available for Java SE Deployment Technology.  It is more important than ever for you to stay current with new JRE versions.

If you are currently running JRE 6 on your EBS desktops:

  • You can continue to do so until the end of Java SE 6 Deployment Technology Extended Support in June 2017
  • You can obtain JRE 6 updates from My Oracle Support.  See:

If you are currently running JRE 7 on your EBS desktops:

  • You can continue to do so until the end of Java SE 7 Deployment Technology Premier Support in July 2016
  • You can obtain JRE 7 updates from My Oracle Support.  See:

If you are currently running JRE 8 on your EBS desktops:

Will EBS users be forced to upgrade to JRE 8 for Windows desktop clients?

No.

This upgrade is highly recommended but remains optional while Java 6 and 7 are covered by Extended Support. Updates will be delivered via My Oracle Support, where you can continue to receive critical bug fixes and security fixes as well as general maintenance for JRE 6 and 7 desktop clients. Note that there are different impacts of enabling JRE Auto-Update depending on your current JRE release installed, despite the availability of ongoing support for JRE 6 and 7 for EBS customers; see the next section below.

Impact of enabling JRE Auto-Update

Java Auto-Update is a feature that keeps desktops up-to-date with the latest Java release.  The Java Auto-Update feature connects to java.com at a scheduled time and checks to see if there is an update available.

Enabling the JRE Auto-Update feature on desktops with JRE 6 installed will have no effect.

With the release of the January Critical patch Updates, the Java Auto-Update Mechanism will automatically update JRE 7 plug-ins to JRE 8.

Enabling the JRE Auto-Update feature on desktops with JRE 8 installed will apply JRE 8 updates.

Coexistence of multiple JRE releases Windows desktops

The upgrade to JRE 8 is recommended for EBS users, but some users may need to run older versions of JRE 6 or 7 on their Windows desktops for reasons unrelated to the E-Business Suite.

Most EBS configurations with IE and Firefox use non-static versioning by default. JRE 8 will be invoked instead of earlier JRE releases if both are installed on a Windows desktop. For more details, see "Appendix B: Static vs. Non-static Versioning and Set Up Options" in Notes 290807.1 and 393931.1.

What do Mac users need?

JRE 8 is certified for Mac OS X 10.8 (Mountain Lion), 10.9 (Mavericks), 10.10 (Yosemite), and 10.11 (El Capitan) desktops.  For details, see:

Will EBS users be forced to upgrade to JDK 8 for EBS application tier servers?

No.

JRE is used for desktop clients.  JDK is used for application tier servers.

JRE 8 desktop clients can connect to EBS environments running JDK 6 or 7.

JDK 8 is not certified with the E-Business Suite.  EBS customers should continue to run EBS servers on JDK 6 or 7.

Known Iusses

Internet Explorer Performance Issue

Launching JRE 1.8.0_73 through Internet Explorer will have a delay of around 20 seconds before the applet starts to load (Java Console will come up if enabled).

This issue fixed in JRE 1.8.0_74.  Internet Explorer users are recommended to uptake this version of JRE 8.

Form Focus Issue

Clicking outside the frame during forms launch may cause a loss of focus when running with JRE 8 and can occur in all Oracle E-Business Suite releases. To fix this issue, apply the following patch:

References

Related Articles
Categories: APPS Blogs

JRE 1.7.0_111 Certified with Oracle E-Business Suite 12.1 and 12.2

Wed, 2016-10-19 10:54

Java logo

Java Runtime Environment 1.7.0_121 (a.k.a. JRE 7u121-b15) and later updates on the JRE 7 codeline are now certified with Oracle E-Business Suite Release 12.1 and 12.2 for Windows-based desktop clients.

All JRE 6, 7, and 8 releases are certified with EBS upon release

Our standard policy is that all E-Business Suite customers can apply all JRE updates to end-user desktops:

  • From JRE 1.6.0_03 and later updates on the JRE 6 codeline
  • From JRE 1.7.0_10 and later updates on the JRE 7 codeline 
  • From JRE 1.8.0_25 and later updates on the JRE 8 codeline
We test all new JRE releases in parallel with the JRE development process, so all new JRE releases are considered certified with the E-Business Suite on the same day that they're released by our Java team. 

You do not need to wait for a certification announcement before applying new JRE 6, 7, or 8 releases to your EBS users' desktops.

Effects of new support dates on Java upgrades for EBS environments

Support dates for the E-Business Suite and Java have changed.  Please review the sections below for more details:

  • What does this mean for Oracle E-Business Suite users?
  • Will EBS users be forced to upgrade to JRE 7 for Windows desktop clients?
  • Will EBS users be forced to upgrade to JDK 7 for EBS application tier servers?

32-bit and 64-bit versions certified

This certification includes both the 32-bit and 64-bit JRE versions for various Windows operating systems. See the respective Recommended Browser documentation for your EBS release for details.

Where are the official patch requirements documented?

EBS + Discoverer 11g Users

This JRE release is certified for Discoverer 11g in E-Business Suite environments with the following minimum requirements:

JRE 7 End of Public Updates

The JRE 7u79 release was the last JRE 7 update available to the general public.  Java is an integral part of the Oracle E-Business Suite technology stack, so EBS users will continue to receive Java SE 7 updates to the end of Java SE 7 Premier Support to the end of July 2016.

How can EBS customers obtain Java 7 updates after the public end-of-life?

EBS customers can download Java 7 patches from My Oracle Support.  For a complete list of all Java SE patch numbers, see:

Both JDK and JRE packages are now contained in a single combined download.  Download the "JDK" package for both the desktop client JRE and the server-side JDK package. 

Coexistence of multiple JRE releases Windows desktops

The upgrade to JRE 8 is recommended for EBS users, but some users may need to run older versions of JRE 6 or 7 on their Windows desktops for reasons unrelated to the E-Business Suite.

Most EBS configurations with IE and Firefox use non-static versioning by default. JRE 8 will be invoked instead of earlier JRE releases if both are installed on a Windows desktop. For more details, see "Appendix B: Static vs. Non-static Versioning and Set Up Options" in Notes 290807.1 and 393931.1.

Java Auto-Update Mechanism

With the release of the January 2015 Critical patch Updates, the Java Auto-Update Mechanism will automatically update JRE 7 plug-ins to JRE 8.

Coexistence of multiple JRE releases Windows desktops

The upgrade to JRE 8 is recommended for EBS users, but some users may need to run older versions of JRE 6 or 7 on their Windows desktops for reasons unrelated to the E-Business Suite.

Most EBS configurations with IE and Firefox use non-static versioning by default. JRE 8 will be invoked instead of earlier JRE releases if both are installed on a Windows desktop. For more details, see "Appendix B: Static vs. Non-static Versioning and Set Up Options" in Notes 290807.1 and 393931.1.

What do Mac users need?

Mac users running Mac OS X 10.7 (Lion), 10.8 (Mountain Lion), 10.9 (Mavericks), and 10.10 (Yosemite) can run JRE 7 or 8 plug-ins.  See:

Will EBS users be forced to upgrade to JDK 7 for EBS application tier servers?

JRE is used for desktop clients.  JDK is used for application tier servers

JDK upgrades for E-Business Suite application tier servers are highly recommended but currently remain optional while Java 6 is covered by Extended Support. Updates will be delivered via My Oracle Support, where you can continue to receive critical bug fixes and security fixes as well as general maintenance for JDK 6 for application tier servers. 

Java SE 6 is covered by Extended Support until June 2017.  All EBS customers with application tier servers on Windows, Solaris, and Linux must upgrade to JDK 7 by June 2017. EBS customers running their application tier servers on other operating systems should check with their respective vendors for the support dates for those platforms.

JDK 7 is certified with E-Business Suite 12.  See:

Known Issues

When using Internet Explorer, JRE 1.7.0_01 had a delay of around 20 seconds before the applet started to load. This issue is fixed in JRE 1.7.0_95.

References

Related Articles
Categories: APPS Blogs

JRE 1.6.0_131 Certified with Oracle E-Business Suite 12.1 and 12.2

Wed, 2016-10-19 10:50
Java logThe latest Java Runtime Environment 1.6.0_131 (a.k.a. JRE 6u131-b14) and later updates on the JRE 6 codeline are now certified with Oracle E-Business Suite Release 12.1 and 12.2 for Windows-based desktop clients.

All JRE 6, 7, and 8 releases are certified with EBS upon release

Our standard policy is that all E-Business Suite customers can apply all JRE updates to end-user desktops:

  • From JRE 1.6.0_03 and later updates on the JRE 6 codeline
  • From JRE 1.7.0_10 and later updates on the JRE 7 codeline 
  • From JRE 1.8.0_25 and later updates on the JRE 8 codeline
We test all new JRE releases in parallel with the JRE development process, so all new JRE releases are considered certified with the E-Business Suite on the same day that they're released by our Java team. 

You do not need to wait for a certification announcement before applying new JRE 6, 7, or 8 releases to your EBS users' desktops.

Effects of new support dates on Java upgrades for EBS environments

Support dates for the E-Business Suite and Java have changed.  Please review the sections below for more details:

  • What does this mean for Oracle E-Business Suite users?
  • Will EBS users be forced to upgrade to JRE 7 for Windows desktop clients?
  • Will EBS users be forced to upgrade to JDK 7 for EBS application tier servers?

New EBS installation scripts

This JRE release is the first with a 3-digit Java version. Installing this in your EBS 11i and 12.x environments will require new installation scripts.  See the documentation listed in the 'References' section for more detail.

32-bit and 64-bit versions certified

This certification includes both the 32-bit and 64-bit JRE versions for various Windows operating systems. See the respective Deploying JRE documentation for your EBS release for details.

Implications of Java 6 End of Public Updates for EBS Users

The Support Roadmap for Oracle Java is published here:

The latest updates to that page (as of Sept. 19, 2012) state:

Java SE 6 End of Public Updates Notice

After February 2013, Oracle will no longer post updates of Java SE 6 to its public download sites. Existing Java SE 6 downloads already posted as of February 2013 will remain accessible in the Java Archive on Oracle Technology Network. Developers and end-users are encouraged to update to more recent Java SE versions that remain available for public download. For enterprise customers, who need continued access to critical bug fixes and security fixes as well as general maintenance for Java SE 6 or older versions, long term support is available through Oracle Java SE Support .

What does this mean for Oracle E-Business Suite users?

EBS users fall under the category of "enterprise users" above.  Java is an integral part of the Oracle E-Business Suite technology stack, so EBS users will continue to receive Java SE 6 updates from February 2013 to the end of Java SE 6 Extended Support in June 2017.

In other words, nothing changes for EBS users after February 2013. 

EBS users will continue to receive critical bug fixes and security fixes as well as general maintenance for Java SE 6 until the end of Java SE 6 Extended Support in June 2017. 

How can EBS customers obtain Java 6 updates after the public end-of-life?

Java 6 is now available only via My Oracle Support for E-Business Suite users.  You can find links to this release, including Release Notes, documentation, and the actual Java downloads here: Both JDK and JRE packages are contained in a single combined download after 6u45.  Download the "JDK" package for both the desktop client JRE and the server-side JDK package.

Coexistence of multiple JRE releases Windows desktops

The upgrade to JRE 8 is recommended for EBS users, but some users may need to run older versions of JRE 6 or 7 on their Windows desktops for reasons unrelated to the E-Business Suite.

Most EBS configurations with IE and Firefox use non-static versioning by default. JRE 8 will be invoked instead of earlier JRE releases if both are installed on a Windows desktop. For more details, see "Appendix B: Static vs. Non-static Versioning and Set Up Options" in Notes 290807.1 and 393931.1.

What do Mac users need?

Mac users running Mac OS X 10.10 (Yosemite) can run JRE 7 or 8 plug-ins.  See:

Will EBS users be forced to upgrade to JDK 7 for EBS application tier servers?

JRE is used for desktop clients.  JDK is used for application tier servers

JDK upgrades for E-Business Suite application tier servers are highly recommended but currently remain optional while Java 6 is covered by Extended Support. Updates will be delivered via My Oracle Support, where you can continue to receive critical bug fixes and security fixes as well as general maintenance for JDK 6 for application tier servers. 

Java SE 6 is covered by Extended Support until June 2017.  All EBS customers with application tier servers on Windows, Solaris, and Linux must upgrade to JDK 7 by June 2017. EBS customers running their application tier servers on other operating systems should check with their respective vendors for the support dates for those platforms.

JDK 7 is certified with E-Business Suite 12.  See:

References

Related Articles

Categories: APPS Blogs

Critical Patch Update for October 2016 Now Available

Tue, 2016-10-18 14:49

The Critical Patch Update (CPU) for October 2016 was released on October 18, 2016. Oracle strongly recommends applying the patches as soon as possible.

The Critical Patch Update Advisory is the starting point for relevant information. It includes a list of products affected, pointers to obtain the patches, a summary of the security vulnerabilities, and links to other important documents. 

Supported products that are not listed in the "Supported Products and Components Affected" Section of the advisory do not require new patches to be applied.

The Critical Patch Update Advisory is available at the following location:

It is essential to review the Critical Patch Update supporting documentation referenced in the Advisory before applying patches.

The next four Critical Patch Update release dates are:

  • January 17, 2017
  • April 18, 2017
  • July 18, 2017
  • October 17, 2017
References Related Articles
Categories: APPS Blogs

Configuring Reverse Proxies and DMZs for EBS 12.2

Mon, 2016-10-17 02:06

You may have end-users outside of your organization's firewall who need access to E-Business Suite.  One way of doing that is to set up a reverse proxy server and a series of network segments separated by firewalls. 

EBS DMZ architecture

The outermost network segment that lies between the internet and an organization's intranet is often called a Demilitarized Zone (DMZ).  DMZs are enforced by firewalls and other networking security devices.

Setting up a DMZ

Instructions for deploying EBS 12.2 in a DMZ-based architecture are published here:

Externally-facing EBS products

A subset of EBS products can be deployed for external use, including iSupplier, iRecruitment, iSupport, and others.  Many of these products have special rules that must be enabled in the URL Firewall to work properly in external deployments.  For a complete list of E-Business Suite products certified for external use, see Section 6 in Note 1375670.1.

Related Articles


Categories: APPS Blogs

Which Oracle Access Manager Patchsets Can Be Used with EBS?

Fri, 2016-10-14 02:04

Oracle versions numbers can be very long.  Complicating matters further, different product families within Oracle use the version hierarchy differently.  This can make it confusing to determine whether a specific product update has been certified with Oracle E-Business Suite.

Specifically, a customer recently asked whether it was acceptable to apply the Oracle Access Manager 11.1.2.2.8 patchset to their OAM instance that was integrated with EBS 12.1.3.  They were concerned because our OAM integration documentation for that combination explicitly specified compatibility with OAM 11.1.2.2.0.

In this particular case, the fifth-level digit in the Oracle Access Manager version is not relevant.  In other words, the customer could apply OAM 11.1.2.2.8 because it was covered by the OAM 11.1.2.2.0 certification. 

For example, all of the following OAM patchsets will work with EBS 12.1.3:

  • OAM 11.1.2.2.0 (documented certification)
  • OAM 11.1.2.2.1
  • OAM 11.1.2.2.2
  • OAM 11.1.2.2.3
  • OAM 11.1.2.2.4
  • OAM 11.1.2.2.5
  • OAM 11.1.2.2.6
  • OAM 11.1.2.2.7
  • OAM 11.1.2.2.8

This is sometimes shown in our documentation in either of the following ways:

  • OAM 11.1.2.2
  • OAM 11.1.2.2.x

The absence of a fifth-digit or the presence of an 'X' in the fifth digit's place means any fifth-digit level updates may be applied to an OAM environment integrated with EBS 12.1.3 without requiring a new certification.  This applies to all environments, including test and production.

Related Articles

Categories: APPS Blogs

MS16-104 Security Update for IE Breaks EBS JRE Download

Thu, 2016-10-13 02:04

Microsoft IE LogoMS16-104: Security update for Internet Explorer: September 13, 2016 (KB3185319) breaks the JRE (oaj2se.exe) download function in Oracle E-Business Suite 12.1 and 12.2. This issue occurs with IE 11 on Windows 7, 8.1, and 10.

Expected behaviour: If an end-user does not have the required JRE plug-in release installed on their desktop client, a dialog box appears, asking whether they wish to download it from the EBS server. When the end-user confirms the download, the oaj2se.exe file downloads and runs.

Incorrect behaviour after the installation of KB3185319: When the end-user confirms the download via the dialog box, oaj2se.exe (the JRE) will not download.

How to fix this problem

Microsoft has published separate fixes for this issue for Windows 7, 8.1, and 10.  The appropriate patch must be installed on all affected end-user desktop clients:

Temporary workaround

If an end-user has installed KB3185319 but is unable to install the fix, end-users may work around the problem by entering the file's URL in Internet Explorer's address bar.  For example:

http(s)://<myserver.example.com>:<port>/OA_HTML/oaj2se.exe

Reference

Related Articles


Categories: APPS Blogs

Balancing EBS JRE Requirements With Other Java Apps

Wed, 2016-10-12 02:05

Java logoCustomers frequently ask me, "What's the best way of handling JRE requirements when I have other Java applications in addition to Oracle E-Business Suite?"

The short answer: you should always try to use the latest JRE release, but before you do that, you need to review your enterprise JRE requirements carefully to ensure that all of your applications are compatible with it.

Why you should always deploy the latest JRE updates

JRE updates include fixes for stability, performance, and security.  The most-important fixes are for security, of course.  Therefore, we strongly recommend that customers stay current with the latest JRE release.  This applies to all Java customers, not just E-Business Suite customers.

New JRE releases are always certified with EBS on day zero

The E-Business Suite is always certified with all new JRE releases on JRE 1.6, 1.7, and 1.8.  We test all EBS releases with beta versions of JRE updates before the latter are released, so there should be no EBS compatibility issues.  Customers can even turn on Auto-Update (which ensures that a new JRE update is automatically applied to a desktop whenever it’s available) with no concerns about EBS compatibility.

Which JRE codeline is recommended for Oracle E-Business Suite?

Oracle E-Business Suite does not have any dependencies on a specific JRE codeline.  All three JRE releases – 1.6, 1.7, 1.8 – work the same way with EBS. 

You should pick whichever JRE codeline works best with the rest of your third-party applications.

Check the compatibility of all third-party Java applications in use

Of course, Oracle cannot make any assurances about compatibility with other third-party products.  I have heard from some customers who have Java-based applications whose certifications lag behind the latest JRE release.

Organizations need to maintain a comprehensive matrix that shows the latest certified JRE releases for all of their Java applications. This matrix should include the E-Business Suite.

Take the "lowest-common denominator" approach

Customers with multiple Java-based applications generally are forced to take a “lowest-common denominator” approach.  Even if Oracle E-Business Suite and the majority of your Java-based applications are compatible with the latest JRE release, any lagging application's incompatibility with the latest JRE release will force you to remain on the earliest version that is common to all of them.

For example:

  • An organization runs Oracle E-Business Suite and four third-party Java-based applications
  • Oracle E-Business Suite is certified with the latest JRE release
  • Three of the third-party applications are certified with the latest JRE release
  • One of the third-party applications is certified only on the previous JRE release
  • The organization is forced to deploy the previous JRE release to their desktops. 

Contact all of your third-party vendors

Organizations whose JRE deployments are held back by a particular application's incompatibility should contact the vendor for that application and ask them test with Java Early Access downloads or to participate in the Oracle CAP Program.


Categories: APPS Blogs

Which EBS 12.1.3 RPC Should I Apply?

Tue, 2016-10-11 02:05

A customer was in the process of upgrading their EBS 12.1.3 environment to RPC 4 when they heard about the release of RPC 5.  They asked, "Which one should we apply?"

This kind of question crops up frequently since we're continually producing new EBS updates. There is no definitive right answer.  For example, the answer depends upon:

  • How far a customer might have progressed in their testing of the previous update
  • The number of customizations affected by the respective updates
  • Whether the customer wants new functionality available only in the latest update
  • Whether the customer needs fixes that are only available in the latest update
  • How risk-averse the customer is (e.g. "Let other customers live on the bleeding edge")
  • etc.

EBS 12.1.3 RPC 5 screenshot download

What is a Recommended Patch Collection?

Recommended Patch Collections (RPC) are collections of patches that we have already released individually for EBS 12.1.3.

Customers can apply individual patches or they can apply a Recommended Patch Collection.  Either approach is fine.

We periodically bundle the latest patches together to save you the trouble of applying them individually.  As an added bonus, all patches in a given RPC are tested together for compatibility, which isn't always true for individual patches that are released on an emergency basis.

Recommended Patch Collections are not a “release.”  We currently have no plans to make a specific RPC a minimum baseline or prerequisite for new EBS 12.1 patches. 

What is our policy for releasing EBS patches?

Our official policy for releasing EBS 12.1 and 12.2 patches is published here:

Our current policy is that EBS 12.1.3 users should apply the latest 12.1.3 product family patches for the products in use, plus a small number of ATG technology stack patches. We will produce new EBS patches for issues that can be reproduced in environments with those prerequisites.

What's the best strategy for applying EBS 12.1.3 Recommended Patch Collections?

We generally recommend applying the latest EBS updates to production as soon as it's convenient for your users.

If you're in the middle of testing a specific RPC and it's too late to switch to a newer one, go ahead and complete your patching project on production. You can always apply the next RPC in a subsequent project.

Related Articles

Categories: APPS Blogs

DSTv27 Timezone Patches Available for E-Business Suite 12.2

Mon, 2016-10-10 02:11
Hourglass iconIf your E-Business Suite Release environment is configured to support Daylight Saving Time (DST) or international time zones, it's important to keep your timezone definition files up-to-date. They were last changed in November 2015 and released as DSTv25.

DSTv27 is now available and certified with Oracle E-Business Suite Release 12.2. The DSTv27 update includes the timezone information from the IANA tzdata 2016f.  It is cumulative: it includes all previous Oracle DST updates. 

Is Your Apps Environment Affected?

When a country or region changes DST rules or their time zone definitions, your Oracle E-Business Suite environment will require patching if:

  • Your Oracle E-Business Suite environment is located in the affected country or region OR
  • Your Oracle E-Business Suite environment is located outside the affected country or region but you conduct business or have customers or suppliers in the affected country or region

The latest DSTv27 timezone definition file is cumulative and includes all DST changes released in earlier time zone definition files. DSTv27 includes changes to the following timezones since the DSTv24 release:

  • Asia/Novosibirsk
  • America/Cayman
  • Asia/Chita
  • Asia/Tehran,
  • Haiti,
  • Palestine,
  • Azerbaijan,
  • Chile
  • America/Caracas
  • Asia/Magadan

What Patches Are Required?

In case you haven't been following our previous time zone or Daylight Saving Time (DST)-related articles, international timezone definitions for E-Business Suite environments are captured in a series of patches for the database and application tier servers in your environment. The actual scope and number of patches that need to be applied depend on whether you've applied previous DST or timezone-related patches. Some sysadmins have remarked to me that it generally takes more time to read the various timezone documents than it takes to apply these patches, but your mileage may vary.

Proactive backports of DST upgrade patches to all Oracle E-Business Suite tiers and platforms are not created and supplied by default. If you need this DST release and an appropriate patch is not currently available, raise a service request through support providing a business case with your version requirements.

The following Note identifies the various components in your E-Business Suite environment that may need DST patches:

What is the business impact of not applying these patches?

Timezone patches update the database and other libraries that manage time. They ensure that those libraries contain the correct dates and times for the changeover between Daylight Savings Time and non-Daylight Savings Time.

Time is used to record events, particularly financial transactions.  Time is also used to synchronize transactions between different systems.  Some organizations’ business transactions are more-sensitive to timezone changes than others. 

If you do not apply a timezone patch, and do business with a region that has changed their timezone definitions, and record a transaction that occurs at the boundary between the “old” and the “new” time, then the transaction may be recorded incorrectly. That transaction's timestamp may be off by an hour. 

For example:

  • An order is placed for a customer in a country which changed their DST dates in DST v27
  • The old Daylight Savings Time expiration date was Nov. 2
  • The new Daylight Savings Time expiration date is now October 31
  • An order is set to ship at 12am on November 1st
  • Under the old Daylight Savings Time rules, the revenue would be recorded for November
  • Under the new Daylight Savings Time rules, the revenue would be recorded for October

Related Article

Oracle's Revenue Recognition rules prohibit us from discussing certification and release dates, but you're welcome to monitor or subscribe to this blog. I'll post updates here as soon as soon as they're available.   


Categories: APPS Blogs

E-Business Suite and Java Web Start: Frequently-Asked Questions

Fri, 2016-10-07 02:04
Does EBS depend upon Java on desktop clients?

Yes.  The E-Business Suite requires Forms.  Forms is started by a Java applet.

Java applets are launched by the Java Plug-in using a browser that supports plug-ins via the NPAPI protocol.

The Java plug-in runs in the browser memory space and manages the execution of the Forms applet and other EBS applets in one or more separate Java Virtual Machines (JVM).  Java Plug-in also supports the communication between these JVMs and browsers.

Will E-Business Suite still require Java in the future?

Yes.  It is expected that our ongoing use of Forms for high-volume professional users of the E-Business Suite means that EBS will continue to require Java.  We replicate, simplify, or migrate selected Forms-based flows to OA Framework-based (i.e. web-based HTML) equivalents with every EBS update, but Forms is expected to continue to be part of the E-Business Suite technology stack for the foreseeable future. 

Does the E-Business Suite have other Java applet dependencies?

Yes.  In addition to Forms, various E-Business Suite products have functionality that runs as Java applets.  These Java applets require browsers that offer plugin support.  These products include applets:

  • Oracle General Ledger (GL)
  • Oracle Customers Online (IMC)
  • Oracle Call Center Technology (CCT)
  • Oracle Sourcing (PON)
  • Oracle Install Base (CSI)
  • Oracle Demand Planning (MSD)
  • Oracle Advanced Supply Chain Planning (MSC)
  • Workflow (WF)
  • Scripting (IES)

What is going on with browsers' support for plug-ins?

Plug-in support is referred to in various ways, including:

Some browsers are phasing out plug-in support. Some browsers were never released with plug-in support.

Some organizations may wish to use browsers that do not offer plugin support, so we're working on a new approach that will work with all browsers. 

What is the new approach?

It's not technically "new" (it is a mature Java technology), but we're using it for the first time with the E-Business Suite.  This "new" approach launches EBS Forms-based screens and other functionality as Java Web Start (JWS) applications instead of as applets.

Will EBS use Java Web Start?

Yes, it is expected that Oracle E-Business Suite will be updated to use Java Web Start. It is expected that this will apply to EBS 12.1 and 12.2.

We have prototypes of EBS applets now launched as Java Web Start applications working today, so this project is already well-underway.  We are polishing and refining issues around window handling, usability, and other areas right now.  Our goal is to make the transition from the current JRE plug-in to Java Web Start as seamless as possible for all EBS end-users.

How does the technology architecture change?

Java Web Start changes the way that Java runs on end-users' computers but this technical change is expected to be invisible to end-users.

Java Web Start applications are launched from browsers using the Java Network Launching Protocol (JNLP).

Will the end-user's experience change?

No, we are working hard to ensure that your end-users' experience with Java Web Start applications will be as similar as possible to applets via JRE.  The differences between applets invoked by JRE and Java Web Start are expected to be almost-invisible to end-users.

For example, today with applets via JRE:

  • JRE runs when your end-users click on an EBS Navigator link to a screen that runs in Forms.

Tomorrow, with Java Web Start:

  • Java Web Start runs when your end-users click on an EBS Navigator link to a screen that runs in Forms.

What happens with Java 9?

The Java team recently published their plans for removing the Java browser plugin in a future version of Java. The announcement states (key words highlighted for emphasis):

Oracle plans to deprecate the Java browser plugin in JDK 9. This technology will be removed from the Oracle JDK and JRE in a future Java SE release.

What does "deprecate" mean?

"Deprecate" means that there will still be a Java Plug-in in JRE 9. The deprecation of the Java Plug-in should not be confused with Java Web Start or Java on the desktop itself.  The latter two will be available for the foreseeable future.  Users will still be able to run Java-based applications using the Java Plug-in in JRE 9.

What does this mean for E-Business Suite users running JRE 9?

The release of Java 9 will not affect E-Business Suite users. JRE 9 will continue to work with the E-Business Suite in browsers that support Java (via the NPAPI protocol). 

What browsers will support the JRE 9 plug-in?

Internet Explorer, Firefox ESR, and Safari will continue to support NPAPI -- and, therefore, Java and Forms.  We recommend that customers who need to use Forms-based products in the E-Business Suite use those browsers.

Alphabet (Google) Chrome and Microsoft Edge do not support NPAPI, so Java-based apps cannot run in those browsers.  

What browsers will support Java Web Start?

It is expected that Java Web Start will work with all browsers, including those that do not work with plugins. 

What are the timelines for browsers' plugin support?

Individual browser vendors have been updating their plans regularly.  Here's a snapshot of what some browser vendors have stated as of today:

Microsoft Internet Explorer (IE)

Microsoft has indicated that they intend to continue to offer plug-in support in IE.

Microsoft Edge

Microsoft Edge was released in Windows 10 without Browser Helper Object (BHO, aka. plugin) support.  Microsoft has no plans to add plugin support to Edge.

Mozilla Firefox Extended Support Release (ESR)

Mozilla indicated in early 2016 that Firefox ESR 52 will be the last version to offer NPAPI (and JRE) support.  Firefox ESR 52 is targeted for release in April 2017 and will be supported until May 2018. 

Mozilla Firefox Rapid Release

Mozilla intends to remove NPAPI support from the Firefox 53 Rapid Release version targeted for release in April 2017. 

Apple Safari for Mac OS

Safari offers Internet plug-in support for Mac OS users.  Apple has not made any statements about deprecating plugin support for Mac OS users.

Alphabet (Google) Chrome for Windows

Chrome offered support for plugins until version 45, released in September 2015.  They removed NPAPI support in later Chrome releases.

Will I need to change browsers?

No.  JRE will continue to work with browsers that include NPAPI plug-in support.  If your organization already uses those browsers, it is expected that you will be able to continue using those browsers. 

Will Oracle release its own browser for the E-Business Suite?

No.  Long-time Oracle users may remember the Oracle PowerBrowser. The industry has since moved away from software that requires proprietary browsers.  We have no plans to release a browser specifically for E-Business Suite users. 

Will Java Web Start be mandatory?

Not for the time being. It is expected that the use of Java Web Start will be optional at least up to Java 9, which may be the last Java release to include the JRE browser plugin. 

Will Java Web Start coexist with JRE?

Yes, it is expected that you be able to have some users launching Java Web Start applications, while others use applets via JRE, connecting to the same E-Business Suite environment. It is expected that you will have full server-side control over these choices.

What prerequisites will be needed for Java Web Start?

We plan to offer Java Web Start for EBS 12.1 and 12.2.  It is expected that a small number of server-side patches for Forms and EBS will be needed. 

All prerequisites are expected to be published here:

Will this affect EBS customizations?

Maybe. It depends upon which of the following apply to your environment:

  • Scenario 1You have modified standard EBS screens running in Forms:  No actions needed. These customizations are expected to work with Java Web Start without any additional changes.
  • Scenario 2You have built custom Java applets of your own to extend the E-Business Suite:  These will continue to run with JRE, but you may wish to update those applets to use Java Web Start.
  • Scenario 3You have third-party extensions or products that depend upon JRE: These will continue to run with JRE, but you may wish to contact your third-party vendor for details about their plans for Java Web Start.

When will Java Web Start be available?

Oracle's Revenue Recognition rules prohibit us from discussing certification and release dates, but you're welcome to monitor or subscribe to this blog. I'll post updates here as soon as soon as they're available.   

Related Articles

Disclaimer

The preceding is intended to outline our general product direction.  It is intended for information purposes only, and may not be incorporated into any contract.   It is not a commitment to deliver any material, code, or functionality, and should not be relied upon in making purchasing decision.  The development, release, and timing of any features or functionality described for Oracle’s products remains at the sole discretion of Oracle.


Categories: APPS Blogs

Updated: Minimizing EBS 12.2.6 Upgrade Downtimes

Thu, 2016-10-06 02:05

We have updated our recommendations for minimizing downtimes when upgrading to EBS 12.2.6:

Written by Jim Machin, a senior member of our Applications Performance group, this white paper contains a wealth of detailed technical recommendations for reducing the amount of time needed for an EBS 12.2.6 upgrade. 

Events vs. sessions bottlenecks diagram

It covers:

  • Technical preparation and planning activities
  • Diagnostics for monitoring and troubleshooting performance issues
  • Common solutions to performance issues
  • Oracle Applications Tablespace Model (OATM) considerations
  • Methods for purging old data
  • Gathering statistics
  • Detailed recommendations for improving resource management, sizing, and workloads

This white paper is updated regularly with new tips and recommendations based upon our Application Performance group's work with actual EBS 12.2 customers and their Service Requests.  All EBS 12.2 sysadmins should monitor this white paper regularly.

Related Articles

Categories: APPS Blogs

Pages