EXCEPTIONLOGOVERWRITE

Parameters

EXCEPTIONLOGOVERWRITE determines where Hyperion Essbase writes application and server exception error log data.

Syntax

EXCEPTIONLOGOVERWRITE TRUE | FALSE

TRUE	Causes Hyperion Essbase to overwrite the existing error log.
FALSE	Causes Hyperion Essbase to keep the existing error log and create new logs for every exception. The default value is FALSE.

Description

EXCEPTIONLOGOVERWRITE determines whether Hyperion Essbase overwrites existing exception error log data or creates a new file for each exception condition.

Hyperion Essbase maintains separate error log files for application and server errors. Server log files are stored in the directory pointed to by ARBORPATH, and application log files are stored in the ARBORPATH \APP directory, or in the database directory.

The Exception Error Log report file name is normally log00001.xcp. The ExceptionLogOverwrite parameter in the ESSBASE.CFG file controls whether Hyperion Essbase overwrites the log file.

When ExceptionLogOverwrite is FALSE:

• Hyperion Essbase creates a new file instead of overwriting the previous one.
• Subsequent reports are numbered sequentially; for example, if log00001.xcp exists, the next report has the file name log00002.xcp, and the next has log00003.xcp, and so on.

Example

EXCEPTIONLOGOVERWRITE FALSE 

The Hyperion Essbase exception handler writes the information into the Exception Error Log report on the local disk in an ASCII file as follows:

• If the server crashed, the report is written in the directory pointed to by ARBORPATH; for example,

D:\ESSBASE

• If the application crashed and the application name is unknown, the report 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 report 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 report is written to the appropriate database directory; for example,

D:\ESSBASE\APP\APP1\DB1.

Notes

• When an exception error occurs, Hyperion Essbase displays and logs an error message telling users path information for the error log file.
• Hyperion Essbase logs errors to the server (agent) error file or to the application (server application) file, depending on where the error occurs.

See Also

The Hyperion Essbase Database Administrator's Guide.

Copyright (c)1991-2000 Hyperion Solutions Corporation. All rights reserved.