Closed as program error.
Problem: When using JDBCConnector to DB2 with Delta and "Read Deleted" checked the following error is displayed when iterating through the result set - 16:13:16,201 INFO - [IterateData] CTGDIZ908I DELTA: Iterating through deleted entries. 16:13:16,211 INFO - marked as deleted: ID94 16:13:16,251 INFO - deleted: ID94 16:13:16,261 INFO - [IterateData] CTGDIS495I handleException , get, com.ibm.db2.jcc.c.SqlException: [ibm][db2][jcc] Virheellinen toiminto: result set on suljettu. 16:13:16,271 ERROR - [IterateData] CTGDIS810E handleException - cannot handle exception , get com.ibm.db2.jcc.c.SqlException: [ibm][db2][jcc] Virheellinen toiminto: result set on suljettu. The exception is caused by a failed attempt to read further data from an already closed ResultSet, We have been able to reproduce this behaviour in our lab environment, and this appears to be a code defect. Steps to Duplicate: b.1) Create a DB "mydb" on the target DBMS b.2) Create a table "MYTEST" with fields: SN, GIVENNAME and TITLE (no need to create any primary key) b.3) Add a couple of records in the table (at least two ones) b.4) Modify the configuration above: change the "db2" connector username and password to the one specific for your db b.5) Run the "myJDBC" AL: it will detect the added rows (all ones) b.6) Manually access to the "MYTEST" and remove a row b.7) Run again the "myJDBC" AL: the subjected exception will be logged Desired Behavior: Customer needs to iterate through deleted objects with out the jdbc connector throwing an error. Environment: TDI-7.1-FP0006 DB2 9.7
Problem with JDBC connector with iterator mode with delta "Read deleted"
This is bug in TDI code and has been fixed, formal fix will be made available in 7.1.0-TIV-TDI-FP0008.
Reported component name
Reported component ID
Last modified date
APAR is sysrouted FROM one or more of the following:
APAR is sysrouted TO one or more of the following:
Fixed component name
Fixed component ID
Applicable component levels