|
From: Karr, D. <dav...@wa...> - 2006-07-08 23:51:34
|
> -----Original Message----- > From: Robert Manning [mailto:rob...@gm...]=20 >=20 > On 7/8/06, Karr, David <dav...@wa...> wrote: > > > > Unfortunately, this didn't help, or maybe it did. > > > > I plugged in the exact same connection data into this command-line=20 > > tool, and it works perfectly fine. I still can't connect to the=20 > > database with SQuirreL 2.2, using this connection data. >=20 > Well, that is a bit of a surprise. You get "The Network=20 > Adapter could not establish..." from SQuirreL, but it=20 > connects fine using the command-line test utility? Makes me=20 > think that the driver being loaded isn't the one you think in=20 > SQuirreL. Do you place drivers in SQUIRREL_HOME/lib or use=20 > the "Extra Classpath" tab for your drivers? When I installed 2.2, my Oracle Thin driver was set up with the "Extra Classpath" pointing to the jar file containing the class. I'm guessing the driver data is stored in the registry, because I tried completely removing the 2.1 directory before installing 2.2, and it still had the same values (my aliases were still there too). I just tried changing my driver definition to remove the "Extra Classpath" entry containing the jar file, and I copied that jar file into the "lib" subdir of SQuirreL, and then I restarted Squirrel. I know it noticed the difference, because before that, the "Oracle OCI" driver didn't have a checkmark, and now it does. Unfortunately, my connection with the Oracle Thin driver still fails. |
