Here are the product-specific log files, their locations, and their purposes: Most monitoring or troubleshooting activities

will lead down one of, or bother of the following folder paths: C:\Oracle\Middleware\user_projects\epmsystem2\diagnostics\logs And/Or C:\Oracle\Middleware\user_projects\domains\EPMSystem\servers\{MANAGEDSERVERNAME}\logs

Unfortunately there is some duplication and more often than not, there will be multiple log files which require attention when focusing on one activity / error.

Essbase Server Logs: 11.1.1.3 Location \Hyperion\Logs\Essbase

11.1.2.1 Location 1 C:\Oracle\Middleware\user_projects\epmsystem2\diagnostics\logs\essbase\essbase_0 ESSBASE.log This is the Essbase server log file as it has traditionally been. Only the location has changed. ESSBASE_ODL.log The is the Essbase Server log file in a different format, which also trims itself at around 1GB and archives itself. * Both the ESSBASE.log and ESSBASE_ODL.log files record the same information, which is Essbase Server activities and errors. Log0000x.xcp This log records errors if and when the Essbase Server stops abnormally. Log00001.xcp This log records errors if and when the Essbase Agent stops abnormally.

11.1.2.1 Location 2 C:\Oracle\Middleware\user_projects\epmsystem1\diagnostics\logs\opmn Opmn.log This log records information about when Essbase starts, stops, and how many stop and start retry attempts are made.

Essbase Application Logs: 11.1.1.3 Location \Hyperion\logs\essbase\app\{appname}

11.1.2.1 Location C:\Oracle\Middleware\user_projects\epmsystem2\diagnostics\logs\essbase\essbase_0\app\{appname} {appname}.log This is the Essbase application log as it has traditionally been. Only the location has changed. {appname}_ODL.log The is the Essbase Application log file in a different format, which also trims itself at around 1GB and archives itself.

Essbase Administration Services Logs: 11.1.1.3 Location \Hyperion\logs\eas\

11.1.2.1 Location 1 C:\Oracle\Middleware\user_projects\domains\EPMSystem\servers\EssbaseAdminServices0\logs Easserver.log This log records Administration Services Server activity. EssbaseAdminServices0.log This log records the Administration Services Web Applications activity.

11.1.2.1 Location 2 C:\Oracle\Middleware\user_projects\epmsystem1\diagnostics\logs\services HyS9eas-sysout.log Records EAS Server activity, this log duplicates what is found in the EssbaseAdminServices0.log above. HyS9eas-syserr.log Records EAS Server errors

Provider Services Logs: 11.1.1.3 Location \Hyperion\logs\aps\

11.1.2.1 Location 1 C:\Oracle\Middleware\user_projects\domains\EPMSystem\servers\AnalyticProviderServices0\log AnalyticProviderServices0.log Records Provider Services Web Application activity Apsserver.log Records Provider Services activity

11.1.2.1 Location 2 C:\Oracle\Middleware\user_projects\epmsystem1\diagnostics\logs\services HyS9aps-sysout.log Records APS Server activity, this log duplicates what is found in the AnalyticProviderServices0.log above. HyS9aps-syserr.log Records APS Server errors

Planning Logs: 11.1.1.3 Location \Hyperion\logs\Planning

11.1.2.1 Location 1 C:\Oracle\Middleware\user_projects\domains\EPMSystem\servers\Planning0\log Planning0.log Records Planning Web Application activity Apsserver.log Records Planning activity

11.1.2.1 Location 2 C:\Oracle\Middleware\user_projects\epmsystem1\diagnostics\logs\Planning HyS9Planning-sysout.log Records Planning Server activity, this log duplicates what is found in the Planning0.log above. HyS9Planning-syserr.log Records Planning Server errors UserProvisionSync.log Records security refresh information, such as User not found issues. This log should be used to troubleshoot synchronization issues between Planning and Shared Services. Planning utility logs can be found here as well.

PlanningAppUpgradeLog_application_name.txt This is an upgrade log for each upgraded Planning Application

Foundation Services Logs: 11.1.1.3 Location \Hyperion\logs\SharedServices9

11.1.2.1 Location 1 C:\Oracle\Middleware\user_projects\domains\EPMSystem\servers\FoundationServices0\log FoundationServices0.log Records Provider Services Web Application activity Apsserver.log Records Provider Services activity

11.1.2.1 Location 2 C:\Oracle\Middleware\user_projects\epmsystem1\diagnostics\logs\services HyS9FoundationServices-sysout .log Records APS Server activity, this log duplicates what is found in the FoundationServices0.log above. HyS9FoundationServices-syserr.log Records Foundation Services Server errors

Consolidating the EPM Log Files It is possible to consolidate all of the EPM log files on each server to one place. Oracle has provided a tool called ziplogs.bat. The tool will find all of the log files on the server where it is launched and compile them into a zipped output. Within the compressed output, the log files exist under their original folder structures. This can be a very useful tool when used for the right purpose. However, the tool does fall short in some areas. For instance, once the tool is run, the resulting zip file of logs is static. This would not be particularly helpful for troubleshooting purposes when we typically like to tail a log file or watch it dynamically update. However, an interesting use of the tool can be to learn where all of the log files live since the ziplogs tool preserves the original folder structure. Another scenario in which the tool can be advantageous is during backups. While it is not perfect, it is certainly useful and can be applied to many creative purposes.

Heres how to run the script: Log in to the EPM Server using the administrator account used to install/configure EPM.

Open Windows Explorer. Navigate to \Oracle\Middleware\user_projects\epmsystem1\bin. Run the ziplogs.bat script. The zip file will be written to the \Oracle\Middleware\user_projects\epmsystem1\diagnostics\ziplogs directory.

Wrap-Up and Additional Information More information can be found in the following Oracle Document ID 1464973.1 (Login required).http://bit.ly/Qy8ia0 Also, refer to the Oracle Hyperion Enterprise Performance Management System Installation and Configuration Troubleshooting Guide which can be found here in HTML version (loads faster than PDF): http://bit.ly/TCbYvs. Try searching for things like Financial Reporting Logs.

We hope that this review of the EPM 11.1.2.1 logs has been helpful and will shave valuable time from your monitoring and troubleshooting activities so that you can reclaim your day.

For more information about this or any of our other blog entries, e-mail us at Info@InnovusPartners.com.