Under uncommitted access, Essbase locks blocks for write access until Essbase finishes updating the block. Under committed access, Essbase holds locks until a transaction completes.
Table 159 illustrates locking behavior under uncommitted access when many transactions contend for a lock on the same data. In this example, transaction Tx1 is running and transaction Tx2 is requesting access to the same data.