Under committed access, if the server crashes, Essbase rolls back all database updates by transactions that were in progress when the server stopped, ensuring that changes made by the aborted transactions are undone.
If a transaction is aborted because of a nonfatal error, all changes made by the transaction are rolled back.