Essbase Logs

Integration Services uses the log4j format, but all other Essbase components use ODL.

The log file for Integration Services activity is EPM_ORACLE_HOME/logs/eis/olapisvr.log. No manual archiving is required for olapisvr.log, which is a rolling log file.

The following table contains information about logs for Essbase components that use ODL.

Table 15. Essbase ODL Component Logs

ComponentDefault Log LocationLog File Name and Contents
Essbase ServerEPM_ORACLE_INSTANCE/diagnostics/logs/essbase/essbase_0, where 0 is an instance number
  • ESSBASE.LOG–Essbase Server activities and errors

  • ESSBASE_ODL.log–Essbase Server activities and errors

  • dataload_ODL.err–Data load and dimension build errors

  • log0000x.xcp–Errors that result when Essbase Server stops abnormally

  • leasemanager_server_HOSTNAME.log–Essbase Server Lease Manager information

  • leasemanager_essbase_HOSTNAME.log–Essbase Agent Lease Manager information

  • log00001.xcp–Errors that result when the agent stops unexpectedly

Note:

ESSBASE.LOG and ESSBASE_ODL.log contain the same information in different formats.

 
 
 
 
Specified through an essbase.cfg setting, which you can change through Essbase Administration Console or with a text editor.dbname_ODL.atx and dbname_ODL.alg, where dbname is specified through an essbase.cfg setting–Successfully completed spreadsheet update transactions

These are SSAUDIT log files. See “Monitoring Data, Applications, and Databases” in the Oracle Essbase Database Administrator's Guide and the Oracle Essbase Technical Reference.

 
EPM_ORACLE_INSTANCE/diagnostics/logs/essbase/essbase_0/application name
  • application name.LOG –Essbase application activities and errors

  • application name_ODL.log–Essbase application activities and errors

  • log00001.xcp–Errors that result when the application server stops unexpectedly

 
Administration Services

Note:

To enable console logging, in MIDDLEWARE_HOME/EPMSystem11R1/products/Essbase/eas/console/bin/admincon.bat, set the Java option parameter –DEAS_ CONSOLE_LOG to True.

MIDDLEWARE_HOME/user_projects/domains/EPMSystem/servers/EssbaseAdminServices0/logs
  • easserver.log–Administration Services Server activity

  • EssbaseAdminServices0.log–Administration Services Web application activity

 
 
Provider ServicesMIDDLEWARE_HOME/user_projects/domains/EPMSystem/servers/AnalyticProviderServices0/logs
  • AnalyticProviderServices0.log–Provider Services Web application activity

  • apsserver.log–Provider Services activity

 
 
Essbase StudioEPM_ORACLE_INSTANCE/diagnostics/logs/upgradesEssbaseStudioServer.log–Essbase Studio upgrade activity  
Essbase staging tool The working directory essStaging.log–Errors that result when the staging tool (essStage.bat or essStage.sh) prepares configuration and security information, data, and applications for file transfer during an upgrade

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

 
Essbase rehosting tool EPM_ORACLE_INSTANCE/diagnostics/logs/essbaseEssbaseRehost.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 Enterprise Performance Management System Installation and Configuration Guide.

 
Essbase Security ClientEPM_ORACLE_INSTANCE/diagnostics/logs/essbaseSecurity_client.log–Tracking of EPM Systemcomponent and CSS communications with native provider

Also records the JDBC configuration from registry in this log file for any binds with native providers.

 
OPMNEPM_ORACLE_INSTANCE/diagnostics/logs/OPMN/opmn
  • opmn.log–Information about when Essbase starts, stops, and how many stop and start retry attempts are made

  • 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.

 
 
 
 
EssbasePing.log– OPMN Forward Ping information 
Essbase PluginEPM_ORACLE_INSTANCE/diagnostics/logs/essbase/lcmessbaseplugin.log– Information about artifacts listing, migration (import/export) of Essbase artifacts, time taken for artifact listing and artifact migration