I've done a few installs of 11.1.2 recently. One was a distributed install on windows (everything except Essbase, APS and EAS on the same server a second server housed the rest.) The other is a mixed environment where everything was on windows except essbase. So below are a few of my findings regarding 11.1.2.

1. Make sure DNS is working and that all servers can see each other by FQDN before attempting to install.
2. Ensure that the server can see it self by DNS name (not localhost).
3. On linux make sure SELINUX is disabled.

Failure to have either of these conditions met will cause all sorts of odd problems.

Now this may seem like common knowledge but in the case of my last two installs I was not involved with the setup of the hardware. In once instance I gave my specifications to an infrastructure team and trusted (by mistake) that they did things correctly. On the other I didn't think to check that the windows server and found out after the fact that the windows server thought its FQND resolved to the equilivent of 127.0.0.1 but in IPv6 (::1)

I had an issue here where Planning (11.1.2) users had been given access to read and write to certain areas however when we refreshed the security filters in planning only the read filters appeared in the Essbase cube. The users could enter data into planning forms but were unable to enter data view SmartView.

After opening a SR and looking around on the web we stubled upon the following forum post. It appears that when this application was migrated from version 9 to 11.1.2 that we missed a setting when provisioning users in shared services. In previous versions of shared servers the setting was called "Essbase Write Access" however in 11.1.2 the name of the setting has been changed to "Analytic Services Write Access". After re-provising the group with this access we refreshed security filters and checked essbase and vola write filters now showed up.

Searched around for this error and found nothing. Assuming I find a new home for my blog that wont happen in the future.

Anyway I am being told this error message occurs when a level 0 member is dynamically calculated. In my case that is odd because the member in question has a formula. That's all for now, I will update if I find the solution.

On and off for the last few months I've been playing with the Essbase API and trying to initialize it in C#. Apparently I am in need of some assistance, for the life of me I can't figure out how to get this thing started. I refuse to accept the idea that I should use the JAVA API and expose the functionality through web services (this is what Dodeca does). So really this is just a rant and maybe a shout out asking if anyone has some samples. Coming from a development background I have been kinda shocked that there is so little code available for public view with regards to this API.

Anyway here are some things I was trying this morning but I am giving up on for now and gonna go work on my IMAP stuff.

 

 

public unsafe struct EssbaseInit
{
    public ulong Version;
    public ushort MaxHandles;
    public string LocalPath;
    public string MessageFile;
    public string HelpFile;
    public ushort ClientError;
    public ushort ErrorStack;
    public ushort usApiType;
    public Int64 vbCallbackFuncAddress;
}
[DllImport("lib\\esbapin.dll")]
public static extern long EsbInit(IntPtr init, ref long instance);
public static unsafe long EssInit(ESB32.EssbaseInit init, ref long instance)
{
    int size = Marshal.SizeOf(typeof(ESB32.EssbaseInit));
    IntPtr handle = Marshal.AllocHGlobal(size);
    Marshal.StructureToPtr(init, handle, true);
    return EsbInit(handle, ref instance);
}

Anyone who has used Oracle Enterprise Performance Management System Workspace also known as EPMA (Enterprise Performance Management Architect) knows its error messages can be quite cryptic so as I come across solutions ill try to document them.

Let me start by saying this error pertains to importing dimensions into EPMA from SQL this is probably valid for file imports too but I have not tested that. Okay so this has given me some trouble over the last couple hours but I think we now know what "This member cannot be inserted because the parent member has another child member with the same name." really means.

In this import we are trying to create the structure similar to this.

• #root
• Category A
• Cat A1
• Cat A2
  
• Category B
• Cat B1
• Cat B2

Our import has the following format:

Parent	Child
#root	Category A
#root	Category B
Category A	Cat A1
Category A	Cat A2
category B	Cat B1
Category B	Cat B2

When running the import all the members are created in the dimension and everything looks good except that EPMA complains that with reference to Cat B1 that "This member cannot be inserted because the parent member has another child member with the same name." If you checked your data like I did and notice there is only one instance of that member in the source. Then you probably have just stumbled on to the error I came across. What EPMA is not telling you is that at least in part it is case sensitive. If you create a child member with all caps then when you reference it as a parent that should be in all caps too. In essence the should have been:

Parent	Child
#root	Category A
#root	Category B
Category A	Cat A1
Category A	Cat A2
Category B	Cat B1
Category B	Cat B2

Anyway there you go my first entry regarding Oracles Enterprise Performance Management Suite.