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.
MORE INFORMATION ON THIS TOPIC
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)
Related Q&A from Kent Milligan
Create a host variable of the where in statement on the fly with dynamic SQL. Continue Reading
To solve the SQL error -321 on IBM i6.1, use the new values statement to overcome the error. If you are using an older release, declare a cursor ... Continue Reading
When working with DB2 files with columns that have both short and long names, there is no option choose which column names are returned via ODBC ... Continue Reading