Possible Agent Error messages- Part 1

In this post i had tried to put some of the error’s that we generally face with Possible problem and possible solution :-

ERROR – 1023057 – Cannot replace partition defn file while there are other active users on database [objectName]

Possible solutions — a) We need to Kill all the sessions that are there .(Best solution) b) This error is automatically corrected in next flip flop or we should manually change the partion for this.


1051002 Unrecognized command: command name

Possible Problems There is most likely a version mismatch between Analytic Server and a client.

Possible Solutions Make sure the versions of your Analytic Server and client are compatible.


***** For detail post , Please go to www.knowhyperion.com *****


Essbase Excel Client Install Files is 3Gb+, what an headache ?

I love Oracle to death but on some things, it bugs me. I have been trying to get somewhere with Oracle for about a month, and the issue surrounds the installation of the Excel 2007 Essbase client (not the SmartView client though). Here’s the story…

For the past 12 years we have use Essbase on Excel, users are required to download the Essbase Client for Excel. The installation up to System 9 version 9.3 is normally around 50Mb or less. That’s a reasonable size for users to download and install.

However, with the new Oracle EPM 11.1.1 and you’ll be surprised to know that you’ll now need to tell an average “Joe the Plumber” user that he/she needs to download 1.9Gb of zip files (5 of them) and then unzip it to his/her disk drive of 3.5Gb  !!!! And then…

The user will probably need an IT person to help to get through the installation (similar to a full installation of Oracle EPM onto a server but with less components selected to install). The process will take probably an hour. My first thought of this is “are you guys nuts?”. How can I explain to my users that by upgrading to EPM, in order to use the Excel client, they just went from a 50Mb to a 3.5Gb install? That’s a 7000% increase in size.

At first glance, from e-delivery you’ll think of downloading the Oracle Essbase Client Release which is 280Mb. Cool, right? Wrong.

In reality, in order for you to be able to install the Excel Essbase Client, you’ll need the EPM Installer 342Mb also. Now if you try to install the installer, along with the 280Mb you downloaded earlier, you’ll realize the common components are missing. Therefore, in order to get the installer fully working, you’ll now need to download the EPM Foundation Services Part 1, Part 2 and Part 3 for a total of 2,643Mb.

Of course if you don’t like that, you can get away with the Essbase Client 9.3, an earlier version that would work fine on Excel 2003 but is a little buggy on Excel 2007. Not to mention you will not have full functionality of EPM 11.1.

OK and the response I hear several times from support was that there’s a lot of new feature in EPM 11.1 that warrants the giant installation. Another reason is Oracle’s strategy to have one common installer for the entire EPM. Now I think the unified installer is a good concept because we all remembered how tough it was in installing System 9. You need to have the right files and then installing them in certain order. The unified installer maks it much easier. However, in this particular scenario, my arguments are:

1. That’s probably true but I am not seeing a big list of benefits for the Essbase Client, and therefore the installation size should reflect that;

2. If you look at the SmartView client, it’s only 57Mb (see below). So it is possible to have a thinner client for SmartView so why not Excel as well?;

3.  If it’s doable for the last 10+ years, surely it’s do-able for EPM 11.1, or am I missing something?

Anyway, I am hoping the Essbase development team would look at this issue and make reasonable adjustments. My suggestion would be to make the Essbase Client Release package to install any common components that’s needed. That way, the installation file size could be down to 622Mb (342Mb + 280Mb), that’s much smaller than 3Gb right?

As I have tried to remove folders that are not required for the Excel Client install, I was able to reduce it down to 2.6Gb. That’s still pretty huge but at least it’s 900Mb less. The interim solution is to zip and make our own distribution as oppose to asking for users to download 5 files, then unzip it to various locations, before the installation process.

Stay tuned, I am still trying to figure out a better way to handle this…


History of Hyperion MDM (Now it’s DRM)

The history of Oracle DRM goes way back to a company called Razza Solutions pre-1995. The company marketed a product called Razza Dimension Server (Razza DS), and had about thirty Fortune 500 as customers. In January, 2005, Hyperion acquired the company with Razza’s 15-person staff became Hyperion employees. Since Hyperion’s acquisition, the product was marketed as Hyperion Master Data Management (MDM) Server. They also integrated it as part of Hyperion’s System 9 Business Intelligence Platform.

The value proposition with Razza’s product was an innovative way to model business reality as required by different LOB and management leaders to measure business performance. They need to have a single point of control on the complex and dynamic business rules such as products, organizational, channel and impacts of mergers and acquisitions.

The need is real. Alot of companies throughout years of building legacy systems, maintain master data in separate (i.e. sometimes more than 10) source systems (e.g. ERP, CRM, BI Dashboards, Reporting Tools). Very few of them have a centralized master data solution. As a result it’s almost impossible to build one single version of truth. Dashboards are often built in silo with different business rules resulting in different groups reporting different performance results.

In the past, businesses leverages master data management (MDM) to harmonize key transactional and ERP systems, Hyperion MDM Server extends these to also manages business dimensions, reporting structures, hierarchies, attributes and business rules. With this product, we can manage master data across all the BI systems, enterprise data warehouses, financial and analytic applications and transactional systems. In addition, it enables a common definitions for business users and ensures a single version of the truth throughout the Business Performance Management (BPM) ecosystem.