Re: [Squirrel-sql-users] DB2 Type 4 Driver: SqlException: Invalid operation: result set closed

[Gerd W. <bir...@t-...>]

Hi Karim,

during the last months all the work I did on SQuirreL was mostly tested 
against DB2 Version 8.2 running on Linux. The driver I use is
COM.ibm.db2.jdbc.net.DB2Driver, URL: jdbc:db2://<host>/<db>
with db2java.zip and db2jcc.jar in the driver definition's extra 
classpath. I Never saw such trouble.


Karim D. Saloojee wrote:
> Hi
> 
> We have just migrated to DB2 Version 8 and are now using the JDBC Type 4 
> driver. This is when the problems started.
> 
> The first problem is when running a simple query (SELECT * from 
> CUSTOMER) the following exception is printed out in the output window:
> com.ibm.db2.jcc.b.SqlException: Invalid operation: result set closed
> Query 1 elapsed time (seconds) - Total: 0.078, SQL query: 0.047, 
> Building output: 0.031
> 
> In 1.2b6, the results of the query are still printed out in the results 
> window. In 2.0rc1 the results of the query do not even display. Using 
> the "Objects" view and drilling down, Squirrel displays the table data 
> in both versions without any issue.
This sounds like a problem that occurred on the Derby DB some time ago. 
I'm not sure if it is fixed in 2.0 rc1. You may try out the latest 
weekly build to be sure you have got the fix.



> 
> I have written a simple class that creates a JDBC connection in the same 
> way. When I run the query, no errors/exceptions occur. Although I only 
> retrieve the first column from the result set but I do not believe this 
> is related to the issue.
> 
> The second problem is as follows. When running an update as follows: 
> UPDATE CUSTOMER SET SEGMENT = 777 WHERE ID IN (SELECT CUSTOMERID from 
> CASEBASIC)
> the following is displayed in the output window:
> 13 Rows Updated
> Query 1 elapsed time (seconds) - Total: 0, SQL query: 0, Building output: 0
> Error: java.lang.StringIndexOutOfBoundsException: String index out of 
> range: -35
Could you please have look at the Windows menu --> 'View SQuirreL logs' 
and check you find a stacktrace for the exception. If so please send it 
to me.

Thanks

Gerd