1. Configuration Reference for Oracle Essbase
  2. Essbase Configuration Settings
  3. Config Settings List
  4. EXCEPTIONLOGOVERWRITE

EXCEPTIONLOGOVERWRITE

This configuration setting determines whether Essbase overwrites the existing exception log or creates a new exception log.

Syntax

EXCEPTIONLOGOVERWRITE TRUE | FALSE

  • TRUE—Essbase overwrites the existing exception log.

  • FALSE—Essbase keeps the existing exception log and creates new logs for every exception. This is the default.

Description

This setting determines whether Essbase overwrites existing exception log data or creates a new log for each exception condition. The exception log name is normally log00001.xcp.

When EXCEPTIONLOGOVERWRITE is FALSE:

  • Essbase creates a new log instead of overwriting the previous one.

  • Subsequent logs are numbered sequentially; for example, if log00001.xcp exists, the next log has the file name log00002.xcp, and the next has log00003.xcp, and so on.

The Essbase exception handler writes the information into the exception log on the local disk in a text file as follows:

  • If the server crashed, the log is written in the directory pointed to by <Essbase Path>.

  • If the application crashed and the application name is unknown, the log is written into the app subdirectory under the directory pointed to by <Application Directory>.

  • If the application crashed and the application name is known, but the cube name is unknown, the log is written to the appropriate application directory; for example, <Application Directory>/app/app1.

  • If the application crashed and both the application and cube names are known, the log is written to the appropriate cube directory; for example, <Application Directory>/app/app1/cube1.

See Environment Locations in the Essbase Platform for information about directory locations in Essbase.

Example

EXCEPTIONLOGOVERWRITE FALSE