What to Expect if a Server Interruption Occurs

Table 160 lists types of Essbase Server interruptions and their results:

Table 160. Essbase Recovery Handling

Interruption

Result

  • Power loss on server

  • Operating system crash

  • Server stopped with Ctrl+C keys

Essbase Server stops. When you restart the server, Essbase recovers the database.

  • Operation cannot complete because of system limitations

  • Memory shortage

  • Out of disk space

  • Application stopped with Ctrl+C keys

Essbase performs fatal error handling. You may need to allocate more memory or disk space and restart the server.

Server crash

Essbase Exception Manager creates an error log of type .xcp. Server stops. When you restart the server, Essbase recovers the database.

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

Type of Request

Recommended Action

Lock

(for spreadsheet update)

Issue the lock command again.

Send

(spreadsheet update)

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.

Calculation

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.

Data load

Perform an action:

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:

  • Clear the database.

  • Restore the database to its preload state.

  • Rerun the load.

Restructure

The restructure is not complete. Delete the temporary restructure files: .pan, .inn, and .otn. Repeat the last operation that caused a restructure.

Note:

If the UPDATECALC parameter is set to FALSE, Essbase recalculates the entire database if an interruption occurs during a calculation. (The default value of the parameter is TRUE.)