Unfortunately this looks like a DB2
JDBC dirver bug.
Here are a few tips:
- update to the latest driver version
- enable SQL logs (show_sql = true see the reference documentation) and check the last SQL statement executed. Try to execute it manually through JDBC to see if you can reproduce the error.