Table 160 lists types of Essbase Server interruptions and their results:
Table 160. Essbase Recovery Handling
Table 161 shows what you must do if a server interruption occurs during a transaction. How Essbase recovers from an interruption depends on the transaction isolation level setting (committed or uncommitted access)—see Rollback with Committed Access and Rollback with Uncommitted Access.
Table 161. Recovery Procedures for Server Requests
If Essbase issues an error, repeat the last send operation. If the spreadsheet has been lost or does not exist, and if you are using SSAUDIT spreadsheet logging, reload the dbname.atx file. See How to Use Spreadsheet Update Logging. | |
Check the server and application logs to see where the calculation left off. See Viewing the Essbase Server and Application Logs. Decide whether to start the calculation over. Repeat the last calculation. | |
| |
Arithmetic data load (adding to or subtracting from values in the database) | If the database is set to committed access, reload the data. (The transaction has been rolled back.) If the database is set to uncommitted access, some of the data loaded, so if you reload all of the data, you receive incorrect results for the data values that loaded twice. Therefore, perform the following actions: |
The restructure is not complete. Delete the temporary restructure files: .pan, .inn, and .otn. Repeat the last operation that caused a restructure. |