Essbase issues write (exclusive) locks for blocks that are created, updated, or deleted, and issues read (shared) locks for blocks that should be accessed but not modified. By issuing the appropriate locks, Essbase ensures that data changed by one operation cannot be corrupted by a concurrent update.
This section discusses locks on data blocks, not locks on database artifacts. For information about locking and unlocking outlines and other artifacts, see Locking and Unlocking Artifacts.
Table 156 explains the lock types:
Table 156. Basic Lock Types
Table 157 shows the locks that Essbase issues for various types of operations.
Table 157. Locking by Higher-Level Functions
How Essbase handles locking depends on whether committed or uncommitted access is enabled.