This content has been marked as final. Show 4 replies
925144 wrote:Error seems pretty clear to me. Methinks you have to take a dive into the documentation again and compare the JDBC URL you have now to what is written in the specifications.
Caused by: java.sql.SQLException: Invalid Oracle URL specified
We're using:Not really. ojdbc14 is a very old driver that was built for Java 1.4 and is designed to be used with Oracle 10g R2. If you use Oracle 11 and Java 6, use the matching ojdbc6 driver (the number in the driver name matches the Java major version).
Java : jdk1.6_31
JDBC : odjbc14.jar
Oracle : Oracle 11g RAC
Is the driver compatible? If yes, could there be something wrong with our URL? Any other possibilities to help?
That doesn't mean it won't work, the database engine underneath doesn't change so much that it would have an influence on JDBC logic so it is possible that an older driver works just fine with a newer DBMS release when you use it purely for JDBC purposes. But I wouldn't like to take chances when its not necessary.
JDBC specs provide the API, do you want to know something about the API? No, you want to know how to configure the Oracle JDBC driver. I don't want to be a douche, but a little reasoning goes a long way.
And of course there is an url, but I'd have to search for it. But that is something you can do too. Or you can just search google for "ojdbc connection url" until you see an example that matches your own setup. I must say that I've never seen a connection string with two hosts in it. Mine always look like this:
One connection, one SID.
1. use ojdbc6.jar driver.
2. With RAC it may make sense to use client side connection Load Balance.
Otherwise first ADDRESS will be always tried first.