Sunday, May 18, 2014

Hyperion Public Sector Planning and Budgeting-Right click menu does not work

Author: - Sanjay Purohit

Audience:  Hyperion Solution Architects and Hyperion Business users
The Hyperion world is really strange and it teaches lesson every day.  We were about to start our budget cycle and suddenly came across an issue. The issue was pretty basic but I had to spend almost two to three days to debug it. This issue remind me phrase “Making a mountain out of a molehill”.  The issue was with almost all the business users because they did not follow guidelines. Our users were not able to open the data form with right click menu. This was Hyperion Public Sector Planning and budgeting (PSPB) application and PSPB heavily relies on out of box right click functionality. I enabled trace: 32 log and put planning in debug mode but nothing to read in log. Log did not tell me much. I was stunt but I was lucky because this functionality was working for one business user. I took this users ID as role model and compared with few users access, security and planning PREFERENCES.  These users had selected “Remember selected page members” from planning preference and other did not.


REASON
Most of supplement/dependent data form in PSPB uses member from primary data form. Please see the example below.  Right click from one data form should land to another data form with same member selection. “Use Members on Forms does not work unless Remember selected page members is checked from preferences.” As per admin guide

Right click on Manage all position data form (PSPB)
This should land to you another data form


Now if we notice- Few of dim-members such as Entity, Position, Scenario, and Version are passed as context from “Manage all Position” to  “Edit Position details form “  This functionality does not work if preference are not setup according to Oracle guideline.


RESOLUTION
The fix of this problem is pretty simple. User needs to “Remember selected page members” to “Yes”.








This should solve the problem. Oracle Description of solution is “If a business rule has run-time prompts and Use Members on Forms is selected, the default member on the run-time prompt window matches the current member in the page and the POV axes of the open data form. Use Members on Forms does not work unless Remember selected page members is checked. See About Launching Business Rules.”

Saturday, May 17, 2014

Unable to obtain lock for Registry database. Existing lock on host

Author: - Sanjay Purohit

Audience:  Hyperion Solution Architects and Hyperion Database Administrator
During installation/configuration of Hyperion EPM on my server, I came across a small configuration hurdle so I thought to share with you. My installation was single server installation and should not have caused me any trouble but it did!!!! I wanted to configure all the components on different schemas therefore I had to run configurator several times and I encountered an error.

 “Unable to obtain lock for Registry database. Existing lock on host ----created by -----.  Do you want proceed? “



This is pretty common error you can get during EPM configuration. We will cover step by step solution of this error in this posting. 
reason
Each run of EPM configurator creates a record/lock on EPM_REGISTRY_LOCK table on share service schema. This lock gets deleted after configuration is done but sometime it does not and prevents new record creation.


resolution

Database administrator should login to the Shared Services schema and delete created lock. After deleting the lock/record. You should be able to run configurator. 




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

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