Calc Manager Rules deployment issue with EPMA

Its been a long time that we are struggling with EPMA, Calc Manager and Capex.

We wanted to use Capex with our EPMA Planning application.

So we created a new application in EPMA with all the custom dimensions (Renamed Entity to Cost Center, Year to Years, added some custom members)and tried to initialize Capex and during the initialization it failed with some errors in log file.

Most of the errors were due to the fact that some of the in-built forms of Capex were not created. So we just ignored the error and went ahead with the Application.

But then came the main problem, when we tried to deploy a custom calc manager rule it gave an error which says “host parameter is null”

So we spent all our effort in looking for places where Calc Manager is storing the host parameter. (which didn’t help at all)

Then we tried to deploy the entire application from Calc Manager and got an error saying “Application needs to be in deployed state”!!!!!!!

We were clueless and then decided to recreate the application – this time without any custom dimensions and without any renaming (Entity as Entity, Year as Year).

This time we got rid of the errors related to Capex Webforms, however got another error (no idea what this was regarding)

[Mar 22, 2011 3:59:14 AM]: Parsing Application Properties…

[Mar 22, 2011 3:59:14 AM]: Application Configuration Properties…
[Mar 22, 2011 3:59:14 AM]: Parsing Dimensions info…
[Mar 22, 2011 3:59:14 AM]: Creating Application …
[Mar 22, 2011 3:59:26 AM]: Registering the application to shared services…
[Mar 22, 2011 3:59:27 AM]: Initializing CAPX…
[Mar 22, 2011 3:59:47 AM]: Error Failed to enable capex during initialization.  Please see log for details[Mar 22, 2011 3:59:47 AM]: Error Content is not allowed in prolog.
org.xml.sax.SAXParseException: Content is not allowed in prolog.
                at org.apache.xerces.parsers.AbstractSAXParser.parse(Unknown Source)
                at com.hyperion.calcmgr.xml.XmlUtil.parseXML(
                at com.hyperion.calcmgr.xml.XmlImport.parse(
                at com.hyperion.calcmgr.xml.XmlImport.parse(
                at com.hyperion.planning.calcmgr.deploy.HspCalcMgrDeployer.deploy(Unknown Source)
                at com.hyperion.planning.calcmgr.deploy.HspCalcMgrDeployer.deploy(Unknown Source)
                at com.hyperion.planning.HspCalcMgrRuleLoader.load(Unknown Source)
                at com.hyperion.planning.utils.HspCXInitializer.initialize(Unknown Source)
                at com.hyperion.planning.appdeploy.HspSaxParsedAppDefinition.deployAppFromXML(Unknown Source)
                at com.hyperion.planning.appdeploy.HspAppDefinition$ Source)

But soon we got to know that this is something related to Calc Manager, because we were not able to deploy any existing rules or new rules.


After lot of experiments (I still remember the permutation and combination problems that I used to solve and those were very helpful here) like creating the application in Classic and then migrate to EPMA, then tried different combinations in EPMA, which didn’t yield any results.

At last we created a Classic Application with all default members and used Business Rules as Calculation mode and initialized Capex, which was successful (ray of hope!!!!!). Made the custom changes (Entity to Cost Center, Year to Years) and then Migrated it to EPMA which was successful. (Only issue was we named Capex cube as CapPlan, but it is still showing as Capex).

We tried to then deploy a new Calc Manager rule and viola it was successful.

Now the investigation started why it was failing before and as usual we ended up in the relational tables (but this time it was the EPMA tables).

If you take a look at the EPMA tables there is one table called OR_OBJECT 

In this there is a column called C_OBJECT_STATUS.

EPMA/Calc Manager looks at the values in here if its a deployed application or not.

  • A value of 2 here indicates that the corresponding application is deployed
  • A value of 8 indicates that the corresponding application is non deployed.
  • A value of 4 indicates that the corresponding application is in a transition state.
Our application were we were having an issue was tagged as 8 and only we had to do was change it to 2.

Hope this helps…..

About Celvin Kattookaran

I’m an EPM Consultant, my primary focus is on Hyperion Planning and Essbase. Some of you from Hyperion Support team might recognize me or have seen my support articles, I was with the WebAnalysis Support Team. I'm an Independent Consultant with “Intekgrate Corporation” based out of Aurora office. I’m from God’s Own Country (Kerala, India), lived in all southern states of India, Istanbul and Johannesburg (and of course United States). I’m core gamer :) and an avid reader. I was awarded Oracle ACE Director for my contributions towards EPM community.

Leave a Reply

This site uses Akismet to reduce spam. Learn how your comment data is processed.

0 thoughts on “Calc Manager Rules deployment issue with EPMA