|
From: Karr, D. <dav...@wa...> - 2006-07-08 18:36:55
|
> -----Original Message----- > From: Robert Manning [mailto:rob...@gm...]=20 >=20 > On 7/7/06, Karr, David <dav...@wa...> wrote: > > I had SQuirreL 2.1 installed, and I installed 2.2 over it. =20 > I entered=20 > > a new alias for an Oracle thin connection, but it fails with "The=20 > > Network Adapter could not establish the connection" when I=20 > try to connect. > > Another person at another location in my company uses Squirrel (not=20 > > sure which version) to connect to the same db, with no trouble. I=20 > > looked at the driver properties, and the driver class name wasn't=20 > > quite what I expected, so I changed it to what I expected=20 > > (oracle.jdbc.OracleDriver), but it made no difference. I=20 > then wrote a=20 > > trivial build.xml that uses the same connection info (and=20 > classpath to=20 > > the driver) and just tries to list the available tables,=20 > and it works perfectly fine. > > > > What could be going wrong here? >=20 > Have a look at the attached java code that Gerd Wagner=20 > created to simlate the way that SQuirreL obtains connections.=20 > It's a simple command-line program that expects four=20 > arguments (driverclass, url, user ,password). It's about as=20 > simple as it can be and might be useful in demonstrating=20 > issues with the driver or connection properties outside of SQuirreL. Unfortunately, this didn't help, or maybe it did. I plugged in the exact same connection data into this command-line tool, and it works perfectly fine. I still can't connect to the database with SQuirreL 2.2, using this connection data. |
