I have been using squirrel 1.2 b5 (I think that's it) for quite some
time with no plugins, and I just installed version 2 rc1 and the oracle
plugin version .13. My Java installation is Sun's version 1.5, and I'm
working on a Windows XP computer. I hadn't used 1.2 b6 because of some
problems which I never got around to properly reporting.
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.
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. On a whim, I clicked to
start a new SQL worksheet for the same session, and it took about 3 full
minutes (I'm guessing), but seemed to unlock this state of
unresponsiveness. Both SQL worksheets were then able to do a few
queries, and for the first time, the syntax of my original statement in
the first window was highlighted.
Then I accidentally executed a statement with my cursor immediately
after the ";" that I had at the end of my test statement, and I got an
"ORA-0911: invalid character" error from oracle. The next three
Subsequent queries result in these three errors:
And it seems that I should expect that to continue until I start a new
session with this database. The IO Exception used to happen to me once
in a while, before upgrading to version 2. I never used 1.1b6 because
the short version of the error message appeared quite regularly (I don't
have a log from that, with the detail though, and I do know that
SQLException: Io Exception could be caused by many different things).
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
java.sql.SQLException: Io exception: invalid arguments in call
at javax.swing.plaf.basic.BasicTextUI$RootView.paint(Unknown Source)
at javax.swing.plaf.basic.BasicTextUI.paintSafely(Unknown Source)
at javax.swing.plaf.basic.BasicTextUI.paint(Unknown Source)
at javax.swing.plaf.basic.BasicTextUI.update(Unknown Source)
at javax.swing.JComponent.paintComponent(Unknown Source)
at javax.swing.JComponent.paint(Unknown Source)
at javax.swing.JComponent.paintWithOffscreenBuffer(Unknown Source)
at javax.swing.JComponent.paintDoubleBuffered(Unknown Source)
at javax.swing.JComponent._paintImmediately(Unknown Source)
at javax.swing.JComponent.paintImmediately(Unknown Source)
at javax.swing.RepaintManager.paintDirtyRegions(Unknown Source)
at java.awt.event.InvocationEvent.dispatch(Unknown Source)
at java.awt.EventQueue.dispatchEvent(Unknown Source)
at java.awt.EventDispatchThread.pumpOneEventForHierarchy(Unknown Source)
at java.awt.EventDispatchThread.pumpEventsForHierarchy(Unknown Source)
at java.awt.EventDispatchThread.pumpEvents(Unknown Source)
at java.awt.EventDispatchThread.pumpEvents(Unknown Source)
at java.awt.EventDispatchThread.run(Unknown Source)
Over the past year and a half of using squirrel 1.1 and 2.0, I've
uninstalled and reinstalled several times, sometimes deleting or moving
$HOME\.squirrel-sql, as well. I've been using Squirrel on two
different Win XP computers. Some combinations have produced the Io
Exception, others have worked. My theory is that there may be something
weird about my database schema we have at work that breaks Squirrel,
also depending on some other more random element of the environment.
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.
For followup questions, I'll stick to talking about my 2.0 installation
that I have now, but the background was just to show that I don't think
the SQLException: Io Exception is a new problem from v2.
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.
> 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
You can tell the JDBC driver version by looking at the "MetaData" tab in
which is displayed along with the Object tree when you start a new
row to look at has a "Property Name" value of "getDriverVersion". For
I'm using the Oracle 10g driver to connect to an Oracle 9i Database
my driver version as reported by SQuirreL is - 10.2.0.1.0. The database
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 188.8.131.52.0 - Production
With the Partitioning, OLAP and Oracle Data Mining options
JServer Release 184.108.40.206.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
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
> 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 ;)
CollabraSpace - Revolutionary Collaboration
Visit us at http://www.collabraspace.com This message has been scanned for viruses by