For databases, Essbase automatically commits data to disk. By specifying isolation levels and related settings, you can tell Essbase how to commit data blocks to disk. For transactions, Essbase offers two isolation levels: committed access and uncommitted access (the default). Using committed access optimizes data integrity.
Note: | These options do not apply to aggregate storage databases. |
You need Database Manager permissions to change isolation level settings. Changes become effective the next time that there are no transactions.
To specify isolation levels and related settings for databases:
From Enterprise View or a custom view, select a database.
Right-click, and select Edit, and then Properties.
In the Database Properties window, select the Transactions tab.
Select Committed access or Uncommitted access (the default).
If you selected Uncommitted access, expand the Synchronization point node, and specify a number for Commit block and/or Commit row.
Click Apply.
“Understanding Isolation Levels” in the Oracle Essbase Database Administrator's Guide
alter database (MaxL) in the Oracle Essbase Technical Reference
setdbstate (ESSCMD) in the Oracle Essbase Technical Reference
setdbstateitem (ESSCMD) in the Oracle Essbase Technical Reference
getperfstats (ESSCMD) in the Oracle Essbase Technical Reference