Example explains rise in IBM DB2 intercurrent 3 spent methods

In DB2, can rise with 3 kinds of methods intercurrent degree:

1. Reduce segregation level, read an operation to won't be barred because of lock conflict

Select. . . . With UR

2. Or, the change increases the opportunity of the lock, reduce a lock to conflict (such Insert/update/delete operations that its get on all right won't chain different Select operates the condition)

Db2set DB2_EVALUNCOMMITTED=ON

Db2set DB2_SKIPDELETED=ON

Db2set DB2_SKIPINSERTED=ON

3. Or reference is added on Where relevant field, reduce a lock to take up

Annotate:

This parameter will be in Db2set DB2_EVALUNCOMMITTED=ON - the ongoing travel predication that records a lock is checked, reduce the time of the lock as far as possible;

Db2set DB2_SKIPINSERTED=ON - new Insert of this parameter general and the data that did not submit is jumped over; For example, SELECT/UPDATE statement won't discover this record;

Db2set DB2_SKIPDELETED=ON - new Delete of this parameter general and the data that did not submit is jumped over; For example, SELECT/UPDATE statement does not await this record refer, and think he had been deleted.