Monthly Archives: July 2013

HFM Redeploy from EPMA – Unspecified Error

When redeploying an Oracle Hyperion Financial Managemenent (HFM) application from Oracle Enterprise Performance Management Architect (EPMA), the deploy operation can fail and return a very unhelpful error message “Unexpected Error”. Although not immediately obvious, this error usually indicates there is an issue within the outline however, if the application has data, it may simply be that the data is being reorganized.

The screen shot below shows the EPMA summary:

130726_Seismi_HFM Redeploy from EPMA_1

The EPMA error log only is not much help either.  It returns the following information:

Error Reference Number: {5AD32CB5-7E26-4A48-A98C-5DC4870698E7}

Num: 0x80004005;Type: 0;DTime: 05/07/2013 13:54:20;Svr: UK1WHYPAPP11Q;File: CHsvMetadata.cpp;Line: 1056;Ver: 11.1.2.1.600.3779;

Num: 0x80004005;Type: 0;DTime: 05/07/2013 13:54:20;Svr: UK1WHYPAPP11Q;File: AgentHelper.cpp;Line: 1237;Ver: 11.1.2.1.600.3779;

Num: 0x80004005;Type: 0;DTime: 05/07/2013 13:54:21;Svr: UK1WHYPAPP11Q;File: CHfmAwbAgent.cpp;Line: 665;Ver: 11.1.2.1.600.3779;

To solve this, in the deploy screen uncheck the “Check Referential Integrity” option and check the “Full Deploy”.

130726_Seismi_HFM Redeploy from EPMA_2

Changing these options should allow you to deploy the HFM Application.

WARNING – Deploying without the option “Check Referential Integrity” means that data can be affected. Before doing so, be sure you have a backup of the application and a point of comparison to review any changes.

 

Tagged , , ,

Estimating the Costs of implementing Oracle Hyperion DRM

Estimating the cost of an Oracle Hyperion Data Relationship Manager (DRM) implementation can be difficult. This blog will highlight the areas and risks you should consider.

When developing the business case for the costs can broadly be separated into 3 distinct areas:

  1. Software and licensing costs;
  2. Hardware costs; and
  3. Implementation costs.

The first of these can be difficult to understand as you need to have some indication of how many nodes will be required for you solution.  This information is not often available until after implementation as the agreed design will affect the number of nodes required.

The second, hardware costs, can be identified relatively easily using the software vendor’s prior experience.

The main issue comes with estimating implementation costs.  At the point at which the decision is being taken to purchase the relevant software, it is unlikely that you have expertise already on the site. You therefore have a few options available. In some instances we have seen organisations ask for an estimate from the software vendor.  This can be a huge mistake for two reasons. The software provider is unlikely to have a detailed understanding of your requirements and in addition they are conflicted as they are trying to sell you the software.  They have a vested interested in trying to minimise the estimate to ensure you buy the software.

Alternatively, you may be tempted to use a formula to try and determine the final implementation costs. This approach is fine as long as the formula used is not arbitrary, and is based on a good understanding of both the requirements and the technology.

In our opinion, the best method of understanding the implementation costs is to approach an independent organisation that has demonstrable experience of implementing the same software in a similar environment.  Most consulting organisations should be willing to give you guidance for free to help you understand expected costs.  In some instances, this may require more analysis time to understand the requirement, but surely a minimal cost upfront, to avoid a huge under, or over, estimation is a necessary investment?

If you need any help understanding the potential implementation costs of Oracle Hyperion DRM can help your organisation please do not hesitate to contact us.

Tagged , , , ,