Essbase - Checking Error Log

About

If a data load or dimension build fails, the error log can be a valuable debugging tool. See Understanding and Viewing Dimension Build and Data Load Error Logs.

Articles Related

Log files

• From EAS client, Hyperion_Home\products\Essbase\eas\client
• Using maxl, you should have an error file defined in the script.
• For Essbase, hyperion_Home\logs\essbase\essbase.log
• For an application, ex with sample application: hyperion_home\logs\essbase\app\Sample\Sample.log

No error log

If there is no error log, check whether the following conditions exist:

• The person running the data load set up an error log.

By default, when using a rules file, Essbase creates an error log.

• The data source and Essbase Servers are available.

See Verifying that Essbase Server Is Available and Verifying that the Data Source Is Available

• Essbase Server crashed during the data load.

If so, you probably received a timeout error on the client. See Essbase - Stopping Data Loads or Dimension Builds / Recovering from a server crash.

• The application log exists. See Essbase Server and Application Logs.

Empty error log

If the error log exists but is empty, Essbase does not think that an error occurred during loading. Check whether the following conditions exist:

• The rules file contains selection or rejection criteria that rejected every record in the data source.

See Essbase - Loading a Subset of Records from a Data Source.

• The rules file validates properly.

See Requirements for Valid Data Load Rules Files and Requirements for Valid Dimension Build Rules Files.