Essbase Logs

The following table contains information about Essbase product family logs that use ODL format:

Integration Services does not use ODL. See Integration Services Logs.

Note:

For more information about analyzing Essbase logs, see the Oracle Essbase Database Administrator's Guide.

Table 10. Essbase Logs

Log LocationLog Name and Description

Essbase:

EPM_ORACLE_INSTANCE/diagnostics/logs/essbase/essbase_0

  • Essbase Server log:

    ESSBASE_ODL.log

    Essbase Server activities and errors

  • Essbase application log:

    /app/APPLICATION_NAME_ODL.log

    Essbase application activities and errors

  • Data load log:

    dataload_ODL.err

    Data load and dimension build errors

  • SSAUDIT log files:

    dbname_ODL.atx and dbname_ODL.alg

    Successfully completed spreadsheet update transactions. These are SSAUDIT log files; file name and location are specified through an essbase.cfg setting. See “Monitoring Data, Applications, and Databases” in the Oracle Essbase Database Administrator's Guide and the Essbase Technical Reference.

  • Exception log:

    log0000x.xcp

    Errors that result when Essbase Server stops abnormally

  • Essbase Server Lease Manager log:

    leasemanager_server_HOSTNAME.log

    Essbase Server Lease Manager information

  • Essbase Agent Lease Manager log:

    leasemanager_essbase_HOSTNAME.log

    Agent Lease Manager information

For more information on how to use these logs to troubleshoot Essbase failover problems, see Essbase Failover Logs.

Essbase Studio upgrade log: EPM_ORACLE_ INSTANCE/diagnostics/logs/upgrades 
EssbaseStudioServer.log
–Essbase Studio upgrade activity
Essbase staging tool:

The working directory

essStaging.log–Errors that result when the staging tool (essStage.bat | sh prepares configuration and security information, data, and applications for file transfer during an upgrade.

For more information about the stating tool, see “Preparing Essbase Data for Upgrading” in Chapter 5, “Upgrading EPM System Products,” in the Oracle Hyperion Enterprise Performance Management System Installation and Configuration Guide.

Essbase Server rehosting log:

EPM_ORACLE_INSTANCE/diagnostics/logs/essbase

EssbaseRehost.log–Errors recorded by the Essbase rehosting tool when it rehosts Essbase connections during an upgrade.

For more information about Essbase Server rehosting, see “Rehosting Essbase Server” in Appendix B, “Rehosting Foundation Services Web Application and Essbase Server,” of the Oracle Hyperion Enterprise Performance Management System Installation and Configuration Guide.
Essbase Security Client log:EPM_ORACLE_INSTANCE/diagnostics/logs/essbaseSecurity_client.log—Tracking of EPM System component and CSS communications with native provider. Also records the JDBC configuration from registry in this log file for any binds with native providers.
Oracle Process Manager and Notification Server logs: EPM_ORACLE_INSTANCE/diagnostics/logs

  • OPMN server log: 

    /OPMN/opmn/opmn.log

    Diagnostic information that the OPMN server prints for various operations performed against a managed component (Essbase). This log contains information about when Essbase starts, stops, and how many retry attempts are made to start and stop.

  • Essbase console log: 

    /OPMN/opmn/console~ESSBASE_CLUSTER_NAME~ESSBASE_PROCESS_TYPE~AGENT~1.LOG

    All console messages are directed to a file that is called the "console" output file for a managed process, in this case, Essbase. Essbase often writes the same log file entries to Essbase.log and stdout; therefore there might be duplicate entries in Essbase.log and this console log file.

  • OPMN Forward Ping log:

    /OPMN/opmn/EssbasePing.log

    OPMN Forward Ping information

For more information on how to use these logs to troubleshoot Essbase failover problems, see Essbase Failover Logs.

Essbase Plugin logs:

MIDDLEWARE_HOME/user_projects/domains/domain name/servers/managed server name/logs/essbase/lcm

essbaseplugin_ODL.log—Log statements related to the LCM artifact listing

Administration Services:

MIDDLEWARE_HOME/user_projects/domains/domain name/servers/managed server name/logs

Note:

To enable console logging, in admincon.lax, set the Java option parameter –DEAS_CONSOLE_LOG. to True.

  • easserver.log—Administration Services Server activity

  • EssbaseAdminServices0.log—Web application activity

Essbase Studio:

EPM_ORACLE_INSTANCE/diagnostics/logs/esbstudio

server.log—Essbase Studio server activity

Provider Services:

MIDDLEWARE_HOME/user_projects/domains/domain name/servers/managed server name/logs

  • AnalyticProviderServices0.log—Web application activity

  • apsserver.log—Provider Services activity