Thursday Feb 26, 2015

Reminder: Upgrade Database 12.1.0.1 to 12.1.0.2 by July 2015

E-Business Suite customers must ensure that their database remains on a level that is covered by Error Correction Support (ECS) -- i.e. while you can get new patches, Critical Patch Updates (CPU), and Patch Set Updates (PSU).  We've covered this in detail here:

The following Note lists Error Correction Support dates for all database patchsets for all database releases:

That Note shows that patching ends for the 12.1.0.1 Database patchset on July 22, 2015. All EBS customers on Database 12.1.0.1 should upgrade to the Database 12c 12.1.0.2 patchset before then. 

Related Articles

Friday Feb 20, 2015

EBS 12.x certified with Apple Mac OS X 10.10 (Yosemite)

Apple logoOracle E-Business Suite Release 12 (12.1.3, 12.2.4 or higher) is now certified with Apple Mac OS X 10.10 (Yosemite) with the following desktop configuration:

  • Mac OS X 10.10 ("Yosemite" version 10.10.2 or higher)
  • Safari version 8 (8.0.3 or higher)
  • Oracle JRE 7 plugin (1.7.0_72 or higher) and JRE 8 plugin (1.8.0_31 or higher)

Users should review all relevant information along with other specific patching requirements and known limitations posted in:

Related Articles


Thursday Feb 05, 2015

Reminder: Upgrade Database 10.2.0.5 Before July 2015

E-Business Suite customers must ensure that their database remains on a level that is covered by Error Correction Support (ECS) -- i.e. while you can get new patches, Critical Patch Updates (CPU), and Patch Set Updates (PSU).  We've covered this in detail here:

The following Note lists Error Correction Support dates for all database patchsets for all database releases:

That Note shows that patching ends for the 11.1.0.7 Database patchset on July 31, 2015. There is additional fine print for Severity 1 fixes and other platforms -- see the Note for details.

All EBS customers should upgrade to a later patchset or database release before then.  As of today, options include upgrading to the 11.2.0.4 patchset or Database 12c 12.1.0.2.

Related Articles


Reminder: Upgrade Database 11.1.0.7 Before August 2015

E-Business Suite customers must ensure that their database remains on a level that is covered by Error Correction Support (ECS) -- i.e. while you can get new patches, Critical Patch Updates (CPU), and Patch Set Updates (PSU).  We've covered this in detail here:

The following Note lists Error Correction Support dates for all database patchsets for all database releases:

That Note shows that patching ends for the 11.1.0.7 Database patchset on August 31, 2015. There is additional fine print for Severity 1 fixes and other platforms -- see the Note for details.

All EBS customers should upgrade to a later patchset or database release before then.  As of today, options include upgrading to the 11.2.0.4 patchset or Database 12c 12.1.0.2.

Related Articles


Reminder: Upgrade Database 11.2.0.3 Before August 2015

E-Business Suite customers must ensure that their database remains on a level that is covered by Error Correction Support (ECS) -- i.e. while you can get new patches, Critical Patch Updates (CPU), and Patch Set Updates (PSU).  We've covered this in detail here:

The following Note lists Error Correction Support dates for all database patchsets for all database releases:

That Note shows that patching ends for the 11.2.0.3 Database patchset on August 27, 2015

All EBS customers should upgrade to a later patchset or database release before then.  As of today, options include upgrading to the 11.2.0.4 patchset or Database 12c 12.1.0.2.

Related Articles


Thursday Jan 22, 2015

Using SHA-2 Signed Certificates with EBS

Secure Hash Algorithms (SHA) are used for a variety of cryptographic purposes including signing of public key infrastructure (PKI) certificates (e.g., code signing cerificates and Secure Socket Layer (SSL) or Transport Layer Security (TLS) server certificates). Currently, the SHA family of functions include SHA-0, SHA-1, SHA-2 and SHA-3. This article and reference notes focus on the use of the SHA256 hash function of SHA-2 with Oracle E-Business Suite.

Why is SHA-2 important to you?

Industry standards for encryption algorithms are constantly under review. Many certificate authorities are recommending or mandating SHA-2 as the minumum signature algorithm for issuing certificates. The time frame for moving to SHA-2 varies depending upon the certificate authority that is used. The requirement for SHA-2 also impacts intermediate certificates which must also be SHA2 in order to chain back to the end-entity SHA-2 certificate issued. Root certificates are not impacted.

When does Oracle E-Business Suite use certificates?

1. HTTPS clients (outbound connections)
HTTPS client connections that originate from Oracle E-Business Suite. For HTTPS clients, you may need to apply product patches to use SHA-2 certificates. Currently, the following products have identified additional requirements to support SHA-2 for HTTPS clients:

  • XML Gateway
    Follow the instructions in the patch README and apply the following patch: 19909850
  • iProcurement
    Follow the instructions for iProcurement in My Oracle Support Note 1937220.1.

In addition to products that initiate outbound connections from java code on the application tier, the Oracle Database may also act as an HTTP client when the UTL_HTTP package is utilized. Some Oracle E-Business Suite products leverage UTL_HTTP for outbound HTTPS connections. You may also use UTL_HTTP for external integrations and customizations.

For the Oracle Database to utilize a PKI (including SHA-2 signed) certificate, SSL/TLS for outgoing connections database connections must be configured.  Our testing in Oracle E-Business Suite development has confirmed that UTL_HTTP is SHA-2 compliant as of Oracle Database 11.1.0.7 (we have not tested with earlier database versions).The steps for enabling and testing SSL/TLS configuration for the Oracle Database are documented in the following:

2. Server Side
In addition to client side (outbound connections), the Oracle E-Business Suite application tier utilizes PKI certificates for code signing by AD Jar Signing and for the (inbound) SSL/TLS termination point using the Oracle HTTP Server.

AD JAR Signing
During patching, Oracle E-Business Suite uses certificates to sign JARs that will be delivered to the browser. As of Java 1.5, Java and its utilities keytool and jarsigner supports SHA-2 certificates. SHA-2 certificates are certified for JAR signing for all versions of Oracle E-Business Suite (11i, 12.0, 12.1 and 12.2) and Java 1.5 and higher.

Oracle HTTP Server (inbound connections)
SHA-2 certificates are also used by the Oracle HTTP server that is delivered with the Oracle E-Business Suite Applications Technology. The requirements for SHA-2 for the Oracle HTTP Server vary per Oracle E-Business Suite version as follows:

  • Oracle E-Business Suite Release 12.2
    SHA-2 certificates are certified with the Oracle HTTP Server delivered with Oracle E-Business Suite 12.2. The wallet management tools that are shipped with EBS 12.2 generate Certificate Signing Requests (CSRs) signed using MD5. The following note has been updated with the steps necessary to create CSRs signed with other algorithms including SHA-2:
  • Oracle E-Business Suite Releases 12.0 and 12.1
    We are currently working on the certification of SHA-2 certificates with the Oracle HTTP Server for Oracle E-Business Suite Release 12.0 and 12.1. As an option while we are working on this certification, you may use an alternate technology (ie, a load balancer, reverse proxy, etc) that supports SHA-2 as the SSL/TLS termination point. Another alternative is to request that your certificate authority issue a SHA-1 certificate.

  • Oracle E-Business Suite Release 11i
    SHA-2 certificates are certified with Oracle E-Business Suite Release 11i when using mod_ssl.so OpenSSL library version 0.98za or later.  To get the minimum mod_ssl.sl library required for EBS 11i and SHA-2, you must apply the July 2014 CPU. Note: We always recommend that you apply the most current CPU available to your environment. You may refer to the following note for additional details:

Related Articles

References

Wednesday Jan 21, 2015

JRE 1.8.0_31 Certified with Oracle E-Business Suite

Java logo

Java Runtime Environment 1.8.0_31 (a.k.a. JRE 8u31-b13) and later updates on the JRE 8 codeline are now certified with Oracle E-Business Suite Release 11i, 12.0, 12.1, and 12.2 for Windows and Mac OS X 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.

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 11i:

For EBS 12.0, 12.1, 12.2

Known Issues

Form Focus Issue:  Clicking outside the frame during forms launch may cause a loss of focus when running with JRE 8. This can occur in all Oracle E-Business Suite releases.  A fix for this issue is currently being investigated, see the documentation below for additional information.

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 this 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) and 10.9 (Mavericks) desktops.  For details, see:

The certification of JRE 8 for Mac OS X 10.10 (Yosemite) desktops is planned.  

Oracle's Revenue Recognition rules prohibit us from discussing certification and release dates, but you're welcome to monitor or subscribe to this blog for updates.

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.

References

Related Articles
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. 


JRE 1.7.0_75 and 1.7.0_76 Certified with Oracle E-Business Suite

Java logo

Java Runtime Environment 1.7.0_75 (a.k.a. JRE 7u75-b13) and 1.7.0_76 (7u76-b13) and later updates on the JRE 7 codeline are now certified with Oracle E-Business Suite Release 11i and 12.0, 12.1, and 12.2 for Windows-based desktop clients.

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?

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 7.

  • CPU Release is JRE 1.7.0_75
  • PSU Release is JRE 1.7.0_76

It is recommended that Oracle E-Business Suite customers use the CPU release (JRE 1.7.0_75) and only upgrade to the PSU release (JRE 1.7.0_76) if they require a specific bug fix.  For further information and bug fix details see Java CPU and PSU Releases Explained.

There are currently no known issues in Oracle E-Business Suite that require the PSU release but it is certified for customers that may need to use it.

JRE 1.7.0_75  (7u75) is a CPU release. If you are running on the JRE 7 stream, it is strongly recommended to upgrade to this latest and therefore most secure version of the JRE 7 Plug-in.

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 7 are documented in these Notes:

For EBS 11i:

For EBS 12.0, 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:

Worried about the 'mismanaged session cookie' issue?

No need to worry -- it's fixed.  To recap: JRE releases 1.6.0_18 through 1.6.0_22 had issues with mismanaging session cookies that affected some users in some circumstances.

The fix for those issues was first included in JRE 1.6.0_23. These fixes will carry forward and continue to be fixed in all future JRE releases on the JRE 6 and 7 codelines.  In other words, if you wish to avoid the mismanaged session cookie issue, you should apply any release after JRE 1.6.0_22 on the JRE 6 codeline, and JRE 7u10 and later JRE 7 codeline updates.

JRE 7 End of Public Updates

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 Extended Support in April 2015.

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 this January 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.9 can run JRE 7 or 8 plug-ins.  See these articles:

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

Java JRE 1.6.0_91 Certified with Oracle E-Business Suite

Java logo

The latest Java Runtime Environment 1.6.0_91 (a.k.a. JRE 6u91-b13) and later updates on the JRE 6 codeline are now certified with Oracle E-Business Suite Release 11i and 12.x for Windows-based desktop clients.

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?

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 in this Java release?

JRE 1.6.0_91  (6u91-b13) is a CPU release. If you are running on the JRE 6 stream, it is strongly recommended that you upgrade to this latest version of the JRE 6 Plug-in.

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.

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.

Worried about the 'mismanaged session cookie' issue?

No need to worry -- it's fixed.  To recap: JRE releases 1.6.0_18 through 1.6.0_22 had issues with mismanaging session cookies that affected some users in some circumstances.

The fix for those issues was first included in JRE 1.6.0_23. These fixes will carry forward and continue to be fixed in all future JRE releases.  In other words, if you wish to avoid the mismanaged session cookie issue, you should apply any release after JRE 1.6.0_22.

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?

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

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.9 can run JRE 7 or 8 plug-ins.  See these articles:

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

Tuesday Jan 20, 2015

Critical Patch Update for January 2015 Now Available

The  Critical Patch Update (CPU) for January 2015 was released on January 20, 2015.  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.

Also, it is essential to review the Critical Patch Update supporting documentation referenced in the Advisory before applying patches, as this is where you can find important pertinent information.

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

The next four Critical Patch Update release dates are:

  • April 14, 2015
  • July 14, 2015
  • October 20, 2015
  • January 19, 2016
E-Business Suite Releases 11i and 12 Reference

Friday Jan 16, 2015

Internet Explorer 11 Certified with E-Business Suite 12.2 and 12.0

Microsoft IE logoMicrosoft Internet Explorer 11 is now certified as a desktop client browser for Oracle E-Business Suite Release 12.2 and 12.0.  This follows our previous certification of IE11 with EBS 12.1.  The certified desktop operating systems are:

  • Windows 7 Service Pack 1 (32-bit or 64-bit)
  • Windows 8.1 Update 1

Certified IE 11 Modes

Internet Explorer 11 can be used in "Desktop Mode" on Windows 8.1.  Running IE 11 from the "Modern" (Metro) Start Screen is not certified.

Due to display issues with certain FWK pages when using IE9 or IE10 we previously recommended running E-Business Suite using the browsers 'compatibility mode'.  These display issues have now been fixed for IE11-- you can now access your E-Business Suite 12.x environments without using 'compatibility mode' in IE 11.

 IE 11 includes an "Enterprise Mode" which can be used to emulated Internet Explorer 8 behaviour and provide compatibility with earlier browser standards.  You should not use "Enterprise Mode" with Oracle E-Business Suite.  EBS compatibility with IE 11 requires server-side patches. Enabling "Enterprise Mode" in IE 11 is not needed and will not resolve all compatibility issues.

EBS 12.2 Prerequisites

  • EBS 12.2.3 or later 12.2 updates
  • Java Plug-in JRE 1.6.0_03 (32-bit) or higher, or JRE 1.7.0_10 (32-bit) and higher
  • Java Plug-in JRE 1.6.0_32 (64-bit) or higher, or JRE 1.7.0_10 (64-bit) and higher

EBS 12.0 Prerequisites

  • EBS 12.0.6
  • Java Plug-in JRE 1.6.0_03 (32-bit) or higher, or JRE 1.7.0_10 (32-bit) and higher
  • Java Plug-in JRE 1.6.0_32 (64-bit) or higher, or JRE 1.7.0_10 (64-bit) and higher
JRE 6, 7, and 8 are certified with EBS

Java Runtime Environment (JRE) Versions 6, 7, and 8 are certified with EBS. 

There appears to be some inaccurate information lying about on the web that claims that JRE 1.7 is not certified with the E-Business Suite. 

This is incorrect. 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

You do not need to wait for a certification announcement before applying new JRE 1.6 or JRE 7 releases to your EBS users' desktops. 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.

"JInitiator version too low" errors

Some non-Oracle staff are claiming that "JInitiator version too low" errors confirm this incompatibility and lack of certification.

In fact, if you're getting a "JInitiator version too low" error, it means that you've missed applying the Forms patch required to enable JRE 1.7 compatibility. Simply apply that patch and your EBS environment is ready for JRE 1.7 clients.

Certifications with EBS 11i still pending

We plan to certify IE 11 with EBS 11i.  This certification us underway now and will be released soon.

If you're running EBS 11i, you must ensure that your mission-critical desktops remain on an earlier certified browsers until this certification is completed.  As of the time this article was published, certified browsers include IE 10 and Firefox ESR 31 for Windows desktops.

You can block automatic updates by using Microsoft's Internet Explorer 11 Blocker Toolkit:

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.    

References

Related Articles

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.

Wednesday Jan 14, 2015

Reminder: EBS 12.0 Extended Support Ends January 31, 2015

Extended Support for Oracle E-Business Suite 12.0 ends on January 31, 2015.  See:

Chart displaying EBS Premier and Extended Support dates

EBS 12.0 users should upgrade to EBS 12.1 or 12.2 as soon as possible. You might find this article useful:

What happens after Extended Support ends?

Sustaining Support for EBS 12.0 begins on February 1, 2015.  You can request diagnostic assistance for EBS 12.0 issues and download existing patches and documentation. Sustaining Support does not include:

  • New updates, fixes, security alerts, data fixes, and critical patch updates
  • New tax, legal, and regulatory updates
  • New upgrade scripts
  • Certification with new third-party products/versions
  • Certification with new Oracle products

For more specifics on Premier Support, Extended Support, and Sustaining Support, see:

Implications for EBS 12.0 users

You may need to freeze your desktop and server configurations while you upgrade to EBS 12.1 or 12.2. 

New versions of desktop components may not work with EBS 12.0.6. These include new releases of:

  • Windows
  • Mac OS X
  • Internet Explorer (IE)
  • Firefox
  • Safari
  • Office
  • Desktop-based Java Runtime Environment (JRE)  

New versions of server-based components may not work with EBS 12.0.6. 

These include new releases of:

  • Server-based operating systems (Linux, AIX, HP-UX, Solaris, etc.)
  • Oracle Database
  • Java JDK
  • Fusion Middleware components (Oracle HTTP Server, OC4J, Forms, etc.)

Related Articles

Friday Jan 09, 2015

EBS 12.1.3 Certified with Microsoft Windows Server 2012 R2

Microsoft Windows Server logoOracle E-Business Suite Release 12 (12.1.3) is now certified with Microsoft Windows Server 2012 R2 on both the application and database tiers through a certified migration of an existing Release 12 installation. Microsoft Windows Server 2012 R2 is a Windows x64 (64-bit) only operating system and is the latest Windows Server version.

Support of the E-Business Suite on this platform is achieved by a two-step process of migrating the Oracle Database first (as documented in the 11gR2 Database Tier Only Platform note), and then migrating the application tier using the process documented in the R12 Rapid Clone note. These steps and all requirements are outlined here:

The operating systems certified on this platform are:

  • Microsoft Windows Server 2012 R2 Standard
  • Microsoft Windows Server 2012 R2 Datacenter

Pending Certifications 

Certification for Rapid Install of Oracle E-Business Suite Release 12.2 on Microsoft Windows Server 2012 R2 is in progress and will be announced separately.

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

Where can I find more information?

Related Articles

Monday Jan 05, 2015

Enhance E-Business Suite Security By Switching to TLS

It seems fitting to start 2015 with a security-related blog post about Secure Socket Layer (SSL) and Transport Layer Security (TLS).  TLS is the successor to SSL. TLS, like SSL, is a protocol that encrypts traffic between applications and servers. TLS is based on SSL 3.0. TLS 1.0 is sometimes referred to as SSL 3.1. Going forward you will hear us talk more about TLS and less about SSL.

TLS is considered to be more secure than SSL.  All systems that use SSL 3.0 may be vulnerable to a design vulnerability in SSL’s handling of block cipher mode padding.  The Padding Oracle on Downgraded Legacy Encryption (POODLE) attack is one possible attack vector for web browsers and web servers.

Oracle E-Business Suite customers can migrate to TLS and mitigate the effects of POODLE attacks by following:

Happy 2015!

.Related Articles

References

Wednesday Dec 31, 2014

2014: A Year in Review for Oracle E-Business Suite

Happy New Year.  2014 was another big year for the Oracle E-Business Suite. 

Did you miss any of the most-important articles of the year?

Upgrading to EBS 12.2

Updates to EBS 12.2

Updates to EBS 12.1

Java

Important Technology Stack Updates

Virtualization

Maintaining and Extending EBS

Support Policies

Monday Dec 29, 2014

Quarterly EBS Upgrade Recommendations: December 2014 Edition

(16-Jan-2015 Update to recommendation number 5:  Removed 11i from 12.1.0.2 and added to 12.1.0.1.  Removed 12.2 from 12.1.0.1 and added to 12.1.0.2)

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 December 2014

  1. EBS 11i users should upgrade to 12.1.3 or 12.2.  Before upgrading, 11i users should be on the minimum 11i patching baseline.

  2. EBS 12.0 users should upgrade to 12.1.3 or 12.2.  Before upgrading, 12.0 users should be on the minimum 12.0 patching baseline.

  3. EBS 12.1 users should upgrade to 12.1.3 RP2 or 12.2.

  4. EBS 12.2 users should upgrade to 12.2.4 or the latest AD/TXK tools and StartCD 49.

  5. Oracle Database 10gR2, 11gR1, and 11gR2 users should upgrade to 12.1.0.1 (11i) or 12.1.0.2 (12.0/12.1, 12.2)

  6. EBS 11i and 12 users of Oracle Single Sign-On 10g users should migrate to OAM 11gR2 Patchset 2 11.1.2.2.0.

  7. Oracle Internet Directory 10g users should upgrade to Oracle Internet Directory 11g 11.1.1.7.

  8. Oracle Discoverer users should migrate to Oracle Business Intelligence Enterprise Edition (OBIEE), Oracle Business Intelligence Applications (OBIA), or Discoverer 11g 11.1.1.7.

  9. Oracle Portal 10g users should migrate to Oracle WebCenter 11g 11.1.1.7 or upgrade to Portal 11g 11.1.1.6.

  10. All Windows desktop users should migrate from JInitiator and older Java releases to JRE 1.6.0_85 or later 1.6 updates or JRE 1.7.0_72 or later 1.7 updates or JRE 1.8.0_25 or later 1.8 updates.

  11. All EBS 11i, 12.0, 12.1, and 12.2 users must sign their environment's JAR files now.

  12. All Firefox users should upgrade to Firefox Extended Support Release 31.

  13. All EBS 11i, 12.0, 12.1, 12.2 users should apply the latest Critical Patch Update.

  14. Windows XP and Office 2003 users should upgrade to later versions.

  15. All EBS customers on Exalogic and Exadata should follow the latest recommendations.

Related Articles

Tuesday Dec 23, 2014

Running E-Business Suite on Exalogic and Exadata

Exalogic serverPrior articles have noted that you can run the E-Business Suite on Oracle Engineered Systems such as Exalogic Elastic Cloud and Exadata Database Machine

What EBS combinations can you run on Exalogic and Exadata?

We certify E-Business Suite releases on operating systems and database releases (e.g. EBS 12.1.3 is certified on Database 12.1.0.2 on Linux 6 x86-64), not specific configurations of hardware such as Exadata or Exalogic.  This means that you can run the E-Business Suite on Exadata and Exalogic with any of the certified combinations listed in the Certifications database on My Oracle Support.

Srini Chavali, my colleague in the Exalogic division, has published a nice summary of all of the latest resources:

Srini gives an overview of the process for getting EBS onto these systems, discusses VM templates and Maximum Availability Architectures, and points to other useful best practices and reference documents. 

Related Articles

Thursday Dec 18, 2014

DB 12.1.0.1 Certified with EBS 11i & R12 on Linux on IBM System z

IBM LogoOracle Database 12c Release 1 (12.1.0.1) is now certified with Oracle E-Business Suite Release 11i, 12.0, and 12.1 on the following Linux on IBM System z operating systems as 'database tier only' platforms:

Release 11i (11.5.10.2 + ATG PF.H.delta.7 (RUP 7) or higher), Release 12.0 (12.0.6 or higher), Release 12.1 (12.1.3 or higher):

  • Red Hat Enterprise Linux (RHEL) version 5 (64-bit)
  • Red Hat Enterprise Linux (RHEL) version 6 (64-bit)
  • Novell SUSE Linux Enterprise Server (SLES) version 11 (64-bit)

This is a 'database tier only' or 'split tier configuration' certification where the application tier must be on a fully certified E-Business Suite platform (see My Oracle Support Certifications for more information). IBM's z systems fully support a mixed platform architecture with distributed Unix and Linux certified application tier servers for customers looking to run Oracle E-Business Suite on System z.

This announcement includes:

  • Oracle Database 12cR1 version 12.1.0.1
  • Oracle Database 12cR1 version 12.1.0.1 Real Application Clusters (RAC)
  • Transparent Data Encryption (TDE) Column Encryption using Oracle Database 12cR1 version 12.1.0.1
  • Transparent Data Encryption (TDE) Tablespace Encryption using Oracle Database 12cR1 version 12.1.0.1
  • Advanced Security Option (ASO)/Advanced Networking Option (ANO) with Oracle Database 12cR1 version 12.1.0.1
  • Export/Import Process for Oracle E-Business Suite Release 11i with Oracle Database 12cR1 version 12.1.0.1
  • Export/Import Process for Oracle E-Business Suite Release 12.0 or 12.1 with Oracle Database 12cR1 version 12.1.0.1

Pending Certifications

The following are not yet certified and will be announced on a later date once completed.

  • Oracle Multitenant 12cR1 version 12.1.0.1
  • Oracle Database Vault 12cR1 version 12.1.0.1
  • Transportable Database and Transportable Tablespaces Data Migration Processes

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.    

References

Please also review the platform-specific Oracle Database Installation Guides for operating system and other prerequisites.

Related Articles

Tuesday Dec 09, 2014

Database 12c 12.1.0.2 Certified With 12.1 On Oracle Solaris on x86-64

As a follow up to our earlier announcement, Oracle Database 12cR1 Version 12.1.0.2 is now certified with Oracle E-Business Suite Release 12 for 12.1 on the following additional platform:

Release 12.1 (12.1.3 and higher):

    Oracle Solaris on x86-64 (64-bit) (10, 11)

This is a 'database tier only' or 'split tier configuration' certification where the application tier must be on a fully certified E-Business Suite platform.

Data12.1.0.2 download screenshot

In addition, the Export/Import process for EBS release 12.0 or 12.1 with Oracle Database 12cR1 Version 12.1.0.2 is now certified.

Certification data in My Oracle Support (http://support.oracle.com) is being updated with this information - please review the documents below for all requirements and additional details:

Related Articles

Thursday Dec 04, 2014

JRE Support Ends Earlier than JDK Support

One of our Applications Technology Group architects recently drew my attention to an important change in Java support policies that I'd missed: support for client-based Java Runtime Environment (JRE) plug-ins now ends earlier than the support dates for server-based Java Development Kit (JDK) components.

Screenshot from Java Lifetime Support Policy document JDK JRE different dates

These dates are published here:

The client-side Java technology (Java Runtime Environment / JRE) is now referred to as Java SE Deployment Technology (Java Web Start & Java Plug-in technologies) 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:

Related Articles

Tuesday Dec 02, 2014

EBS VMs: Appliances, Templates, and Assemblies Explained

This article describes the different types of Oracle E-Business Suite virtual machine software packages available, and how they are appropriate for different situations.

The appliances, templates, and assemblies provided on the Oracle Software Delivery Cloud (https://edelivery.oracle.com/linux) all contain virtual machine images. These are intended for different purposes, but all allow you to install EBS rapidly and create an EBS virtual machine.

Here are some important terms related to Oracle’s VM offerings:

  • Oracle VM is Oracle's own server virtualization platform. An Oracle VM template is one media format -- the original media format -- used to deliver a virtual machine within the Oracle VM framework.
  • Oracle VirtualBox is Oracle's own desktop virtualization platform. An Oracle VM appliance uses an industry-standard media format to deliver a virtual machine on top of VirtualBox. Because appliances use an industry standard format, they can in principle be deployed on third party virtualization platforms, but Oracle does not test those platforms.
  • An Oracle VM Virtual Assembly is a format developed specifically for deployment using Enterprise Manager Cloud Control (EMCC). An assembly is powerful in that a single assembly contains multiple VM's (not just a single VM like an appliance or a template) as well as the logic to connect those VM's, allowing EMCC to install a multi-node system at the touch of a button. Customers who use Enterprise Manager and run Oracle VM can take advantage of these.
Note that Oracle VM Manager can now import Oracle VM appliances, so we have switched over to producing appliances wherever possible, giving a single set of virtual machine images that can be installed on a server, desktop or laptop. We do still produce VM templates for Exalogic (ex.: Oracle VM Templates For EBS 12.2.3 For Exalogic) because Enterprise Manager Operations Center (EMOC) currently only supports VM templates.

Summary of Usage

Virtual Appliances
  • Deploy an EBS VM on a desktop or laptop using Virtual Box
  • Deploy an EBS VM on a server using Oracle VM Manager
  • Manual setup required to add nodes and configure multi-node
VM Templates
  • Deploy an EBS VM on a server using Oracle VM Manager
  • Deploy an EBS VM on Exalogic using Enterprise Manager Operations Center
  • Manual setup required to add nodes and configure multi-node
Virtual Assemblies
  • Deploy EBS VM's on a server or servers using Oracle Enterprise Manager Cloud Control
  • Automated installation of single or multi-node

Available Releases

Virtual Appliances


Single Node Multi-Node MOS Doc ID
Oracle VM Virtual Appliances for Oracle E-Business Suite 12.2.4
VIS
PROD, VIS
1928303.1
Oracle VM Virtual Appliances for Oracle  E-Business Suite 12.2.3
VIS
PROD, VIS
1620448.1
Oracle VM Virtual Appliances  for Oracle E-Business Suite 12.1.3
VIS
PROD, VIS
1906691.1


VM Templates


Single Node Multi-Node MOS Doc ID

Oracle VM Templates for Oracle E-Business Suite 12.2.3 for Exalogic

n/a
PROD, VIS
1633952.1
Oracle VM Templates for Oracle E-Business Suite 12.2.2
n/a
PROD, VIS
1590941.1
Oracle VM Templates  for Oracle  E-Business Suite 12.1.3 for Exalogic
n/a
VIS
1499132.1


Virtual Assemblies


Single Node Multi-Node MOS Doc ID
Oracle Virtual Assemblies for Oracle E-Business Suite 12.2.3
PROD
PROD
1904928.1
Oracle Virtual Assemblies for Oracle E-Business Suite 12.1.3
PROD
PROD
1904928.1


Related Articles

Monday Dec 01, 2014

November 2014 Updates to AD and TXK for EBS 12.2

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, and have now made available a fifth 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 (November 2014 bundle fixes) at your earliest convenience:

Patch 20034256

Applying these on top of AD Delta 5 and TXK Delta 5 respectively will bring you to the recommended codelevel for AD and TXK:

  • AD Delta 5 (Patch 18283295) + November 2014 Bundle Fixes (Patch 20034256)
  • TXK Delta 5 (Patch 18288881) + November 2014 Bundle Fixes (Patch 20043910)

 You must always keep your AD and TXK codelevels synchronized.

Important: As well as providing additional fixes, the November 2014 bundle fixes include all the fixes provided in the October 2014 set. So if you have not yet applied the October set, you can just apply the November set instead.

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 release.

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 that product.

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 bundle fixes can be found in:

Related Articles

Wednesday Nov 26, 2014

Oracle EBS Adapter for Oracle SOA Suite 12c Now Available

Oracle E-Business Suite Adapter for Oracle SOA Suite 12c (12.1.3) is now available for use with the E-Business Suite.  Previous releases of this product were called Oracle Applications Adapter for Oracle SOA Suite.

Architecture diagram for EBS Adapter for SOA Suite

You can use the Oracle E-Business Suite Adapter for Oracle SOA Suite to integrate EBS 11i, 12.1, and 12.2 with external systems.  The EBS Adapter allows you to build bidirectional standards-based real-time integrations with the E-Business Suite.  The Adapter supports JCA and web service standards for creating service-oriented applications (SOA). 

What's new in this release?

  • Adapter configuration reports: You can now view Adapter configuration reports in Oracle Fusion Middleware Control. 
  • Flexfield support for Open Interface Tables:  In addition to its existing support for PL/SQL APIs, this release provides flexfield support for Open Interface Tables by displaying flexfield data and mapping if configured in Open Interface Tables at design and run time

References

Related Articles


Tuesday Nov 25, 2014

New 12.2 EBS Technology Stack Documentation Roadmap Available

Oracle E-Business Suite Release 12.2 includes many significant new features and some of them are updated frequently-enough that their main documentation is published via My Oracle Support Notes rather than the guides that accompany each major release. 

We have published a new My Oracle Support knowledge document to make the official EBS 12.2 Notes from ATG Development easier to find:

Document 1934915.1

The notes listed in this Oracle E-Business Suite Release 12.2 Technology Stack Documentation Roadmap (Note 1934915.1) apply either exclusively to Release 12.2, or to 12.2 and stated earlier releases.  This documentation roadmap will be updated every time the Applications Technology Group releases a new EBS 12.2-related Note.

What about earlier EBS releases?

We have published documentation roadmaps for EBS 11i and 12.0 / 12.1, as well.

References

  • Oracle E-Business Suite Release Notes, Release 12.2 (Note 1320300.1)

Friday Nov 21, 2014

Testing Your EBS Environment After Database Upgrades

Customers often ask, "What should I test after I upgrade my EBS database?" Your environment is, by definition, unique to you, with your own architectural configurations, setup data, and customizations.  You should always concentrate your testing efforts on the areas that may differ from our generic EBS tests.  Until now, our generic common-sense answer has always been, "Test what is important to your business."  

Our Quality Assurance group in EBS Development has just published some guidance on the things that you might consider adding to your post-upgrade test plans:

They discuss things such as memory-intensive concurrent requests, compliance with new standards for initialization parameters, custom workflows, and more.

Your feedback is welcome.  I'll make sure that the Note's authors are notified if you drop me an email or post a comment here. 

Related Articles

Wednesday Nov 19, 2014

EBS 12.0 & 12.1 DB Migration Using 12cR1 Transportable Tablespaces Now Certified


Database migration across platforms of different "endian" (byte ordering) formats using the Transportable Tablespaces (TTS) process is now certified for Oracle E-Business Suite Release R12 (12.0.6, 12.1.3) with Oracle Database 12c Release 1 (12.1.0). Migration between different platforms of the same "endian" format with 12c can be accomplished using export/import (datapump) utilities. 

This certification requires that the source database be 11gR2 (11.2.0.3 or higher) and the target database be 12cR1 (12.1.0.1 or higher).  

This migration process requires a patch delivered by our EBS Platform Engineering team that is 'Controlled', i.e. it requires a password obtainable through Oracle Support. We released the required patch in this manner to monitor customer issues and to gauge uptake.

The "endian-ness" of platforms can be checked by querying the view V$TRANSPORTABLE_PLATFORM using sqlplus (connected as sysdba):

        SQL> select platform_name, endian_format from v$transportable_platform;

Here's a list of relevant platforms certified for the EBS R12 with 12cR1 on the database tier:

 

Big Endian Platforms
Little Endian Platforms
Oracle Solaris on SPARC
Linux x86-64
HP-UX Itanium
Oracle Solaris on x86-64
IBM AIX on POWER Systems
MS Windows x64

The use of Transportable Tablespaces can greatly speed up the migration of the data portion of the database - it does not affect metadata which must still be migrated using export/import.

We recommend that users initially perform a test migration with export/import on their database with the 'metrics=y' parameter to find out the relative size of data vs metadata in their database and to have a basis to compare any gains in timing. Generally speaking, the larger the relative size of data (as compared to metadata), the more likely it would be that TTS is suitable as a migration process to reduce downtime.

Pending Certifications

Testing with 12cR1 as the source is still pending.

Full transportable export/import, a new feature in 12c to move an entire database, is not certified for use with E-Business Suite databases yet. 

Transportable Database (TDB), a migration process for platforms of the same "endian" format, is also a pending 12cR1 certification exercise. 

References

 Related Articles


Friday Nov 14, 2014

Java JRE 8 Certified with Oracle E-Business Suite

Java logo

[Dec. 3, 2014 Update: JRE support dates are not the same as JDK support dates any longer.  Corrected support dates for JRE 6, 7, and 8.]

Java Runtime Environment 1.8.0_25 (a.k.a. JRE 8u25-b18) and later updates on the JRE 8 codeline are now certified with Oracle E-Business Suite Release 11i, 12.0, 12.1, and 12.2 for Windows and Mac OS X 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.

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 11i:

For EBS 12.0, 12.1, 12.2

Known Issues

Form Focus Issue:  Clicking outside the frame during forms launch may cause a loss of focus when running with JRE 8. This can occur in all Oracle E-Business Suite releases.  A fix for this issue is currently being investigated, see the documentation below for additional information.

Availability of Server-Side Patches:  This certification requires patches to be applied to EBS 11i, 12.0, 12.1, and 12.2 servers.  Patches for 12.0 and 12.1 are available for:

  • Linux x86 (Oracle Linux 4, 5, 6; Red Hat Enterprise Linux 4, 5, 6)
  • Linux x86-64 (Oracle Linux 4, 5, 6; Red Hat Enterprise Linux 4, 5, 6; SLES 10,11) 
  • Oracle Solaris on SPARC (64-bit)(10, 11)

Patches for other server operating systems are pending. You can monitor the documentation for updates on platform availability.

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.

    Enabling the JRE Auto-Update feature on desktops with JRE 7 installed will only apply JRE 7 updates today. 

    In the future, enabling Auto-Update will upgrade JRE 7 to JRE 8.  For details, see:

    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) and 10.9 (Mavericks) desktops.  For details, see:

    The certification of JRE 8 for Mac OS X 10.10 (Yosemite) desktops is planned.  

    Oracle's Revenue Recognition rules prohibit us from discussing certification and release dates, but you're welcome to monitor or subscribe to this blog for updates.

    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.

    References

    Related Articles
    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. 


    Thursday Nov 13, 2014

    EBS 12.2.4 OA Extensions for Jdeveloper 10g Now Available

    When 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.4.  For details, see:

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

    Related Articles

    Wednesday Nov 12, 2014

    New Critical Patches Added to EBS 12.2.3 and R12.2.4 Release Notes

    Based on customer feedback, we continue to release updates to core EBS 12.2 components. The latest such updates consist of a set of critical patches that significantly improve the performance of connection handling, principally resolving issues where connections might not be correctly released for return to the data source connection pool.

    There are two patches for Release 12.2.3, and three for Release 12.2.4. We strongly advise all 12.2.3 and 12.2.4 customers to apply the respective patches.

    Example Download

    The patches are documented in the associated release notes, as described below.

    Release 12.2.3 Customers

    Refer to Section 7: Apply Additional Critical Patches of Oracle E-Business Suite Release 12.2.3 Readme (Note 1586214.1).

    Release 12.2.4 Customers

    • Patch 19494816 - Oracle Application Object Library
    • Patch 19807163 - Oracle Applications Manager
    • Patch 19858552 - Oracle Application Framework

    Refer to Section 8: Apply Additional Critical Patches of Oracle E-Business Suite Release 12.2.4 Readme (Note 1617458.1).

    Related Articles

    Friday Oct 24, 2014

    New OA Framework 12.1 Release Update Pack 4 Now Available

    Web-based content in Oracle E-Business Suite 12 runs on the Oracle Application Framework (OAF or "OA Framework") user interface libraries and infrastructure. 

    A new consolidated Oracle Application Framework patchset is now available for EBS 12.1:

    OAF 12.1 RUP 4 patch 18936791 screenshot


    Who Should Apply This Patch?

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

    What's New in this Patch?

    In addition to the fixes listed below, this patch contains updates required to support Microsoft Internet Explorer 11 (IE 11) and Google Chrome browsers. 

    Bugs fixed in this patch:
    • Bug 10007122 FRM-41058 ERROR OCCURS WITH CTRL+E KEYS WHEN THE CURSOR FOCUS IS ON THE BUTTON.
    • Bug 10040856 R12.0.X PREREQ PATCH FOR FNDFILE.DRV
    • Bug 10044347 IMAGE PATCH FOR OOW BUILD2
    • Bug 10057139 GSI: QUERY IN FND_GLOBAL CAUSES HIGH CPU/NODE CRASH DUE TO MUTEX WAIT
    • Bug 10078872 1OFF:10057139:GSI: QUERY IN FND_GLOBAL CAUSES HIGH CPU/NODE CRASH DUE TO MUTEX W
    • Bug 10109713 THE CURRENT RESPONSIBILITY CONTEXT HAS BEEN SWITCHED TO: IN WEBCENTER WSRP
    • Bug 10119166 PREVIOUS USERS RESPONSIBILITIES ARE SHOW TO NEW USER
    • Bug 10177414 RESP CONTEXT CHANGE SETS FND_GLOBAL.ORG_ID = -1
    • Bug 10192670 12.1.4:10192626 FORWARD PORT: BI 3.1.1.11 :GRAPH IS NOT WORKING ON 64 BIT LINUX
    • Bug 10196565 10112858 FORWARD PORT: VO SUBSTITUTION DISPLAY AFTER 'DISABLE SELF-SERVICE PERSO
    This patch also includes fixes included in the Oracle Application Framework Release 12.1.3 Consolidated Fixes V.2, Patch 15880118, and the Oracle Application Framework Release 12.1.3 Consolidated Fixes V.1, Patch 11894708:
    • Few rows are missing while exporting data from a table.
    • NoDefException when user selects a value from Look Ahead LOV
    • Segment values are cleared when a value is entered in a segment.
    • User is able to login and see the previous users list of responsibilities on the same PC
    • Graphs not rendering properly in Linux Machines
    • Insufficient privileges' issue encountered while doing forward to Embedded mode URL
    • NullPointerException encountered in OASlideMenuUtil when attempting to create commercial surrogate quote.
    • Segments not aligned to the parent segments when flex bean is added under message component layout.
    • NullPointer Exception thrown in AdvancedTable pages when the Accessibility mode is set to Screen Reader Optimized.
    • Key flexfield segments are blanked out or populated with incorrect values.
    • LOV not working in Screen Reader Optimized accessibility mode.
    • "Portlet Not Available' error in E-Business Suite Portlets integrated with WebCenter 11g.
    • Intermittent FND_NO_DATABASE_CONNECTION error observed in Configurable Home Page.
    • Invalid date error shown when attempting to enter a Daylight Saving Time (DST) change date.
    • Support to retrieve the Page Name through Javascript.
    • Ability to display errors associated with the context segment at attribute level also.
    • Support to export file as .tsv when FND_EXPORT_MIME_TYPE is set to "text/tab-separated-values".
    • Support for enabling sorting in the classic table columns that are added under a layout.
    • Serbian language support in OA Framework. This is a common fix for both Latin Serbian script and Cyrillic Serbian script.
    • Support for enhanced Popup indicators.
    • Bug 10192670 - 12.1.4:10192626 FORWARD PORT: BI 3.1.1.11 :GRAPH IS NOT WORKING ON 64 BIT LINUX
    • Bug 10285481 - GOING TO SOURCING HOME PAGE FROM FAVOURITES, CREATING A QUOTE CAUSING EXCEPTION
    • Bug 10385406 - CLASSCASTEXCEPTION OCCURED WHEN ADDING OAHEADERBEAN AS 1ST CHILD TO OAPAGELAYBEAN
    • Bug 10390503 - EBS 12.1.3 EXPORT TXT MIME TYPE CANNOT BE MAPPED FOR EXCEL
    • Bug 10435049 - PEOPLE GROUP SEGMENTS BLANKED DURING UPDATE WHEN THOSE SEGMENTS NOT DISPLAYED
    • Bug 11832737 - FORWARD PORT OF 9908921 TO 12.1.3
    • Bug 11891959 - FORWARD PORT OF BUG 9614874 TO 12.1.3
    • Bug 7369074 FWK:APPENDING OF IMAGE NOT WORKING FOR READONLY MESSAGETEXTINPUT
    • Bug 9527712 FWK:FNDLOVCHOICEVALUE VO CAUSING SQL PARSE ERROR: INVALID NUMBER
    • Bug 9773527 FWK:WHEN USING IE8 LOV WINDOW DOES NOT GET FOCUS
    • Bug 10335521 FWK:THE APPLICATIONS BACKGROUND TURNS COMPLETELY BLUE INTERMITTENTLY
    • Bug 10435049 FWK:PEOPLE GROUP SEGMENTS BLANKED DURING UPDATE WHEN THOSE SEGMENTS NOT DISPLAYED
    • Bug 11781531 FWK:NOT ABLE TO ADD HTTPS URL TO FAVORITES LINK IN 12.1.2. HTTP IS PRE-PENDED TO URL
    • Bug 11856365 FWK:CAN NOT OPEN FAVORITES LINKS IN NEW WINDOW FROM PREFERENCES PAGE
    • Bug 11879499 FWK:CREATION_DATE AND LAST_UPDATE_DATE ARE NOT CORRECT
    • Bug 11924872 FWK:EMPTY SUB MENUS IN THE NEW TREE MODE NAVIGATOR ON HOMEPAGE (12.1.3)
    • Bug 12350371 FWK:UNABLE TO SEE LOGINPAGE PROBLEM 12.1.3
    • Bug 12424716 FWK:SAVE RESPONSIBILITY CONTEXT WHEN CREATING FAVORITES
    • Bug 12661140 FWK:12.1.3 :FAVORITES ADDED USING 'ADD TO FAVORITE' LOOSES MENU CONTEXT INFORMATION
    • Bug 12763903 FWK:Move to top and bottom icon titles in Navigator and Favorite dropdown should be
    • Bug 12814546 FWK:SYMANTEC ICAP CLIENT ALWAYS THROWS JAVA.LANG.STRINGINDEXOUTOFBOUNDSEXCEPTION
    • Bug 12820394 FWK:MDS QUERY - PERFORMANCE ISSUE
    • Bug 12829410 FWK:INCORRECT REQUISITIONS SHOWN WHEN USING OA FAVORITES
    • Bug 13028359 FWK:VIRUS SCAN DOES NOT KICK IN AFTER THE ATTACHMENTS ARE ADDED
    • Bug 13033466 FWK:MOZILLA : COPY PASTING AND TYPING BEHAVE DIFFERENT IN RTE
    • Bug 13033815 FWK:AFTER APPLYING PATCHES :12654106 AND 11894708, TEXT STYLE CHANGED IN POPUPS
    • Bug 13038333 FWK:RO SEGEMENTS WHEN DEFAULTED ARE NOT STORING THE VALUES ON SUBMIT
    • Bug 13109125 FWK:ALT+TAB TO TOGGLE IN AND OUT OF APPS CAUSING O AND N TO ACTIVATE SLIDEMENU
    • Bug 13243104 FWK:ISSUE WITH EXCEL DRILLDOWN
    • Bug 13322060 FWK:PLANNING- FORECAST SCHEDULE LINK FAILS WITH JAVA ERROR MESSAGE
    • Bug 13340173 FWK:QUANTITY FIELD DOES NOT VALIDATE DECIMAL SEPARATOR
    • Bug 13402264 FWK:UNABLE TO CREATE QUERY CRITERIA MAP IN PERSONALIZATION
    • Bug 13549105 FWK:NEED FORWARD PORT PATCH FOR BUGS 13108282 AND 13373481 IN 12.1.3
    • Bug 13550248 FWK:YOU ARE TRYING TO ACCESS A PAGE THAT IS NO LONGER ACTIVE
    • Bug 13555434 FWK:CANNOT IMPORT PERSONALIZATIONS USING FUNCTIONAL ADMINISTRATOR
    • Bug 13626261 FWK:POPUP THROWS EXCEPTION WHEN CHANGING RESPONSIBILITY IN CONTEXT SWITCHER
    • Bug 13691585 FWK:ENTITY CACHE NOT HONORED WHEN EO ACCESSED VIA AO
    • Bug 13710707 FWK:($RO$) SUFFIX MAKES SEGMENT VALUES DISAPPEAR IN KFF LOV WINDOW RESULTS TABLE, AV
    • Bug 13737406 FWK:HIJRAH DATE FORMAT ISSUE WHEN A DATE VALUE IS GETTING DEFAULTED
    • Bug 13738942 FWK:SUPPORT OPENING OF LOV WINDOW WHEN EXACT MATCH IS ALSO A PARTIAL MATCH
    • Bug 13822452 FWK:CONNECTION LOCKED IN OANAVIGATEPORTLETAM AFTER LOGIN WITH CONFIGURABLE HOME PAGE
    • Bug 13915163 FWK:RESPONSIBILITY ID NOT VISIBLE WHILE PERSONALIZING THROUGH FUNCTIONAL ADMINISTART
    • Bug 13919206 FWK:NEW BASE-DESKTOP.XSS CHANGES OAF DESIGN DUE TO 12350371
    • Bug 14071624 FWK:START PAGE PROFILE/PREFERENCES GETTING RESET
    • Bug 14343026 FWK:AM LEAK IN ICXFAVORITESAM AND OANAVIGATEPORTLETAM LEADING TO JDBC CONNECT LEAKS
    • Bug 14345705 FWK:THE NUMBER OF ERROR MESSAGE STACKED IN ARRAYLIST IS RESET FROM 10TH IN OAF
    • Bug 14365312 FWK:PROJECT INFORMATION NOT GETING SAVED IN IPROC
    • Bug 14467324 FWK:OADESCRIPTIVEFLEXBEAN REFERS INCORRECT SEGMENT LIST CORRESPONDING TO THE CONTEXT
    • Bug 14644892 FWK:7505198 - PERFORMANCE ISSUE WHILE ENTERING CHARGE ACCOUNT IN REQUISITION PAGE IN
    • Bug 14682009 FWK:HIGH DATA (HTML) TRANSFER OVER NETWORK ON PAGE RENDERING AND PPR

    Related Articles


    About

    Search

    Categories
    Archives
    « August 2015
    SunMonTueWedThuFriSat
          
    1
    2
    3
    4
    5
    6
    7
    8
    9
    10
    11
    12
    13
    14
    15
    16
    17
    18
    19
    20
    21
    22
    23
    24
    25
    26
    27
    28
    29
    30
    31
         
    Today