FanaticZine

Today when I was running one of my kettle scripts against a large Data Ware House DB, an error popped out in my log, something looks like this,

Unexpected error :
org.pentaho.di.core.exception.KettleDatabaseException:
Couldn’t get row from result set

and further

Unexpected error closing query : org.pentaho.di.core.exception.KettleDatabaseException:
Couldn’t close query: resultset or prepared statements
Communications link failure due to underlying exception: ** BEGIN NESTED EXCEPTION ** java.net.SocketException
MESSAGE: Connection reset STACKTRACE:

java.net.SocketException: Connection reset

This is simply because, after long time in execution the MySQL server get confused at somewhere in the corner and decides to not to feed the rows back to JDBC driver. As I found in MySQL massage board placing SQL_NO_CACHE next to your SELECT keyword (SELECT SQL_NO_CACHE * FROM users) should solve the issue.

I will confirm, if this works since my script is still running, so far so good!

To be verified….

REF :: http://forums.mysql.com/read.php?39,203407,217196#msg-217196