If the server crashes while you are loading data, Essbase sends you a timeout error. The recovery procedures that you must perform depend on the type of load you are performing and the Isolation Level database transaction setting (see Understanding Isolation Levels):
If you are overwriting the values of the data source, reload the data source when the server is running again.
If you are adding to or subtracting from existing values in the data source and the Isolation Level setting is:
Committed, reload the data source when the server is running again.
Uncommitted, determine how much data Essbase loaded before the crash:
Compare the values of the data source with the values of the database.
If the values that you are adding to or subtracting from have not changed, reload the data source.
If the values that you are adding to or subtracting from have changed, clear the values that loaded and reload the previous data sources. If, for example, you derive monthly sales figures by adding the sales figures for each week as they are loaded, clear the sales figures from the database and reload the sales figures for each week up to the current week.