The Essbase Server Kernel considers the following errors fatal:
When the kernel encounters a fatal error, it shuts down and restarts, attempting to reinitialize itself and proceed with database recovery. When recovery begins, Essbase displays an error message similar to this one:
1080022 Reinitializing the Essbase Kernel for database dbname due to a fatal error...
This message is followed by other informational messages related to database recovery, such as this one:
1080028 Performing transaction recovery for database dbname during fatal error processing.
When you see such messages, the kernel has shut down and is attempting to restart. Check the Essbase Server log and determine whether Essbase issued a fatal error message just before it generated the reinitialization messages. See Using Essbase Server and Application Logs.
If the kernel did encounter a fatal error, you must usually restart any operation that was active at the time of the fatal error. If the operation was a calculation or a data load, you may be able to continue where the operation left off; check the Essbase Server log to see how far Essbase processed the operation. When in doubt, restart the operation. See What to Expect if a Server Interruption Occurs.
If the kernel did not encounter a fatal error, contact your software provider’s technical support to determine what caused the kernel to shut down and restart.
See Contents of the Essbase Server Log for descriptions of the contents of the Essbase Server log. See Essbase Server and Application Log Message Categories for information about identifying the component where the error occurred.