This is a discussion on jdk version - oracle 9i R2 windows within the Oracle Database forums, part of the Database Server Software category; --> Hi, I would like to know if there is a way to make only use of JDK 1.3.1 in ...
| |||||||
| FAQ | Members List | Calendar | Search | Today's Posts | Mark Forums Read |
| ||||
| Hi, I would like to know if there is a way to make only use of JDK 1.3.1 in Oracle 9i R2 for windows. For instance, OEM keeps picking up the 1.1.8 (jrew.exe), despite jre\1.3.1 is first in the path. Any info most appreciated, Eric |
| |||
| eric wrote: > > I would like to know if there is a way to make only use of JDK 1.3.1 in > Oracle 9i R2 for windows. > For instance, OEM keeps picking up the 1.1.8 (jrew.exe), despite jre\1.3.1 > is first in the path. > > Any info most appreciated, > > Eric Curious - are you concerned about the OEM operation or some of your own stuff? (As I understand it, OEM requires 1.1.8 to run properly, so attempting to override that might not be a good idea.) |
| |||
| "Hans Forbrich" <forbrich@yahoo.net> a écrit dans le message de news:KuGEc.58464$E84.18961@edtnps89... > eric wrote: > > > > > I would like to know if there is a way to make only use of JDK 1.3.1 in > > Oracle 9i R2 for windows. > > For instance, OEM keeps picking up the 1.1.8 (jrew.exe), despite jre\1.3.1 > > is first in the path. > > > > Any info most appreciated, > > > > Eric > > Curious - are you concerned about the OEM operation or some of your own > stuff? > > (As I understand it, OEM requires 1.1.8 to run properly, so attempting to > override that might not be a good idea.) > I think 1.3.1 brings more stability, and besides, one great "benefit" of Java besides its multi-platform support is that there comes one version for every product you install. But why does Oracle install 2 and uses the now obsolete 1.1.8, not supported by Sun if I am not mistaken ? I would have espected some flags to be able to use JDK1.3.1 for OEM. I tried to remove the 1.1.8 with UI, seemed to be possible, but then I got many dependencies that made this impossible. Maybe can you give me some reasons ? Eric |
| |||
| eric wrote: > > Maybe can you give me some reasons ? Regardless what you may think or believe, Oracle has tested OEM using 1.1.8 and is apparently satisfied enough with the stability to provide support. So - my answer is "Probably because that is the one they support." As far as I can tell, the newer versions of OEM use newer versions of the JDK. ANd they install the newer JDK for reasons other than OEM. (I am personally very pleased when an organization locks in all the components to a set that is known to work, and provides appropriate patches on that set. Otherwise we'd end up with sonething similar to the DLL anarchy we enjoy in the Windows world.) I still don't understand why you want to change to one that is not proven to work. Or, another way of asking that - Why do you think you understand Oracle's OEM-JDK requirements better than Oracle does? |
| |||
| "Hans Forbrich" <forbrich@yahoo.net> a écrit dans le message de news > eric wrote: > > > > > Maybe can you give me some reasons ? > > Regardless what you may think or believe, Oracle has tested OEM using 1.1.8 > and is apparently satisfied enough with the stability to provide support. The reason I asked is after installing 9iR2, and playing 5 minutes with OEM, I noticed in the task manager I had 2 jrew.exe. I closed OEM, and killed the remaining jrew.exe > > So - my answer is "Probably because that is the one they support." > > As far as I can tell, the newer versions of OEM use newer versions of the > JDK. ANd they install the newer JDK for reasons other than OEM. Yeah, absolutely, we get 1.3.1 and 1.1.8 at install time, and if I understand your comment, the newer versions of OEM use 1.3.1, but that was not due to the necessity to modify OEM to use 1.3.1 :-). And if OEM were very stable with 1.1.8, why not for the other Oracle components. I'm not a pusher for using absolutely the last version, but it was a surprise to see such a discrepancy between the components. > > (I am personally very pleased when an organization locks in all the > components to a set that is known to work, and provides appropriate patches > on that set. Otherwise we'd end up with sonething similar to the DLL > anarchy we enjoy in the Windows world.) > I still don't understand why you want to change to one that is not proven to > work. Or, another way of asking that - Why do you think you understand > Oracle's OEM-JDK requirements better than Oracle does? > Oracle installs a 1.1.8, so let be satisfied with that and do not ask why .... So far, the "master in the world" for Java remains SUN :-) And Sun does not support anymore 1.1.8 ... so my question... this JDK-OEM issue seems pretty hot for Oracle staff, isn't it ? |
| ||||
| eric wrote: > Oracle installs a 1.1.8, so let be satisfied with that and do not ask why > ... So far, the "master in the world" for Java remains SUN :-) And Sun > does not support anymore 1.1.8 ... so my question... this JDK-OEM issue > seems pretty hot for Oracle staff, isn't it ? The way I understand it ... Oracle installs a specific version of JRE with a specific version of it's product. They support that combination. Then, at a later date, when SUN releases an upgrade, Oracle supports THAT version of the JDK with _subsequent_ versions of Oracle's product. I do not understand why you think Oracle should be forced to test an older version of their product just because SUN has released a newer environment. Especially when a newer version of Oracle's product is up to date with SUN. |