Calculate cubes using transparent partitions

hello,since I have had a transparent partition to my cube (my cube is the target) the calculation duration increases dramaticaly although the calc script do not fix on the members used in the partition.Have you already met this problem? Is it possible to define particular parameters to avoid this increase?many thanks for your help!

I have hesitated to suggest this because it involves changing more than your environment and calc, and it may not even be appropriate for you, but it would definitely help if you can do this.Instead of having 2 cubes, use 3 (ouch). The current cube becomes a facade to the two source cubes that contain data, call this CUBE_Facade, and also copy it to CUBE_SRC_Current (dropping the members mapped to CUBE_Source), and then CUBE_Source becomes CUBE_SRC_History. You should get the idea from this layout.Now for the calc. You wouldn't perform this on CUBE_Facade, but directly on CUBE_SRC_Current. If you further want to ensure that users don't interfere, you could temporarily drop the partition, but for a 3 minute calc I doubt this is a concern for you (if it is, you should also know doing it this way is a lot easier and cleaner than trying to kick users off and disabling logins). Security would also be associated with the facade, but it doesn't hurt to set it on all cubes (the users would have the ability if not the knowledge to connect to the source cubes, after all).Aside from the approach above, I can only surmise that perhaps the fix that limits your calc to the current portion (time/scenario?) doesn't account for variance formula's (even if dynamically calculated?). A solution for this may exist be making them stored (another ouch), and calculating them in a script instead of with a formula? I'm only guessing that this might help, or that the situation even applies.

Similar Messages

  • Using AGG/CALC DIM function in the BSO target cube of Transparent Partition

    Hi,
    Is it possible to use AGG("dimension") on a dimnesion in the BSO cube that is a target cube for a BSO-BSO Transparent Partition/
    I have created the partition area with 3 dimensions, one being 'Source'. 90% of the source members are being refrenced from source to target via that transparent partition. But I still have the 10% Source members in the target cube that need to roll up to the 'Source"(along with the 90%) for correct aggregation.
    When I try to use AGG("Source") in a FIX statement that's within the partition area, I get the following error:
    Error: 1042013 Network error [10054]: Cannot Receive Data
    Error: 1042012 Network error [10054]: Cannot Send Data
    Can I not aggregate the dimension in the Target cube?
    Thanks

    Hi,
    We have the same problem.
    I try to create transparent pertition between BSO (as a source) and ASO (target) and have the same warning message.
    Just to eliminate possible effect of outline complexity I created very simple DBs with the following outlines:
    __For ASO:__
    mes1
    mes2
    Measures
    prd1
    prd2
    Products
    Actual
    Adjustment
    Scenarios
    __For BSO:__
    mes1
    mes2
    Measures
    prd1
    prd2
    Products
    Adjustment
    Scenarios
    In addition to the message I have the following behavior - ASO has data in "Actual" scenario, BSO has data in "Adjustment" scenario. Before partition definition I can see the data in the right places, but when the partition created, Actual data disapeared from report of ASO. It is still in the database, and when the partition removed - appears again.
    Any ideas?
    Thank you in advance,
    Alexey

  • Combine 2 cubes with transparent partition but failed in cell count match

    I have 2 cubes:
    Cube A DIMENSIONS(YTD, YEAR, PRODUCT, LOCATION) + MEASURES
    Cube B DIMENSIONS(YTD, YEAR, PRODUCT, LOCATION, BE_TYPE) + MEASURES
    Both cubes have the same YTD AND YEAR.
    It is comparable for A.PRODUCT,GEN2 VS B.PRODUCT,GEN3
    It is comparable for A.PRODUCT,GEN5 VS B.PRODUCT,GEN6
    It is comparable for A.LOCAITON,GEN2 VS B.LOCATION,GEN5
    It is comparable for A.LOCATION,GEN5 VS B.LOCATION,GEN5
    Most measures have the same name between 2 cubes.
    Some are not.
    Now I need to combine 2 cubes into 1 for OBIEE usage.
    Criteria:
    1. Include all YTD and YEAR
    2. Combine A.PRODUCT,GEN2 & B.PRODUCT,GEN3
    3. Combine A.PRODUCT,GEN5 & B.PRODUCT,GEN6
    4. Combine A.LOCATION,GEN2 & B.LOCATION,GEN2
    5. Combine A.LOCATION,GEN5 & B.LOCATION,GEN5
    6. All data from Cube B are selected with B.BE_TYPE = 'TYPE_A'
    7. Combine ALL MEASURES FROM 2 CUBES.
    So, I am working on transparent partition with source = Cube B and target Cube A inside EAS.
    However, I cannot match the cell counts.
    Do you have suggestions? Any hints on my cases?

    thanks, in my case,
    YTD and YEAR contain the same members and names.
    Number of measures of two cubes are the same.
    However,
    1. A.PRODUCT,GEN2 & B.PRODUCT,GEN3
    2. A.PRODUCT,GEN5 & B.PRODUCT,GEN6
    3. A.LOCATION,GEN2 & B.LOCATION,GEN2
    4. A.LOCATION,GEN5 & B.LOCATION,GEN5
    the number of members of 2 cubes are not the same. Since the Product ID contained in A.PRODUCT,GEN5 is the not same in B.PRODUCT,GEN6. Infact I wonder how I can make them matched. It is because my purpose is to combine all these different product into one dimension (just like union them into one column), so their number must not match.
    Am I correct? How can I handle this case?

  • DynCalc And Transparent Partitions

    Following Problem:We have a big cube (13 dimensions!!!)covering 5 years of data, which i build up every month (for performance reasons). The 5 years are members of a separate (sparse) dimension.I also have a scenario dimension (sparse) including members like actual, forecast, LastYear (DynCalc), variance (Dyncalc),...Now I think of splitting the cube in 5 single cubes, one for each year (including the scenarios actual and forecast) that should serve as the data sources in a transparent partition.The data target should be a cube with all 13 dimensions (including all years!) and all scenarios (incl. the dynamically calculated ones). Unfortunately a retrieve on e.g. the member "lastyear" (DynCalc) shows a very low performance!Any ideas?(BTW: all 13 dimensions are necessary....)

    Depending on how much physical memory you have, bump up your Index Cache. You will also want to bump up your CALCCACHEHIGH to 199999999. Refer to this setting in all your memory intensive calc scripts. Unfortunately, using transparent partitioning adds a layer of overhead to data retrieves. If you have ample storage space, try changing the member option to dynamic calc and store. This will help out the performance for next user who retrieves this data. I have a very similar model. Less dimensions but some huge hierarchies.

  • Partitioning of cube using Fiscal period

    Hai Gurus
    Gud Morning
    Can u tell me how to partition a cube using 0fiscper ie Fiscal Year/Period.
    I am having one in this
    How to give value for 0FISCVARNT.
    I just need the steps to partition the cube
    Please suggest me.
    Awaiting all ur replies.
    Thanks
    mahi

    Hi Mahi,
    To partition the cube double click the cube this will take you to the definition of the cube. Click on the extras button at the top of the screen. you will get a dropdown, there you can see Partition option, click on that you will get another window there you all time chars select on which you want to partition and continue.
    you will get another popup window there you have to give Range.
    When you activate the cube fact tble will be created in DB with number of partitions corresponding to your Range.
    While you do this there should be no data in the cube.
    Regards
    Ananth

  • Slower processing in a cube with a transparent partition?

    I have a database that includes some scenarios that are the targets of transparent partitions.<BR><BR>I have found that the database loads data more quickly without the partitions in place. The calc all also seems to go more quickly.<BR><BR>Has anyone ever encountered this?<BR><BR>Jared

    Thanks for your answer but, if the same value of the characteristic I want to count comes from both update rules, will the counter value be 2? in my case, value of 2 would be wrong.
    Thanks,
    Inma

  • Drill-through via Transparent Partition

    Hi
    I am using Essbase Server and EIS 11.1.1. I have a ASO target cube which points to different ASO source cubes partitioned on dates. Each source cube has defined a drill-through report and this drill-through reports work fine if I access them directly from Excel add-in. But when I access these source cubes via my target cube (transparent partition) drill-through reports don't work (no visual effect on intersection cells). When I double click on them I cannot see my drill-through reports. Could anyone tell me what I am doing wrong here please? According to documentation, I should be able to drill-through via tranparent partioned target cube.
    Regards
    Chandra

    Thank you for the reply but Essbase Studio does NOT support drill-through from Recursive Hierarchy dimensions. That's why I had to go back to EIS.
    Edited by: user2695091 on 20-Feb-2009 17:30

  • Transparent Partition Mapping Error

    I havd an ASO source cube and BSO target cube
    Source Dimensions:-
    Periods
    Account
    Company
    CostCentre
    Product
    Target Dimensions
    Periods
    Account
    FiscalYear
    Scenario
    Company
    CostCentre
    Product
    Using MAXL I create a partition but I cannot get the mapped area to work correctly. the syntax I am using is :-
    create transparent partition 'SOURCE'.'GrpSrc'
    area '@DESCENDANTS("Periods"), @IDESCENDANTS("Account"),@IDESCENDANTS("Company"),@IDESCENDANTS("CostCentre"),@IDESCENDANTS("Product")' sourcearea
    to 'TARGET'.'GrpTgt'
    area '@LEVMBRS("Periods","Lev0,Periods"),@IDESCENDANTS("Account"),@IDESCENDANTS("Company"),@IDESCENDANTS("CostCentre"),@IDESCENDANTS("Product")' targetarea
    mapped targetarea('"Actual"') to ('')
    mapped targetarea('"CY"') to ('');
    The partition is not being created correctly because the extra dimensions in the target cube [Scenario and Fiscal Year] are not mapped
    Please let me know what I should be doing to get this to work!
    Essbase 11.1.2.1
    Many thanks

    Hi ,
    This error generally comes when there is an extra dimension in the target datasource.
    Yes, you can create a transparent partition between databases having different numbers of dimensions. In your case, you have to create a mapping from 'void' to a member in your extra dimension (i.e. 'Actual') in the target. There is an example in the DBAG.
    see the section on this page headed "Mapping Data Cubes with Extra Dimensions": http://download.oracle.com/docs/cd/E17236_01/epm.1112/esb_dbag/dotprtbd.html.
    Thanks,
    KKT
    http://www.knowhyperion.com

  • ASO and BSO Transparent partition

    Hi
    I have couple of questions regarding transparent partition, please help me out,
    1) I have two ASO cubes and one empty BSO cube, do I need to run security (apply filters) on both ASO and BSO cubes?
    2) How should I give access to users? For example: what should I write as "..."identified by" ....
    TO 'VZB_ISu'.'VB_IS' AT "localhost"
    AS "....." IDENTIFIED BY "....."
    AREA '"2006","2005",@IDESC("Month"),@IDESC("Scenario"),@IDESC("Measure_Type"),@IDESC("Measures"),@IDESC("Accounts"),@IDESC("RegionCompany"),@IDESC("Company"),@IDESC("RegionOrganization"),@IDESC("Organization"),@IDESC("Affiliate"),@IDESC("Product"),@IDESC("Ledger_Code"),@IDESC("Region"),@IDESC("Country")';
    3) Are their specific ways to tune an empty BSO cube transparently linked to ASO cube? BSO cube has no data.
    Thank you
    Namita

    Hi,
    1) You only need to set security on the BSO db (I'm assuming the users will not be connecting directly to the ASO db). When you setup your partition you define what user will be used to login to the ASO database. When ever an end-user retrieves data over the partition it's the partition user that logs into the ASO database to retrieve the data. You only need to make sure that the user defined in the partition has sufficient rights to retrieve that data.
    2) You can either use EAS to create the filter or MaxL...this is the example for create/replace filter: create filter sample.basic.filt1 read on 'Jan, sales', no_access on '@CHILDREN(Qtr2)';
    3) Try an avoid too many dynamic calcs in the target. These will obviously affect the retrieval times.
    Gee

  • ASO Cube with BSO Partition as a Target

    Hi,
    Can someone please explain me the following because after reading different blogs as well as some other Essbase documents I am not able to understand,
    What is the actual use of having a BSO Transparent partition (target) of an ASO cube (source)?
    How exactly does the Write-Back functionality works if I have a BSO Transparent partition (target) of an ASO cube (source)?
    And lastly, in what business scenario one would implement a BSO Transparent partition (target) of an ASO cube (source)?
    Your help is much appreciated.
    thanks,
    fikes

    I have a situation where I have a BSO (target) on top of an ASO (source).  This was to try and resolve the dynamic time series (where time and periods are in different dimensions).  The DTS works almost great in the BSO partition.
    The other problem (or why we wanted to go to ASO) was that BSO cubes do not handle attributes across partitions (we have quarterly data in transparent partitions) to the target cube. -- but we do have dynamic time series.
    What I'm facing now it that the attributes work in the BSO (target) except when using a dynamic time series.
    The attributes are defined in both the BSO and ASO cubes.
    Any suggestions on how to handle attributes AND dynamic time series ?

  • Outline Synchronization in Transparent Partitioning

    Hi,<BR><BR>Would it be possible to synchronize outlines in a transparent partition that uses different types of storage? I have a source db of ASO and target db of BSO. I tried GETPARTITIONOTLCHANGES using Esscmd, but didnt work since it requires both cubes of the same storage types. I also tried using 'refresh outline' from maxl, but it didnt seem to do any good. Anyone encountered this type of problem?<BR><BR>Gerd

    Found out that this cant be done if the storage types between source and target are different.

  • MDX / BSO calculations with transparent partitions - Recursive reference

    Hi Everyone,
    I am using Essbase v11.1.2 and have an empty ASO cube that has transparent partitions to several ASO source cubes. However, I would like to use MDX in the target ASO cube to pull data from one cube, but make it available to all queries from other cubes.
    Eg. Empty Target ASO cube TrgtASO has VOLUMEmetric and versions Ver1, Ver2 and Ver3. I have 3 ASO source cubes for each version.
    SrcASO1 is only cube with volume data
    SrcASO2
    SrcASO3
    I had created a metric called "Vol-All versions" in the TrgtASO cube and tried to use MDX fornula ([Version].[Ver1],[Measures].[VOLUME]) so that no matter what version is selected, the data will always be from SrcASO1.
    It works if I have all data in one cube and load data only into Ver1. However, for performance and query reasons, I need to put each version into it's own cube.
    My question is do transparent partitions allow recursive retrieval of data?
    I.e. If I log into TrgtASO cube and pull metric "Vol-All versions" but have either Ver2 or Ver3 as the version, is there an MDX formula that will pull the volume from Ver1 cube?
    Any assistance would be greatly appreciated.

  • User View is not reflecting the source data - Transparent Partition

    We have a transparent partition cubes. We recently added New fiscal year details to the cube (user view as well as source data cube). We loaded the data to the source data cube. From the user view, we tried to retrieve data, it shows up 0's. but the data is availble in the source data cube. Could anyone please provide the information what might be the issue?
    Thanks!

    Hi-
    If u haven't add the new member in the partition area, then Madhvaneni's advice is the one u should do. Because, if u haven't add the member, the target can't read the source.
    If u have already added the new member in the partition area, and still the data won't show up, sometimes it's worth to try re-save the partition, and see what's the outcome.
    -Will

  • Syntax error Creating Transparent Partition in MaxL

    Hello,
    I'm trying to create a simple transparent partition (no mapping needed, just using all the 3 dimensions and descendants in the source database to the target database. I'm getting a syntax error, I went through the MaxL naming conventions and also tried a couple of diffferent things but to no avail. Please help as to what the error might be:
    My code is as below. The error I get is: Getting a syntax error near '@IDESCENDANTS("Accounts"), @IDESCENDANTS("Products"),@IDESCENDANTS("Market)
    Code:
    create transparent partition student8.coke area '@IDESCENDANTS("Accounts"), @IDESCENDANTS("Products"),@IDESCENDANTS("Market")' sourceArea to student8.cokepart at lab01 as essadmin identified by 'password' area '@IDESCENDANTS("Accounts"), @IDESCENDANTS(Products), @IDESCENDANTS("Market")' targetArea;

    Nobody replied to this, but actually the error was the double quotes on Accounts, Products and Market.

  • Transparent Partition Between ASO & BSO

    Hi,
    I am trying to define a Transparent Partition between an ASO (Source) & a BSO (Target) cube.
    My ASO cube has 16 dimensions, BSO has 12 dimensions. The matching 12 dimensions are identical.
    The data from the source should be taken from all levels of the 12 matching dimensions and Highest level data of the non matching dimensions.
    Is this doable?
    Is there any special syntax in partitions definitions?
    Appreciate your thoughts.
    Thanks,
    Ethan.

    Glenn,
    Thanks. It's working. I created the partition manually, kept void for all the 4 missing dimensions.
    When I have to write the script, I am not sure how to specify that in the script
    mapped targetAreaA ("Dim1") to (Void)
    mapped targetAreaA ("Dim2") to (Void)
    mapped targetAreaA ("Dim3") to (Void)
    mapped targetAreaA ("Dim4") to (Void);
    or
    mapped targetAreaA ("Dim1", "Dim2", "Dim3", "Dim4") to (Void, Void, Void, Void)
    Are these correct syntaxes?
    Appreciate your thoughts.
    Thanks,
    Ethan.

Maybe you are looking for