You can specify whether to have Essbase Server messages written to the Essbase Server log (EPM_ORACLE_INSTANCE/diagnostics/logs/essbase/essbase_0/essbase.log), the Essbase Server Console, or both.
Log levels:
Information messages, such as notification of a user action or information about an application or database
In the following example, the admin user logged out.
[Sun Oct 21 16:00:55 2001]Local/ESSBASE0///Info(1051037) Logging out user admin, active for 144 minutes
Warning messages, such as a notification that an operation was not completed
Warnings often follow errors. In the following example, the rename operation did not complete because of a previous error in the log.
[Fri Nov 02 13:38:14 2001]Local/ESSBASE0///Warning(1051003) Error 1051031 processing request [Rename Application] - disconnecting
Error messages, such as trying to perform an action that Essbase Server cannot perform
In the following example, the rename operation failed because the application name already existed.
[Fri Nov 02 13:38:14 2001]Local/ESSBASE0///Error(1051031) Application Testing already exists
Debug messages, such as OPMN ping messages.
Table 143 lists the configuration settings that you specify in the essbase.cfg file to determine what types of messages Essbase Server writes to the Essbase Server log or displays to the Essbase Server Console. If you change an essbase.cfg setting, restart Essbase Server to apply the change.
Table 143. List of Essbase Server Message Configuration Settings