Overwriting or Retaining Existing Logs

By default, Essbase Server creates one or more exception logs each time the server shuts down abnormally. Subsequent exception logs are numbered sequentially; for example, if log00001.xcp exists, the next log is named log00002.xcp.

While you can use the EXCEPTIONLOGOVERWRITE TRUE configuration setting in essbase.cfg to overwrite the existing exception log file instead of creating a new log file, Oracle recommends that you use the default setting of FALSE. An abnormal shutdown may create multiple exception log files, and the first log file created during the shutdown is often the most descriptive. See Oracle Essbase Technical Reference.