Troubleshooting Essbase Errors

In This Section:

Understanding Fatal Error Handling

Recovering from Dense Restructure Failures

Recovering from Sparse Restructure Failure

Synchronizing Member Names in Report Scripts and Database Outlines

Handling Essbase Server Problems When Running Multiple Reports

References

Understanding Fatal Error Handling

The Essbase Server Kernel considers the following errors fatal:

  • One or more control fields have unexpected or inconsistent values.

  • The kernel detects data corruption.

  • The kernel cannot perform an operation that is necessary to ensure data integrity (for example, disk space is insufficient).

  • The kernel encounters a condition that can lead to data corruption.

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.

Recovering from Dense Restructure Failures

If an error or system failure occurs while Essbase is restructuring, it probably will occur during step 2 in the procedure Dense Restructures.

  To recover from a failure during step 2 of Dense Restructures:

  1. Delete the temporary files, to free disk space and to avoid conflicts during the next database restructure.

  2. Restart the database.

  To recover from a failure during step 1, step 3, or step 4 of Dense Restructures:

  1. Review the disk directory and determine how far restructuring has progressed.

  2. If all but step 4 is complete, rename the temporary files to the correct file names.

Recovering from Sparse Restructure Failure

If a system failure occurs during any step of a sparse restructure, you can recover by restarting the database.

Synchronizing Member Names in Report Scripts and Database Outlines

When you run a report, ensure that the member names in the report script match the member names in the database outline. An error displays whenever the Report Extractor cannot find a matching member name; you must correct the name in the report script before the report continues processing.

Handling Essbase Server Problems When Running Multiple Reports

Your server computer may freeze if you try to run more reports in parallel than you have assigned server thread resources.

If you are running multiple report scripts and your server freezes, check the value of the configuration file setting SERVERTHREADS in the essbase.cfg file on the server. At least one thread should exist for each report running. For example, if you are running 22 reports, the value for SERVERTHREADS should be at least 22.

References

Chapters related to partitions, currency conversion, and data load have basic troubleshooting information in the relevant chapters.

For information about restoring from backups, see the Oracle Hyperion Enterprise Performance Management System Backup and Recovery Guide.

For information about specific error messages, see Oracle Essbase Error Message Reference.

For information about error and exception logs, see Using Essbase Logs.