Upload duplicate members to ASO

I'm testing for a conversion of a cubo to one that allows duplicate members. So far, the outline has been constructed properly, including my test members [dim1].[OTHER] and [dim2].[OTHER]. However, I can't upload any data to cells in those members.
When I include just the leaf member names 'OTHER', I get an error in the dataload.err file saying OTHER is a duplicate member, even though they already exist in their dimensions.
But, if I type the qualified member name [dim1].[OTHER] in the datafile, EAS throws an error saying "Aggregate storage applications ignore update to derived cells. [%s] cells skipped". I am sure it does recognize those names as existing in the outline because changing the name throws the usual "does not exist in database" error.
I figure it interprets qualified names as having formulae in them. Is there any workaround this issue?
Thank you,
Alejandro Castro
UPDATE: I tried giving different aliases to each duplicate member (others and otherss), and got the same "Aggregate storage applications ignore update to derived cells. [%s] cells skipped" error message.

DataStorage is set to 'Store Data' for both members.
Alejandro Castro

Similar Messages

Duplicate Members - Please help!

Can anyone please give me a good explanation of how to add duplicate members in an ASO cube via Essbase Studio? Firstly, I have created an inner join between parent and child members of one of my minischema tables. Next, I go to the model properties and check the "duplicate member support" option. I then go to the member that I want to allow duplicates for and in the "outline build" tab I check off *"Ignore duplicate members, do not move"* I'm assuming this means that when a duplicate member is encountered it should be allowed to stay in the cube... Anyways, when I try to deploy the cube this way, the duplicates don't come thru. Am I following the correct process for adding duplicate members?
I've also read that my member name needs to be fully qualified. How do I do this in Essbase Studio?
thanks,
Akshay

Can you try closing the outline without saving and manually adding in some to see exactly where the error is? It sounds like there is a duplicate member not marked as Share. Are you using a load rule to build the outline? I agree with the last post about checking the dimension build settings.

Pulling duplicate members in excel

Hi all
I have just built an ASO cube allowing duplicate members for the first time. I have 2 dimensions with duplicate parents (Other):
Summary Allowed
Other Other
How do I call up "Other" in Excel (using the Excel Add-in). I cannot just put "Other" in the sheet as it returns an error
(unknown member name [[Summary]@[Other]] in Outline query
Thanks for your help as always

Hello,
Create a new member down the first one in your dimension. Put the value 'shared member' in DataStorage options.
Regards

Duplicate Members in Essbase

I need to have duplicate members in one of my dimensions, without adding a qualifying prefix or sufix. For example, suppose my dimension is as follows:
Country->State->City->Zip. I want to have duplicate member names at the City level, without having something like "MA_Springfield". I want the city name to just be "Springfield"
So in order to accomplish this, I modify the key binding for City in Essbase Studio to the following:
*"[" || connection : \'OBIEEDEV'::'ENTERPRISEBI.COUNTRYDIM.'Country' || "].[" || connection : \'OBIEEDEV'::'ENTERPRISEBI.COUNTRYDIM.'State' || "].[" || connection : \'OBIEEDEV'::'ENTERPRISEBI.COUNTRYDIM.'City' || "]"*
I then enable duplicate members in Essbase properties and deploy the cube, but the Cities that are duplicates get dropped during the outline build.. The error messages say that *"duplicate members are not allowed at this generation level"*
What am I doing wrong?
Appreciate any advise.
Fyi - I'm building an ASO cube in EPM 11.1.2 using Essbase Studio. Also, in my Essbase properties Outline Build, I'm choosing the Move duplicate members (and their descendants) setting
Edited by: 806008 on Nov 11, 2010 11:19 AM
Edited by: 806008 on Nov 11, 2010 11:22 AM

Hello,
Create a new member down the first one in your dimension. Put the value 'shared member' in DataStorage options.
Regards

Duplicate member in ASO application

Hi,
I need to load data in an ASO application (version 11.1.2.1). Provision for duplicate members is enabled for this application and so, some of the members across dimensions have duplicate members. But during data loading, Essbase is throwing error on duplicate members and data is not loaded. Similarly, in Smart View, query is not accepted if duplicate members are selected.
Please advise if there is any work around to load data for duplicate members.
Thanks.

Hi,
one basic things is duplicate members / member aliases are not allowed within same parent.
Make sure your application is enabled for duplicates and try to create some duplicates manually and then send data through some add-in, etc. For data loads, have you tried to load them using qualifiers ?
Refer the below link for working on duplicates
[http://docs.oracle.com/cd/E17236_01/epm.1112/esb_dbag/dotnonuq.html|http://docs.oracle.com/cd/E17236_01/epm.1112/esb_dbag/dotnonuq.html]

Maximum number of members in ASO outline

Hi All,
We are using Essbase 11.1.2.1. We have ASO cube with 11 dimensions, 1 dimension is expected to have more than 30 million members. Is that allowed ? What is the maximum limit for members in ASO cube ?
Also how to improve performance for such cube ?
Kindly advice.

I believe the answer is no. The maximum number of members is 20 million: http://docs.oracle.com/cd/E17236_01/epm.1112/esb_dbag/frameset.htm?limits.html#limits_8
Cheers,
Mehmet

Multiple shared members in ASO outline

 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. 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." 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. I have also ensure the following: <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> <UL>There are no shared members in the primary hierarchy.</UL> <UL>All members, non-shared and shared, are in the same dimension.</UL> <UL>Non of the stored hierarchies contain both a non-shared instance and a shared instance of the same member.</UL> I have tried making the alternate hierarchies dynamic, but query retrievals are so slow that they're completely unacceptable to the client. Has anyone encountered a similar problem? Is there a solution to this? 

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. Hope this saves someone some grief. -Silvester

Shared Members in Duplicate Members Hierarchy

It seems that many people have asked this question on this forum but I am yet to find a solution. Most of the posts were about 5 years old so I am hoping maybe something new has happened since.
I have a dimension that has a regular and alternate hierarchy (shared members). I have changed this dimension to duplicate members enabled. Once I have this turned on, my regular dimension build rule no longer creates shared members but instead creates a new member of the same name. I cannot find any property that I can put in the dimension load rule to specifically tag members as shared. The only way that I can change it is in EAS one by one. Is there any fix that allows me to load shared members through a load rule with duplicate members enabled?

You may have seen my posts on this on Network54 from 2007 or so while you were searching. I could never find a way to do this, and there is no property to tag members as "Shared" to the best of my knowledge. I tried it again quite recently (in 11.1.2.3.500) and got the same result.

'Allow Duplicate Members' not compatible with Attribute Dimensions

When setting the 'Allow Duplicate Members' option on there is a problem if the duplicate member is used as an Attribute. When attempting to apply the member filter to use the attribute Essbase throws an error: Cannot uniquely identify a member, the name [L] is duplicated.
In my case L is duplicated across two dimensions [L=LOCAL as a BOOK_CODE and L=LIABILITY as an ACCOUNT_TYPE].
The ACCOUNT_TYPE is an attribute dimension related to the ACCOUNTS dimension. Both the excel addin and Financial Reports have a problem as their member selection interfaces don't fully qualify the selection.
This seems like a bug.

When you sync over the cable, it is one set of calendars in one section labeled "From My Mac" when you sync with iCloud, that is store in a completely separate area labeled "iCloud." The "From My Mac" calendars are stored on the phone as just "regular" calendars. The iCloud account are "CalDav" calendars, which syncs with iCloud. The old mobileme calendars did do what you wanted, sync over the cable and then to mobileme, and that lead to huge data corruption and why Apple made the new mobileme calendars which sync over CalDav only (and cannot talk to the cable) to protect the calendars. The phone sees them as two separate calendars.
Your best bet is if you want to use calendars on your G4 is to just use the iCloud.com web interface. I'm also not familiar with the whole drop box thing, so I can't comment on that.

Importing duplicate members for planning appln - EPMA Dimension Library

Hi,
How to import duplicate members while importing dimensions using flat file in EPMA Dimension Library (11.1.2.1).
We have Isprimary column which enables multiple instances of a member as shared members, but how to import duplicate members in EPMA?
From the EPMA Guide:
Specifying Primary and Shared Instances of a Member using IsPrimary
In import files, any two members in the same dimension, with the same name, are always treated
as separate instances of the same member. If a member has multiple instances in a dimension,
the IsPrimary column specifies which instance is primary and which instance(s) are shared. The
IsPrimary column is not required; however, we strongly recommend that you use it. If left
undefined, it defaults to “True”, which assumes that the member is primary. If left undefined,
a warning is displayed in the Import Results file.
Note: Older import files, that do not use the IsPrimary column, can still be run. However, if the
import file does not have the IsPrimary column, it is not possible to create shared members
or move members.
Thanks in advance.

As you are talking about a planning application then duplicate members are not supported but Shared members are.
Cheers
John
http://john-goodwin.blogspot.com/

Duplicate Members From Same Dimension On Data Record

Hi guys, been a while but I'm back into problem land again. I got a SQL Server database with a load of records in it, some are NULL, and I use them to build a rules file called CGI_BUILD. When I run the rules file on the outline it builds fine with no errors but when it does the second part of loading the data, it kicks out an error file. The error that repeats over and over in the log is "\\ Duplicate Members From Same Dimension On Data Record". This seems to be the case for every record in the load file except for the second record. The only difference with that record is it has N/A for some of the columns instead of the regular "Retail" or "Finance" or whatever the other fields are.
I realize you have limited information here without screenshots but maybe you can help me get started on a solution. In my searching I found that some people have had this happen when the first record has an empty column in it but I can't rearrange them because there's a few columns that are empty for every record. They're there for add-ons later in the project. Any ideas?

To my outline, via SQL load, I added a new attribute dimension called Retail Region/Area:
-Retail Region/Area
--West Region : Region Manager
---Area1 : Area Manager
---Area2 : Area Manager
---Area3 : Area Manager
--East Region : Region Manager
--Factory Region : Region Manager
---Area1 : Area Manager
---Area2 : Area Manager
--Central Region : Region Manager
As you can see, it's split up into regions which have a region manager. And each region has a pile of areas which each have an area manager. The relationship for each region/area to its respective manager is 1:1.
To my rules file I added 3 new columns:
GEN1,Retail Region/Area (data = "Retail Region/Area")
GEN2,Retail Region/Area (data = Region Name : Region Manager)
GEN3,Retail Region/Area (data = Area Name : Area Manager)
I've ignored the data load and dimension build on the first 2 columns, but the third one, the lowest level, is the one data is being loaded into, among many other dimensions. The only weird thing I noticed is the last column (GEN3,Retail Region/Area) doesn't have a Field Name under the Data Load Properties. It's just blank.....but I don't think that would matter.
Now to answer your questions.....multiple columns that have members from the same dimension........it doesn't look like that's the case with the three columns I added. Am I missing it? And the rows I should be looking at......are you referring to the SQL database or the data prep editor in Essbase after loading the SQL file? I'm not converting NULL to anything that I know of. If it was preset before starting the project it's likely the same for every dimension. And as far as transformations, I'm not familiar with that so that would be a no.
Message was edited by:
DeX
Message was edited by:
DeX

Data Load Duplicate Members Warning / Error

Hi,
I am running Essbase 11.1 and haven't used duplicate member settings much before. I'm having some trouble with data load errors.
Background
I have a dimension called "State" which includes member "SC" for South Carolina - however this is a parent member, and data loads go to it's children.
I also have a dimension called "Method" which includes member "SC" for S-Cycle
Both these dimensions are flagged to allow duplicate members.
Problem
When I load data to my outline, my error message says "Member SC is a duplicate member in the outline". I am using a rules file, and have told essbase that my one column represents the "Method" dimension. Because I load to a child of the state, I am not loading data to SC state directly (I ignore the state column in my data).
Any ideas on what I need to do to get this to work? I"ve tried prefix/suffix to add [Method].[SC] and similar but no luck so far.

Thanks John - still not quite working
I should give another detail / extra complexity
The "Geographic Location" dimensions looks like this:
"Geographic Location" (Gen 1)
"United States" (Gen 2)
"SC" (Gen 3)
"Unique Facility 1", "Unique Facility 2" etc (Gen 4)
The data I have would be for Facility 1, Facility 2 which are unique member names which just happen to roll up under SC in the outline. I would have thought it would just load directly to those members without needing to specify their parent values.
Do I need to specify [Geographic Location].[United States].[SC].[Facility 1] ? This seems like it's something that needs to be done in the source file rather than using the prefix/suffix features of the Rules File.

FDM Essbase Adapter - Duplicate members from same dimension on data records

I am getting this error message when trying to export data to Essbase using FDM.
Error - Duplicate members from same dimension on data records.
Though this error looks quite straight forward, I could not find any thing in the data file to indicate the same. I even tried loading a single row data, but still got the same message.
What other things I should be looking at to fix this issue?
Thanks.

There are one or two previous threads on this, but this might give you some help to start with as it links to an esssbase document which gives suggestions for the error message:
Error in dataload- Duplicate Members From Same Dimension On Data Record
another thread indicated that the first record had a blank in it and by re-sorting to have the first records with all fields populated resolved the issue (not sure on this one).
from the FDM side:
1. Are the dimensions correctly mapped in the Essbase adaptor?
2. Are the dimensions in the correct sequence for loading to Essbase.
3. Does the same value appear In more than one field (Can't remember but i think essbase didn't use to allow the same member name across dimensions).

Duplicate members from same dimension on data load

Hi friends,
i have three dimensions.ORG,CUSTOMER,MEASURES. I HAVE SHOWN THE STRUCTURE BELOW.
ORG
group(GEN2)
raja(GEN3)
vertical(GEN2)
raja(GEN3)
CUSTOMER
raja(GEN2)
MEASURES
actual.
I AM USING DUPLICATE MEMBERS CONCEPT.
The problem is that how to load data for duplicate members in the same dimension.since i am having group and vertical under ORG. how to give names for those colums.i have given my data file which i used to load.
gen2,ORG gen3,ORG gen2,CUSTOMER actual
group raja vertical raja raja 20
here i dont know what name to give for vertical and raja since it is a duplicate member from the same dimension.
i also tried to load data for group and verical separately. it loads successfully. but when i view the member raja(from CUSTOMER dimension) across actual i get the value as 40. since i have loaded the data twice( one combination for group and one for vertical.
can anyone help me to resolve this problem. it will be of great help to me.
Thanks.

Hi,
To ensure duplicate member outline hierarchies are built correctly, use qualified member names in data source or use the rules files to construct qualified member names from fields in the data source
Example:-
suppose we have this data set-
West India Delhi 12344
West India Bangalore 46544
East "New york" "New york" 126787
Here I am using the RULE FILE to construct qualified member names--
Step 1:- Create the additional TEXT fields, create one field each for the
following text elements-
Step 2:- Using the MOVE operation, move the fields to the following sequence:
1 . .2 . .3 . .4 ..5 ... 6 . 7 . . . 8
[   west ].[ India ].[ Delhi ] 12344
step 3:- Using JOIN operation, join together fields 1 2 3 4 5 6 7 to create a
signle field as
1     .     . . . . . . . . . . . . . . 2
[west].[India].[Delhi] 12344
OR
you should specified the full qualified name in your DATA SOURCE.
Hope it will help you.
-Mohit

Duplicate members to be showed as shared member

Hi all,
working on ver11.1.1.3.X,i tried to build dimensions through rules file but some duplicate members are there in the .dim file. I have build the primary member hierarchy first and later tried to build the member hierarchy having duplicates,when i loaded the duplicate member hierarchy the members in primary member hierarchy were automatically deleted.
I'm using Level reference for dimesion building. The duplicates in the second member hierarchy should be shown as shared members,
can any one tell me how to make the duplicate members as shared with level reference?
thanks in advance

Hi gurus,
I'm building two members of a dimension hierarchy through rule files, i have two .dim files in level reference format so i created two rule files.The problem is during defining the dimension build properties because some of the members in the second member hierarchy have to be defined as shared members.
Let say i have a dim A and the members are B & C. I need to load B.dim,C.dim files by using level reference method through B1.rul,C1.rul files. C.dim has some duplicate members of B.dim which are to be defined as shared members of C member.
The duplicate members are at different levels(in B at Levl2 and in C at Levo- these Lev0 duplicate members have to be shared ).Please help me out in defining the dim build properties,
thanks in advance
Edited by: kailash on Jan 4, 2012 11:27 AM

Upload duplicate members to ASO

Similar Messages

Maybe you are looking for