What is committed and Uncommitted Access?
Ans: Committed access provides a high level of data consistency because only one transaction at a time is written to data block. Under committed access, Essbase allows transactions to hold read/write locks on all data blocks involved with the transaction until the transaction completes and commits. However, you can still allow read-only access to the last committed data values. It is time consuming if the data size is too large. Uncommitted access (enabled by default), the Essbase kernel allows transactions to hold read/write locks on a block-by-block basis; Essbase releases a block after it is updated but does not commit blocks until the transaction completes or until a specified limit (a “synchronization point”) has been reached. You can set this limit, as described below. It is faster, but in case of catastrophic conditions loads data again.Concurrent users accessing the same data blocks might experience unexpected results under uncommitted access, because Essbase allows read-only a
