Multiple shared members in ASO outline

Question

<BR>I am building an outline with one primary and three alternate hierarchies within one of the dimensions of an Aggregate Storage (ASO) cube. All of the leaf members in each of the alternate hierarchies are shared members of a member in the primary hierarchy. The non-shared member is a leaf in some cases and a summary point in others. All hierarchies are stored. <BR><BR>When I try to save the outline, I get a long list of verification errors. For the stored members to which the shared members refer, Essbase is complaining that "This member has multiple copies of same shared member in at least one stored hierarchy. See other messages for which members and which hierarchies." For the shared members, Essbase complains that "Aggregate storage outlines only allow a shared member once in a stored hierarchy." For the alternate hierarchies, Essbase complains that "This stored hierarchy has multiple copies of same shared member. Remove extra member or change hierarchy to be dynamic."<BR><BR>However, I did a find on a handful of the members that Essbase was complaining about and in all cases have found only one instance of each shared member in each alternate hierarchy. The same shared member might appear in two or more alternate hierarchies, but I have not found a case where it appears more than once in the same hierarchy.<BR><BR>I have also ensure the following:<BR><UL>The primary hierarchy occurs first in the outline, so non-shared members always appear before any instances of any of the shared members.</UL><BR><UL>There are no shared members in the primary hierarchy.</UL><BR><UL>All members, non-shared and shared, are in the same dimension.</UL><BR><UL>Non of the stored hierarchies contain both a non-shared instance and a shared instance of the same member.</UL><BR><BR>I have tried making the alternate hierarchies dynamic, but query retrievals are so slow that they're completely unacceptable to the client.<BR><BR>Has anyone encountered a similar problem? Is there a solution to this?<BR>

Answer 1

I heard back from Hyperion Tech Support again. Turns out it's not a defect after all. It's actually a subtle technicality in the restrictions on shared members with ASO. The first restriction, which is explained in the outline verification error message, is that you can only have one instance of a shared member within a given stored alternate hierarchy. The second restriction is that you cannot have any shared members within a given stored alternate hierarchy where the non-shared instances of the members are ancestors/descendants of each other. Unfortunately, when this restriction is violated, EAS gives the same error message as it does for the first restriction, so it's a bit harder to debug.<BR><BR>Hope this saves someone some grief.<BR>-Silvester