DB2 rollbacks and isolation levels

Edit online

If you are experiencing rollback activities in DB2®, check the isolation level. Rollbacks occur when one application process has a row that is locked while another application process tries to access that same row.

The default isolation level, repeatable read, can result in more rows that are locked than are required for the current read request. Hence, a more relaxed isolation level is normally required for LDAP applications.

For example, the read stability isolation level allows other applications to insert or update data in rows that were read. If a second read is issued for that range of rows, the new data is reflected in the result set. Keep in mind, however, that the second read can return data that is different from the first read. If an application depends upon the same data to be returned on multiple reads, the isolation level must be set to repeatable read.

To set the DB2 isolation level, type the following at a command prompt:

db2set isolation_level=YES

where isolation_level is the isolation level you want to apply, such as DB2_RR_TO_RS.

Note: All applications that are using the current database instance are affected by this setting.