Folks

I have an hibernate application up and running in development against a DB2/400.
At this stage I point out that I am no iSeries(AS400) expert.

The app runs fine when the DB2/400 files are journaled, but when they are not journaled(as is the intended case for production- don't ask me why?) I get the following

[03/10/03 11:28:03:881 BST] 170a4eee JDBCException E net.sf.hibernate.util.JDBCExceptionReporter TRAS0014I: The following exception was logged java.sql.SQLException: [SQL7008] TKD6CPP in LTRAPF not valid for operation.
at com.ibm.as400.access.JDError.throwSQLException(JDError.java:520)
at com.ibm.as400.access.AS400JDBCStatement.commonExecute(AS400JDBCStatement.java:822)
at com.ibm.as400.access.AS400JDBCPreparedStatement.executeUpdate(AS400JDBCPreparedStatement.java:1179)
at net.sf.hibernate.impl.NonBatchingBatcher.addToBatch(NonBatchingBatcher.java:22)
at net.sf.hibernate.persister.EntityPersister.insert(EntityPersister.java:478)

which I have been informed by the AS400 guys that it would appear that
hibernate is expecting the DB2/400 file to be journaled. Is this the case?

Any advice would be appreciated

cheers
Paul

This sounds like a JDBC driver issue.

The problem is that Hibernate will require transactions, and without journaling DB2/400 is not capable of SQL transactions. You will REQUIRE journaling to work with hibernate, or hack hibernate to append "with nc" to every sql statement and remove use of transactions.

You will also run into problems if you are not using OS400 V5R4 or higher due to problems with ORDER BY on columns that are not SELECTed

This is all from experience with a medium complexity project working with DB2/400

Hi...
Paul, did you find any workaround to this issue??

I'm facing the same problem.
Thank you.

The workaround is to have journaling on. Hibernate will not work without it.

I too had to work against an AS400 database with journalling off. Setting hibernate.connection.isolation 0 worked for me, however each statement was autocommitted.