For appeals, questions and feedback about Oracle Forums, please email oracle-forums-moderators_us@oracle.com. Technical questions should be asked in the appropriate category. Thank you!
Interested in getting your voice heard by members of the Developer Marketing team at Oracle? Check out this post for AppDev or this post for AI focus group information.
I face a situation on the jdbc driver and jdk version which are not certified with Oracle and I concern about I can not get any support on it
How about the compatibility between JDK and ojdbc driver version?
Thanks
You can get support from Oracle on all Oracle products via your MOS account.
And how about the compatibility between JDK and ojdbc driver version?
The public info about that is available on Oracle's JDBC FAQ page
Oracle JDBC Frequently Asked Questions
See the section about 'release specific' issues
Bullet #3 covers JDK versions.
If you have additional questions about those links/faqs please address them to Oracle. They are the ONLY ones that can answer them definitively.
Thanks. Would you mind to share some knowledge about why JDK7 and JDK8 are supported in 11.2.0.3 and 11.2.0.4 jdbc driver version only?
As I have noticed that the jdbc file ojdbc6.jar can be compatible with JDK 6, JDK 7, and JDK 8
(Note: JDK7 and JDK8 are supported in 11.2.0.3 and 11.2.0.4 only)
1236438 wrote:Thanks. Would you mind to share some knowledge about why JDK7 and JDK8 are supported in 11.2.0.3 and 11.2.0.4 jdbc driver version only?As I have noticed that the jdbc file ojdbc6.jar can be compatible with JDK 6, JDK 7, and JDK 8 (Note: JDK7 and JDK8 are supported in 11.2.0.3 and 11.2.0.4 only)
1236438 wrote:
This rules out JDK7/8 support for 11.2.0.1 or anything earlier, ie if it is not 11.2.0.3/4
New versions of software are new because either:
1. they introduce NEW functionality that didn't exist before
2. they fix bugs that DID exist before
So when new JDK versions (e.g. jdk7 an jdk8) are released then will include things that the current/previous jdbc drivers either
1. can't work with because the functionality is new so didn't exist when the driver was released
2. can't work with anymore because a fixed bug breaks the code the driver uses
3. won't work the same way with because a fixed bug causes the jdk code to work differently which causes the jdbc code to work differently.
That 'not supported' means that Oracle will NOT provide support if you use that combination and run into problems. It does NOT necessarily mean the jdbc driver won't work properly for certain functionality.
So for basic connections and basic queries the older jdbc driver may work just fine. But if it doesn't you are on your own because Oracle won't support that combination.
1. you own a new car - still under warranty
2. you decide to put a souped-up 4-barrel carburetor in it to impress your friends
3. the manufacturer tells you the carburetor you want to add is 'not supported' and voids your warranty
The carburetor may very well work just fine with no impact on your engine. Or it could cause unforeseen problems because the manufacturer hasn't tested that combination.
If you have engine trouble and take your car to the dealer you will find your warranty is void because you used an unsupported component.
If you don't care about voiding your warranty and are comfortable taking the risk go ahead and install your new carburetor.
If you want the dealer to fix problems under the warranty then don't use unauthorized components.
Same with JDK/JDBC/DB versions - if you want support from Oracle use authorized/supported combinations.
If you don't care about support or potential problems use any combo you want.
rp0428 wrote:1236438 wrote:Thanks. Would you mind to share some knowledge about why JDK7 and JDK8 are supported in 11.2.0.3 and 11.2.0.4 jdbc driver version only?As I have noticed that the jdbc file ojdbc6.jar can be compatible with JDK 6, JDK 7, and JDK 8 (Note: JDK7 and JDK8 are supported in 11.2.0.3 and 11.2.0.4 only)New versions of software are new because either:1. they introduce NEW functionality that didn't exist before2. they fix bugs that DID exist beforeSo when new JDK versions (e.g. jdk7 an jdk8) are released then will include things that the current/previous jdbc drivers either1. can't work with because the functionality is new so didn't exist when the driver was released2. can't work with anymore because a fixed bug breaks the code the driver uses3. won't work the same way with because a fixed bug causes the jdk code to work differently which causes the jdbc code to work differently.That 'not supported' means that Oracle will NOT provide support if you use that combination and run into problems. It does NOT necessarily mean the jdbc driver won't work properly for certain functionality.So for basic connections and basic queries the older jdbc driver may work just fine. But if it doesn't you are on your own because Oracle won't support that combination.1. you own a new car - still under warranty2. you decide to put a souped-up 4-barrel carburetor in it to impress your friends3. the manufacturer tells you the carburetor you want to add is 'not supported' and voids your warrantyThe carburetor may very well work just fine with no impact on your engine. Or it could cause unforeseen problems because the manufacturer hasn't tested that combination.If you have engine trouble and take your car to the dealer you will find your warranty is void because you used an unsupported component.If you don't care about voiding your warranty and are comfortable taking the risk go ahead and install your new carburetor.If you want the dealer to fix problems under the warranty then don't use unauthorized components.Same with JDK/JDBC/DB versions - if you want support from Oracle use authorized/supported combinations.If you don't care about support or potential problems use any combo you want.
rp0428 wrote:
OMG, please don't void my warranty. Thanks