Working with Hibernate and DB2 9, if you have a byte member in your entity which is supposed to be mapped to a BLOB column, you'll probably get:
ERROR [org.hibernate.util.JDBCExceptionReporter] - <DB2 SQL Error: SQLCODE=-301, SQLSTATE=07006, SQLERRMC=2, DRIVER=3.61.75> ERROR [org.hibernate.event.def.AbstractFlushingEventListener] - <Could not synchronize database state with session> org.hibernate.exception.SQLGrammarException: could not insert...
Which in general means wrong data type!
After throwing lots of hooks into the sea of Google & IBM, I came up with this one - thanks to Steve for his excellent fish
Which gave me a very good starting point. Noticing byte is mapped by hibernate to org.hibernate.type.
I tried modifying the mapping by explicitly specifying the type as blob or binary (Hibernate specific)
or changing the member type to Byte, InputStream or even java.sql.Blob (which is a bad practice anyway). Well, the exception was gone, but, for some reason, the actual binary data was not inserted to the DB!
So getting back to steve's post, the only solution wich worked for me was overriding the connection's progressive streaming behaviour by adding the following property to the connection url:
Hope this will save you a couple of fishing hours
P.S. - Make sure you're using the latest DB2 JDBC driver, since the version shipped with your DB2 might contain some bugs...
Some resources and background: