How to Troubleshoot Hyperion logs and its path [Essbase/Planning logs location]

Welcme to LIT,

In this post we are going to see how to troubleshoot the issues using the logs and you can see the logs location for Essbase and Hyperion Planning.

·         Start a problem log:

  

1.    The most useful habit to develop during issue resolution is to start a detailed log about the issue.

2.    Problems can take days or weeks to resolve and require trying hundreds of different prospective resolution attempts.

3.    It is easy for a “small” problem to become a long winded issue.

4.    If the problem log is created initially, all the important details can be captured.

5.    Additionally, it is much easier to bring others up to speed (management) and create support tickets when all of the information is documented.

6.    This log should include the error as the end user sees it, the error from any logs you are able to capture, screenshots, timestamps, and things that you have tried along with the results.

  

·         Reproduce the issue:

   

1.    The first thing to find out is whether the issue is reproducible.

2.    It is very difficult to solve an issue that is not reproducible. Many errors are simply ‘glitches’ and may have been caused by a very improbable event, such as a database hiccup.

3.    Such a problem may never produce itself again. Consequently, an initial step toward resolution is to restart the Oracle EPM services to bring them back into a ‘known state’.

4.    If the problem is not immediately reproducible after the restart, go back to the problem log and record everything you can.

5.    This type of issue will need to be profiled over a period of time to try and discover patterns if it occurs again.

  

·         Numerous logs:

1.    Once it is discovered that the issue is not a simple glitch, it is time to start digging.

2.    The first place to track down the cause of an issue is in the logs.

3.    The logs come in various forms. Here is a general breakdown of the log types:

  Logs and its location:

·         Essbase Server:

Ø  Location: EPM_ORACLE_INSTANCE/diagnostics/logs/essbase/essbase_0, where 0 is an instance number

·         Application location:

Ø  EPM_ORACLE_INSTANCE/diagnostics/logs/essbase/essbase_0/application name

ØAdministration Services: 

MIDDLE WARE_HOME/user_projects/domains/EPMSystem/servers/EssbaseAdminServices0/logs

Ø  Provider Services: MIDDLEWARE_HOME/user_projects/domains/EPMSystem/servers/AnalyticProviderServices0/logs

Ø  Essbase Studio:EPM_ORACLE_INSTANCE/diagnostics/logs/EssbaseStudio

Ø  Essbase StudioConsole: EPM_ORACLE_HOME/products/Essbase/EssbaseStudio/Console/workspace/.metadata

Ø  Essbase SecurityClient: EPM_ORACLE_INSTANCE/diagnostics/logs/essbase/essbase

Ø  OPMN: EPM_ORACLE_INSTANCE/diagnostics/logs/OPMN/opmn( opmn.log—Information about when Essbase starts, stops, and how many stop and start retry attempts are made)

Ø  Essbase Plugin:

EPM_ORACLE_INSTANCE/diagnostics/logs/essbase/lcm( Information about artifacts listing, migration (import/export) of Essbase )

 

·         Planning:

ØDefault Location: C:/MIDDLEWARE_HOME/user_projects/domains/EPMSystem/servers/Planning0/logs

  

Ø  EPM_ORACLE_INSTANCE/diagnostics/logs/planning

  

 ·         Log file name and contents:

    

Ø  UserProvisionSync.log—Security refresh information, such as provisioning or “user not found” issues

Ø  Planning utility logs—A log for each Planning utility

PlanningAppUpgradeLog_application_name.txt—An upgrade log for each upgraded Planning application

Regards,

Lead Innovative Technologies

Contact:+91-7207118899,+91-9966661460.

Email:Leadinnovativetechnologies@gmail.com