org.pentaho.di.core.exception.KettleDatabaseException: Couldn't get row from result set [ibm][db2][jcc][10120][10898] Invalid operation: result set is closed.

Searched on Google with the first line of a JAVA stack trace?

We can recommend more relevant solutions and speed up debugging when you paste your entire stack trace with the exception message. Try a sample exception.

Recommended solutions based on your search

Solutions on the web

via Pentaho BI Platform Tracking by Billy Armstrong, 1 year ago
Couldn't get row from result set [ibm][db2][jcc][10120][10898] Invalid operation: result set is closed.
via Pentaho BI Platform Tracking by Billy Armstrong, 1 year ago
Couldn't get row from result set [ibm][db2][jcc][10120][10898] Invalid operation: result set is closed.
via pentaho.com by Unknown author, 2 years ago
Couldn't get row from result set Attempt to fully materialize lob data that is too large for the JVM. Disable data source property "fullyMaterializeLobData" for locator-based lob implementation.
via pentaho.com by Unknown author, 1 year ago
- Couldn't get row from result set - IO Error: Socket read timed out
via pentaho.com by Unknown author, 1 year ago
via pentaho.com by Unknown author, 1 year ago
Couldn't get row from result set ERROR: canceling statement due to user request
org.pentaho.di.core.exception.KettleDatabaseException: Couldn't get row from result set [ibm][db2][jcc][10120][10898] Invalid operation: result set is closed.
at com.ibm.db2.jcc.c.bh.mb(bh.java:3327)
at com.ibm.db2.jcc.c.bh.c(bh.java:253)
at com.ibm.db2.jcc.c.bh.next(bh.java:238)
at org.pentaho.di.core.database.Database.getRow(Database.java:2662)
at org.pentaho.di.core.database.Database.getRow(Database.java:2647)
at org.pentaho.di.trans.steps.tableinput.TableInput.processRow(TableInput.java:129)
at org.pentaho.di.trans.steps.tableinput.TableInput.run(TableInput.java:314)

Users with the same issue

You are the first who have seen this exception. Write a tip to help other users and build your expert profile.

Know the solutions? Share your knowledge to help other developers to debug faster.