Re: [Squirrel-sql-users] Help diagnose why SQuirreL fails to connect to Oracle

[Karr, D. <dav...@wa...>]

Bingo.  I changed it to use the jar in the server/ext path, and now it
just works.  Beats me what the difference is.=20

> -----Original Message-----
> From: Robert Manning [mailto:rob...@gm...]=20
> Sent: Sunday, July 09, 2006 4:31 PM
> To: Karr, David
> Subject: Re: [Squirrel-sql-users] Help diagnose why SQuirreL=20
> fails to connect to Oracle
>=20
> On 7/9/06, Karr, David <dav...@wa...> wrote:
> > > -----Original Message-----
> > Ok, I went back to the old setup, with the "ojdbc14.jar"=20
> removed from=20
> > the "lib" dir, and added it back to the "Extra ..." list,=20
> pointing to=20
> > its original location (in the WebLogic81 distribution).
>=20
> Incidentally, which ojdbc14.jar were you using in the WL 8.1 dist?
>=20
> Is it :
>=20
> <BEA_HOME>/weblogic81/server/lib
> or
> <BEA_HOME>/weblogic81/server/ext/jdbc/oracle/920
>=20
> The reason I ask is because I've never attempted to use the=20
> "plain" Oracle drivers distributed with WL - just the=20
> DataDirect drivers - and they can be tricky because they=20
> require alot of supporting jars.
>=20
> > Is there a log file that would help?  Is there some debugging I can=20
> > turn on that would give us more info?
>=20
> The log file is in <user.home>/.squirrel-sql/logs/squirrel-sql.log
> Debug can be enabled by making the following change in
> SQUIRREL_SQL_HOME/log4.j.properties:
>=20
> log4j.rootLogger=3Derror, SquirrelAppender
>=20
> becomes
>=20
> log4j.rootLogger=3Ddebug, SquirrelAppender
>=20
> where SQUIRREL_SQL_HOME is where SQuirreL is installed.
>=20
> I'll take a look at the log (or relevant portion) if you want=20
> to email it to me.  If there are any pieces of data in the=20
> log that you don't want me to see, feel free to scrub it.
>=20
> Rob
>=20