Warning: E-Business Suite Issues with Sun JRE 1.6.0_18
Posted
by Steven Chan
on Oracle Blogs
See other posts from Oracle Blogs
or by Steven Chan
Published on Mon, 22 Mar 2010 10:05:43 -0800
Indexed on
2010/03/22
19:11 UTC
Read the original article
Hit count: 548
Filed under:
Error when finding categories...
Users need a Java client to run the Forms-based content in Oracle E-Business Suite. With Oracle JInitiator 1.3 out of Premier Support as of July 2009, Apps users must run the native Sun Java Runtime Engine (JRE) to access this content.
In early 2008 we relaxed our certification and support policy for the use of the native Sun JRE clients with the E-Business Suite. The policy reflected a switch from certifying specific JRE versions for the E-Business Suite to specifying minimum versions, instead. This permits E-Business Suite users to run any JRE release above following minimum certified levels, even later ones that Oracle hasn't explicitly tested with the E-Business Suite:
Known E-Business Suite Issues with JRE 1.6.0_18
We test every new JRE release with both E-Business Suite 11i and 12. We have identified a number of issues with JRE 1.6.0_18. If you haven't already upgraded your end-users to JRE 1.6.0_18, we recommend that you to keep them on a prior JRE release such as 1.6.0_17 (6u17).
In early 2008 we relaxed our certification and support policy for the use of the native Sun JRE clients with the E-Business Suite. The policy reflected a switch from certifying specific JRE versions for the E-Business Suite to specifying minimum versions, instead. This permits E-Business Suite users to run any JRE release above following minimum certified levels, even later ones that Oracle hasn't explicitly tested with the E-Business Suite:
- JRE 1.5.0_13 and higher
- JRE 1.6.0_03 and higher
Known E-Business Suite Issues with JRE 1.6.0_18
We test every new JRE release with both E-Business Suite 11i and 12. We have identified a number of issues with JRE 1.6.0_18. If you haven't already upgraded your end-users to JRE 1.6.0_18, we recommend that you to keep them on a prior JRE release such as 1.6.0_17 (6u17).
© Oracle Blogs or respective owner