Determines whether Essbase overwrites the existing exception log or creates a new exception log.
EXCEPTIONLOGOVERWRITE TRUE | FALSE
TRUE—Essbase overwrites the existing exception log.
FALSE—Essbase keeps the existing exception log and creates new logs for every exception. The default value is FALSE.
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 ESSBASEPATH; for example, D:\essbase
If the application crashed and the application name is unknown, the log is written into the APP subdirectory under the directory pointed to by ARBORPATH; for example, D:\essbase\app.
If the application crashed and the application name is known, but the database name is unknown, the log is written to the appropriate application directory; for example, D:\essbase\app\app1.
If the application crashed and both the application and database names are known, the log is written to the appropriate database directory; for example, D:\essbase\app\app1\db1.
When an exception occurs, Essbase displays and logs an error message telling users the path to the exception log.
Essbase logs errors to the Essbase Server log or to the application log, depending on where the error occurs.
EXCEPTIONLOGOVERWRITE FALSE
Oracle Essbase Database Administrator's Guide