Using CUR_COMMIT concurrency control isolation level
DB2 9.7 introduces a new isolation level called Currently Committed (CC) , wherein readers don't block writers, and writers don't block readers. In earlier versions of DB2, there were chances that a reader would block a writer and a writer would block a reader.
The isolation level currently committed will be set at the database level using the CUR_COMMIT parameter. When one creates a database on DB2 9.7, by default, CUR_COMMIT will be ON, and in case if one migrates the database from an older version on to DB2 9.7, one has to update the configuration parameter explicitly.
Getting ready
To update the database configuration parameter CUR_COMMIT, one should have the SYSADM or the DBADM privilege.
How to do it...
In this section, we'll look at extracting the current database configuration parameter CUR_COMMIT, and update it, if it's not active. We will also look at the ways of overriding the database-level parameter at the application layer...
