Wednesday Aug 15, 2012

Java JRE 1.6.0_34 Certified with Oracle E-Business Suite

Java logoThe latest Java Runtime Environment 1.6.0_34 (a.k.a. JRE 6u34-b04) is now certified with Oracle E-Business Suite Release 11i and 12 desktop clients.  

What's new in Java 1.6.0_34?

See the 1.6.0_34 Update Release Notes for details about what has changed in this release.  This release is available for download from the usual Sun channels and through the 'Java Automatic Update' mechanism.

32-bit and 64-bit versions certified

This certification includes both the 32-bit and 64-bit JRE versions.

32-bit JREs are certified on:

  • Windows XP Service Pack 3 (SP3)
  • Windows Vista Service Pack 1 (SP1) and Service Pack 2 (SP2)
  • Windows 7 and Windows 7 Service Pack 1 (SP1)

64-bit JREs are certified only on 64-bit versions of Windows 7 and Windows 7 Service Pack 1 (SP1).

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.

All JRE 1.6 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 1.6 codeline.  We test all new JRE 1.6 releases in parallel with the JRE development process, so all new JRE 1.6 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 1.6 releases to your EBS users' desktops.


For important guidance about the impact of the JRE Auto Update feature on JRE 1.6 desktops, see:


Related Articles

Five Errors Customers Make When Upgrading E-Business Suite 12 (Part 5)

This is the fifth in a series of articles about common technical myths or misunderstandings about the E-Business Suite. Other articles have covered installations, cloning, patching, migrations, and maintenance. This article discusses upgrading. 

Each article is absolutely not definitive and I’d be interested in comments from readers who think there are other misconceptions about the day to day maintenance and upgrade of a typical E-Business Suite environment.

COMMON ERROR #1: Believing that DBUA does not work for Apps databases.

ORACLE’S RECOMMENDATION: Many DBAs still like to perform database upgrades manually using Oracle-provided scripts as they feel it gives them more control of the upgrade process. For the rest of us, DBUA is an excellent tool that greatly simplifies the upgrade process and which should reduce your upgrade time. E-Business Suite database upgrade documentation now assumes (but does not mandate) that you will use DBUA and documentation will be written accordingly. Raise a Service Request if you believe you have an issue where DBUA fails and the manual process is required instead.

COMMON ERROR #2: Assuming that only one test upgrade is needed before the production upgrade.

ORACLE’S RECOMMENDATION: Oracle advise a minimum of three completely successful tests of any upgrade or maintenance downtime before your production upgrade.

COMMON ERROR #3: Using generic documentation instead of the E-Business Suite versions.

ORACLE’S RECOMMENDATION: As an example, if you need to upgrade your database do not just refer to the standard database upgrade manuals. The E-Business Suite Development Team have created documentation specifically for upgrading the E-Business Suite technology stack to supplement generic documentation. Follow these supplemental documents. They are well written, thoroughly tested and will make your upgrade a success.

COMMON ERROR #4: Skipping new products included in Release Update Packs (RUPs) because there are no plans to use that product.

ORACLE’S RECOMMENDATION: When instructed to add new products to your database as part of a RUP you must always add those products. These products will later be patched and updated by this or later RUPs and if the products are not present then the patches will fail.

COMMON ERROR #5: Manually copying files between different E-Business Suite environments.

ORACLE’S RECOMMENDATION: New or replacement files should only be introduced to your system by patching, scheduled upgrades or other documented methods. Manually copying files between systems can cause mismatches between files in the APPL_TOP and their corresponding entries in database AD tables. This could cause patching issues later.

Related Articles



« August 2012 »