Ojdbc14.jar driver version

So what driver do we use? The latest Oracle 11g - despite the fact that it's usually 9i and 10g databases? Why don't they just link all versions to the same "one driver suits all" file? Or are there minute differences leading to effects like our random errors? The numbers in ojdbc For example in Java 8, there is a new method executeLargeUpdate in java.

This method will be implemented in ojdbc8. Also if your runtime uses Java 7 then you know you can't use ojdbc8. UnsupportedClassVersionError error. These are the reasons why Oracle includes these numbers in the jar's name. Also note that if you want to know from which Oracle Database release the jar comes from you can run java -jar ojdbc8.

Both the Database and the driver are backward compatible up to 1 major release so, even though it's recommended, you don't have to use the same version of the product on both tiers.

When we upgraded our Oracle database from 8. OMG Ponies k 75 75 gold badges silver badges bronze badges. Stroboskop Stroboskop 4, 5 5 gold badges 33 33 silver badges 50 50 bronze badges. The "version" in the driver's filename refers to the Java version they are intended for, not to the driver's version.

I made it a habit to save the jar file with the driver's version appended when downloading them e. Just go for the latest drivers. Add a comment. Active Oldest Votes. Improve this answer. Adam Butler 2, 4 4 gold badges 33 33 silver badges 38 38 bronze badges. Oliver Michels Oliver Michels 2, 1 1 gold badge 17 17 silver badges 14 14 bronze badges.

These drivers "can talk to" just about any modern database version. So you're saying i just pick the newest release and keep my fingers crossed that it has all the bug fixes i need?

We retired them last year. Are we talking about ORA, invalid number? If so, i would check the debugging logs and not care about driver version conflicts. Yes, it's ORA We use PreparedStatements, meaning the type conversions are all done by the driver. And the same statement works fine We of course looked at our code first, but there seems to be nothing out of the ordinary.

Random ORA errors are very often caused by relying on implicit data type casting. Don't do it. Jean de Lavarene Jean de Lavarene 3, 1 1 gold badge 18 18 silver badges 25 25 bronze badges. With the compiler from JDK 1. Sign up or log in Sign up using Google. Sign up using Facebook. Sign up using Email and Password. Post as a guest Name.

Email Required, but never shown. The Overflow Blog. Stack Gives Back Safety in numbers: crowdsourcing data on nefarious IP addresses. Featured on Meta. New post summary designs on greatest hits now, everywhere else eventually. Visit chat. Linked 0. Related