Setting up Additional debug- TRACE: 32 in planning environment

Author: - Sanjay Purohit

How to setup Additional debug- TRACE: 32 in planning environment

Audience:  Hyperion Solution Architects, Hyperion Technical developer and administrator.

Recently I came across an issue with one of our client. And the issue had major impact on SLA. The entire budgeting process was affected. We were unable to make a move. We had to completely shut down the budgeting process due to this issue.

Whenever you see error/issue with an environment. The first place is to check log files. People don’t speak but log speaks. After looking at all the possible logs, I was unable to figure out the root cause.  However I had trust on my theory but logs did not speak much this time and I was wondering why!! What is wrong with my environment and why logs are not providing details as they should? I did some research and found out two articles on Oracle support:-

How to change the logging levels for Hyperion Products in 11.1.2.x (Doc ID 1158016.1)

How to Capture SQL Transactions in the Hyperion Planning Log File (Doc ID 841007.1)

Both the articles were easy to follow but I thought to create a step by step doc. The default log level is setup to NOTIFICATION: 1. The default is good enough to debug day to day issues/errors.  But my issue was not captured in this log. Then had to setup additional debug/TRACE: 32 logs. The TRCAE: 32 logs should provide the detail of client/server activities and should help you to debug the root cause. The purpose of this blog is to demonstrate step by step process to setup the TRACE: 32 log. However we will not cover any specific issue. TRACE:32 logs can be used to debug your environment. I will not advice to enable until you really need it.   he first step to setup from Planning and second is from server.

The first step is to setup from Planning web: Administration > Manage Properties > System Properties

- Add a new parameter called “PROFILING_ENABLED” and set it to “true”

- Add a new parameter called “DEBUG_ENABLED” and set it to “true”

 PS- Make sure the parameter is added to System Properties not Application properties.

Please refer URL to check the different log option such as NOTIFICATION and TRACE..

http://docs.oracle.com/cd/E17236_01/epm.1112/epm_install_troubleshooting/frameset.htm?ch03s01.html

http://docs.oracle.com/cd/E40248_01/epm.1112/epm_troubleshooting/frameset.htm?ch03s04s01.html

The second step is to make change on logging.xml file. The location of this file is

<Middleware_Home>\user_projects\domains\EPMSystem\config\fmwconfig\servers\Planning0 and you will see logging.xml file. Open this file to notepad ++ or any of text editor.

And go to the following line(s)

---------------------------------------------------------------------------------------------------------------------------

-<logger name="oracle.EPMHSP" useParentHandlers="false" level="NOTIFICATION:1"> <handler name="epmhp-planning-handler"/>

CHANGE TO:

---------------------------------------------------------------------------------------------------------------------------

-<logger name="oracle.EPMHSP" useParentHandlers="false" level="TRACE:32"> <handler name="epmhp-planning-handler"/>

Before making the change, you need to back up the file. The file should looks like

After making the change file should look like 

After making changes you must restart planning and check planning log. The log will speak more than what they should!!!!!

To setup the Essbase ODL log. Please refer to this URL

https://blogs.oracle.com/pa/entry/essbase_11_1_2_x