Connection timeout with DB2 source
Hi all,
looking for any similar experience... I've a scenario, started with StartScen.sh command, that imports data from a DB2 mainframe database and do some transformation.
Sometimes, when data to import is huge, even if all ELT transformations goes ok the whole scenario fails. Debugging it I've seen that failure is due to a timeout got from DB2 connection. I've found that ODI works in this way:
1. Opens connection to DB2
2. Loads needed datas
3. Peforms transformations
4. Closes connection
Since step 3 takes long time DB2 connection time out and of course when you close the connection you get an error about socket already closed from remote side. TCPDump has showed that no keepalive packets are sent from client to server.
I've opened an SR to Oracle and they told me that there's no way to force closing connection before perform transformation. Also Oracle relays problem to a possibile missing keepalive function in DB2 JDBC driver. Oracle suggests to change the scenario adding a step to load data from DB2 to a local table and then another step to perform transformation starting from this local table. This is not applicable as many scenarios have to be change in a production environment.
Does anyone has already dealt with a similar problem?
Thanks
Stefano
--
http://www.stefanocislaghi.eu/