Locking Under Uncommitted Access

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.

Table 159. Locking Behavior with Uncommitted Access

Status when Tx2 Makes a Request

If Tx1 holds read lock

If Tx1 holds write lock

Read lock

Tx2 gets read lock

Tx2 gets read lock

Write lock

Tx2 gets write lock

Tx2 waits for Tx1 to release the lock