Connection JDBC d'un PC Windows NT a une base Oracle sur IBM AIX

Question

j'utilise un driver JDBC pour me connecter a une base Oracle sur
un serveur Unix IBM AIX a partir d'une station sous Windows NT4
(SP6)
Par contre, lorsque je lance la connection il m'affiche une
SQLException : Exception d'E/S : the network adapter could not
establish the connection
Donc de quoi ais-je besoin entre ma station NT et le serveur Unix
pour me connecter ???
Sinon j'ai entri ca comme parametre de connection :
JDBC Driver : oracle.jdbc.driver.OracleDriver
URL : jdbc:oracle:thin:@<Adresse IP du serveur Unix>:1721:orax
(orax : nom de la base de donnies)
<sid> -> ne sachant pas ce que cela represente j'ai pensi entrer
le nom de la BD a la place, mais a mon avis cela est faux !!!
Donc avez une astuce ?

Answer 1

Hi, yes we should go straight to lynching the driver.
;)No we shouldn't. We should lynch Edward King.
No matter what Java is tried, even homicidal Java
code can't cause native segfaults that kill the JVM.Well you see....
The only cause of this is broken native code.Technically correct and I agree but (and you knew this was coming)....
First of all http://java.sun.com/products/jdbc/faq.html#14 This may or may not be part of the problem here. I can't say for sure. But the bridge driver is not multi-threaded. Sun is pretty straightforward in saying so. Since it is (contains) native code if you treat it otherwise you need to expect bad things to happen.
More importantly though...
EdwardKing is using MS Access. Access is a single user desktop database product not a database service (let alone an enterprise database service).
So multiple connections hitting a Access database may well cause unpleasant things. One can blame the driver yes and ultimatley the source point for the actual error is there I agree but EdwardKing is in reality to blame for trying to use a product (Access) for which it was not intended.
And this leads me back to my original point which is that even IF another driver supports connection pooling to Access in reality it isn't much of a connection pool at all. Because (a) there is no actual network connection and (b) all the queries will be lining up one at a time to lock the underlying file to do things anyway.
JoeMax
PS Another Joe will be along later to possibly comment on the suitablity of the use of the JDBC-ODBC bridge driver. However once again I would just like to point out that my underlying concern is that Edward King is trying to use Access as if it were SQL-Server or the like and it is no such thing.