Jack Eidsness wrote:
> The whole time, I've been using the oracle JDBC library that came with
> oracle, I think version 9.2, but once you install it, I don't know how
> to find out after-the-fact and confirm that. I had definitely
> experimented with several different versions, so I'm not 100% sure of
> that.
You can tell the JDBC driver version by looking at the "MetaData" tab in
SQuirreL
which is displayed along with the Object tree when you start a new
session. The
row to look at has a "Property Name" value of "getDriverVersion". For
instance,
I'm using the Oracle 10g driver to connect to an Oracle 9i Database
Server and
my driver version as reported by SQuirreL is - 10.2.0.1.0. The database
server
version is reported by the row that has a "Property Name" value of
"getDatabaseProductVersion". SQuirreL reports that my database server is:
Oracle9i Enterprise Edition Release 9.2.0.1.0 - Production
With the Partitioning, OLAP and Oracle Data Mining options
JServer Release 9.2.0.1.0 - Production
> For some reason, I can initially only run one SQL query per session now;
> I did a select * from some_small_table, and got a normal looking
> result window, and subsequent queries produce an "Executing SQL" tab,
> and a cancel button, but nothing ever happens.
My guess would be that at this point an exception was raised that
SQuirreL didn't
handle appropriately. It's tough to say without the stack trace.
> I looked up the last traceback in my log and it says this:
>
> 1096187 [AWT-EventQueue-0] ERROR
> net.sourceforge.squirrel_sql.client.session.SchemaInfo - failed to load
> table names
We've made a number of changes to the way SchemaInfo loads it's data
recently.
Some synchronization issues were addressed. You should get the latest
snapshot
build and see if it doesn't fix this issue. You can find this build here:
http://sourceforge.net/project/showfiles.php?group_id=28383&package_id=158128&release_id=366921
If you still see the errant behavior and you have some time, please file
a bug report
against the new version with a stack trace from the log.
> I think I had tried running squirrel with Java 1.4, as well, and had
> similar results. I still have java 1.4 installed, with JDBC drivers in
> place, but I am not sure how to make it use java 1.4 instead of java 1.5
> without going through a long process of uninstallations and
> reinstallations. I can give it a go if you think this is really
> important to the troubleshooting process.
I doubt this would make any difference.
> Lastly, I would like to apologize for leaving Rob Manning hanging, back
> in July when I had originally asked about this, but didn't make time to
> follow up in the troubleshooting. Time constraints led me to move back
> to 1.2b5, which worked often enough for me.
We all have busy lives - no problem ;)
Rob Manning
CollabraSpace - Revolutionary Collaboration
Visit us at http://www.collabraspace.com
This message has been scanned for viruses by
ClamAV v0.83
|