|
From: Jack E. <ja...@pe...> - 2005-11-04 02:56:38
|
Hi - 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: SQLState: 42000 ErrorCode: 911 Error: Io exception: invalid arguments in call SQLState: null ErrorCode: 17002 Error: java.sql.SQLException: Io exception: invalid arguments in call, SQL State: null, Error Code: 17002 Error: java.sql.SQLException: Io exception: invalid arguments in call, SQL State: null, Error Code: 17002 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 table names java.sql.SQLException: Io exception: invalid arguments in call at oracle.jdbc.dbaccess.DBError.throwSqlException(DBError.java:134) at oracle.jdbc.dbaccess.DBError.throwSqlException(DBError.java:179) at oracle.jdbc.dbaccess.DBError.throwSqlException(DBError.java:334) at oracle.jdbc.driver.OracleStatement.freeLine(OracleStatement.java:6483) at oracle.jdbc.driver.OracleConnection.needLine(OracleConnection.java:2400) at oracle.jdbc.driver.OracleStatement.open(OracleStatement.java:557) at oracle.jdbc.driver.OracleStatement.doExecuteWithTimeout(OracleStatement.java:2786) at oracle.jdbc.driver.OraclePreparedStatement.executeUpdate(OraclePreparedStatement.java:608) at oracle.jdbc.driver.OraclePreparedStatement.executeQuery(OraclePreparedStatement.java:536) at oracle.jdbc.OracleDatabaseMetaData.getColumns(OracleDatabaseMetaData.java:2571) at net.sourceforge.squirrel_sql.client.session.SchemaInfo.loadColumns(SchemaInfo.java:788) at net.sourceforge.squirrel_sql.client.session.SchemaInfo.isTable(SchemaInfo.java:295) at net.sourceforge.squirrel_sql.plugins.syntax.netbeans.SQLSyntax.matchTable(SQLSyntax.java:948) at net.sourceforge.squirrel_sql.plugins.syntax.netbeans.SQLSyntax.parseToken(SQLSyntax.java:773) at org.netbeans.editor.Syntax.nextToken(Syntax.java:173) at org.netbeans.editor.DrawEngine.draw(DrawEngine.java:1089) at org.netbeans.editor.DrawEngineLineView.paint(DrawEngineLineView.java:227) at org.netbeans.lib.editor.view.GapBoxViewChildren.paintChildren(GapBoxViewChildren.java:777) at org.netbeans.lib.editor.view.GapBoxView.paint(GapBoxView.java:1457) at org.netbeans.lib.editor.view.GapDocumentView.paint(GapDocumentView.java:225) at org.netbeans.editor.DrawEngineDocView.paint(DrawEngineDocView.java:300) at org.netbeans.editor.view.spi.LockView.paint(LockView.java:357) 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 javax.swing.SystemEventQueueUtilities$ComponentWorkRequest.run(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. -Jack Eidsness |
