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

Pentaho BI Platform Tracking | Billy Armstrong | 9 years ago
  1. 0

    Whenever I try to do: SELECT L.LOOKUP_ID, L.LOOKUP_DESCRIPTION , CAST(? AS CHAR(30)) AS X FROM OTPUSER.LOOKUP L INNER JOIN OTPUSER.LOOKUP_ASSOC LA on L.LOOKUP_ID = LA.LOOKUP_CHILD_ID WHERE L.LOOKUP_DESCRIPTION = 'Interactive' it retrieves one line and then fails with this error: Unexpected error : 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 org.pentaho.di.core.database.Database.getRow(Database.java:2727) 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) Caused by: com.ibm.db2.jcc.c.SqlException: [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) ... 3 more sboden suggested: "It's a known feature with DB2 (of v7 and v8 I'm sure off), they have a "strange" interpretation of the JDBC spec: When ResultSet is TYPE_FORWARD_ONLY it reaches the end of the ResultSet it returns false and closes the ResultSet. The typical use is while(rs.next) {...} and you usually dont use the resultset anymore. But in case you do a rs.next again, it will result a 'com.ibm.db2.jcc.a.SqlException: Invalid operation: result set closed' exception." More discussion is at http://forums.pentaho.org/showthread.php?p=177515#post177515

    Pentaho BI Platform Tracking | 9 years ago | Billy Armstrong
    org.pentaho.di.core.exception.KettleDatabaseException: Couldn't get row from result set [ibm][db2][jcc][10120][10898] Invalid operation: result set is closed.
  2. 0

    Whenever I try to do: SELECT L.LOOKUP_ID, L.LOOKUP_DESCRIPTION , CAST(? AS CHAR(30)) AS X FROM OTPUSER.LOOKUP L INNER JOIN OTPUSER.LOOKUP_ASSOC LA on L.LOOKUP_ID = LA.LOOKUP_CHILD_ID WHERE L.LOOKUP_DESCRIPTION = 'Interactive' it retrieves one line and then fails with this error: Unexpected error : 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 org.pentaho.di.core.database.Database.getRow(Database.java:2727) 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) Caused by: com.ibm.db2.jcc.c.SqlException: [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) ... 3 more sboden suggested: "It's a known feature with DB2 (of v7 and v8 I'm sure off), they have a "strange" interpretation of the JDBC spec: When ResultSet is TYPE_FORWARD_ONLY it reaches the end of the ResultSet it returns false and closes the ResultSet. The typical use is while(rs.next) {...} and you usually dont use the resultset anymore. But in case you do a rs.next again, it will result a 'com.ibm.db2.jcc.a.SqlException: Invalid operation: result set closed' exception." More discussion is at http://forums.pentaho.org/showthread.php?p=177515#post177515

    Pentaho BI Platform Tracking | 9 years ago | Billy Armstrong
    org.pentaho.di.core.exception.KettleDatabaseException: Couldn't get row from result set [ibm][db2][jcc][10120][10898] Invalid operation: result set is closed.
  3. 0

    Spring & [ibm][db2][jcc][10120][10898] Invalid operation: resultset is closed. - dbTalk Databases Forums

    dbtalk.net | 1 year ago
    com.ibm.db2.jcc.c.SqlException: [ibm][db2][jcc][10120][10898] Invalid operation: result set is closed.
  4. Speed up your debug routine!

    Automated exception search integrated into your IDE

  5. 0

    DB2 & Spring | dBforums – Everything on Databases, Design, Developers and Administrators

    dbforums.com | 11 months ago
    com.ibm.db2.jcc.c.SqlException: [ibm][db2][jcc][10120][10898] Invalid operation: result set is closed.

    Not finding the right solution?
    Take a tour to get the most out of Samebug.

    Tired of useless tips?

    Automated exception search integrated into your IDE

    Root Cause Analysis

    1. com.ibm.db2.jcc.c.SqlException

      [ibm][db2][jcc][10120][10898] Invalid operation: result set is closed.

      at com.ibm.db2.jcc.c.bh.mb()
    2. com.ibm.db2
      bh.next
      1. com.ibm.db2.jcc.c.bh.mb(bh.java:3327)
      2. com.ibm.db2.jcc.c.bh.c(bh.java:253)
      3. com.ibm.db2.jcc.c.bh.next(bh.java:238)
      3 frames
    3. org.pentaho.di
      TableInput.run
      1. org.pentaho.di.core.database.Database.getRow(Database.java:2662)
      2. org.pentaho.di.core.database.Database.getRow(Database.java:2647)
      3. org.pentaho.di.trans.steps.tableinput.TableInput.processRow(TableInput.java:129)
      4. org.pentaho.di.trans.steps.tableinput.TableInput.run(TableInput.java:314)
      4 frames