Evaluate Weigh the pros and cons of technologies, products and projects you are considering.

When must I journal a table?

My application accesses and manipulates data in DB2 on the iSeries. I encountered SQL error 7008; I then started...

to journal on the table, which maked the error re-occur. After that, everything runs well. But when I deploy the application on another server, the same error occurs but this time on another table. When must I journal a table? I don't care about backup and recovery -- my sole purpose is to have SQL run and not throw any exception. Journaling is required when the SQL isolation level or commitment control level is set to a value other than No Commit/*NONE. Using a value of No Commit/*NONE does prevent the application from being able to issue a Commit or Rollback.


Check out this Search400.com Featured Topic: Database issues resolved

Search400.com's targeted search engine: Get relevant information on DB2/400.

The Best Web Links: Tips, tutorials and more.

Dig Deeper on DB2 UDB (universal databases)

Have a question for an expert?

Please add a title for your question

Get answers from a TechTarget expert on whatever's puzzling you.

You will be able to add details on the next page.

Start the conversation

Send me notifications when other members comment.

Please create a username to comment.