Ensuring that CUR_COMMIT is ON on DB2 version 9.7 and later versions

Edit online

Databases that are updated from versions earlier than DB2 version 9.7 have this parameter set to DISABLED. It must be set to ON.

Before you begin

  1. You must have IBM® DB2® database installed and configured on your system.
  2. You must be logged in as the DB2 Instance owner.

About this task

Installing DB2 9.7 or later versions sets the cur_commit parameter to ON by default. Databases that are upgraded from a previous release have this parameter set to DISABLED. For the proper functioning of IBM Verify Identity Governance and to prevent deadlocks during peak load, this parameter must be set to ON.

Procedure

  1. Determine whether the cur_commit is set to ON.
    Enter the commands (as DB2 Instance owner).
    db2 connect to itim_dbname user itim_dbadmin_id using itim_dbadmin_password
db2 get database configuration
  2. Look for the Currently Committed parameter CUR_COMMIT.
    It must be set to ON. 
    Currently Committed (CUR_COMMIT) = ON
  3. If it is not set to ON, issue the following commands to enable it. 
    db2 update db cfg  for itim_dbname using cur_commit on
db2 disconnect current
  4. Stop and start the DB2 server to set the configuration.
    Issue the commands
    db2stop
db2start
    Note:

    If db2stop fails and the database remains active, enter db2 force application all to deactivate the database. Then, enter db2stop.

What to do next

After you create and configure the IBM Verify Identity Governance database, stop and start the DB2 server for the changes to take effect.