Transparent Partition

I have two source cubes (say C1 and C2) connected through a target cube (C3). Now C3 has got some dynamic calc that refer across both the source cubes (C1 & C2). This is hitting the data retrieval performace through Excel Add-in... and if the number of rows in the retrieved report is more (say 1000-2000 lines) then it just hangs forever. Kindly suggest some way to improve the performace of retrieval. Thanks. Raj

No. In C1 & C2 they are stored. In C3 the dynamic calc is x-referencing C1 & C2.

Similar Messages

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.

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

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

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.

Essbase Transparent partitions error

Hi!
I'm facing the following error in essbase
Essbase database error 1023040: msg from remote site [[Wed May 22 11:14:36 2013]preicostos66/PS09/PS09/admin@Native Directory/Warning(1023011) Error asigning remote member [OBJ_537].]
msg from remote site [[Wed May 22 11:14:36 2013]preicostos66/PS09/PS09/admin@Native Directory/Error(1040023) Unvalid network data.
The situation is the following
Three applications have Transparent Partitions PS2008 PS2009 & PS2010 (sources)
These were referenced in only one application PS (target) with extra dimention (YEAR)
PS outline is member complete but when retrieved any data that is not in the PS2009 outline unexistent member it shows the error.
Please help
Oscar

Hi-
It wouldn't be matter if members in current BSO cube partitioned to members existing in historical ASO cube. But if you want to retrieve new members that exist in BSO cube and don't exist in ASO historical cube, it won't show any value since it doesn't exist in the historical cube and of course the partition area from BSO to ASO can't be updated except when you want to map it to another member.
Regards,
Will
Edited by: William Lesmana on 22-Jan-2009 02:37

Transparent Partitioning Error

Can somebody please help with this error :
[target] - partition definition is not valid: [unable to process area for slice [1] see server log]

There are 2 cubes A, B and transparent partition created to third final cube C with both of them. On partition b/w cube B and cube C following error is coming:
[target] - partition definition is not valid: [unable to process area for slice [1] see server log]
I read somewhere on google that this error comes when there is problem with other partitions on same cube.
On partition b/w cube A and cube C following error is coming:
Partition [sestc01as288.danfoss.net:1423 EssDRS EssDRS] is not valid [Target] - Partition definition is not valid: [Partition definition for slice [1] does not parse]
Please suggest some solution how to check.

MAXL and Transparent Partition

Hello,
I am actually working on the Hyperion Essbase EPM 11.1.2
I am trying to create a transparent partition using a MaxL command:
When I create manually this partition (using EAS): This is validated and data are copied.
When I run the MaxL: The partition, appear but it seems to be broken, I can only repaire or delete the new partition.
If I try to repair it (in EAS), It does not work. I don’t manage to link my partition to source and target database.
I have used with two different users : Admin (native directory) and another user (admin access).
Thanks for your answer,
Arthur.

Hi,
What the error message you are getting.
When you create a partition via Mxl editor it will open the interface to create the partiton. Check this Mxl with your mxl.
Thanks,

Transparent Partition Issue

Hi All,
We have Planning BSO cube and it has 16 dimensions (Had to go with that many dim, although the max. is 10), and the aggregation process took abt 1.30 hrs, we've tried all possible fine tuning.. considering the no. of dims, it's fairly ok.
Now the client wants all the HFR reports to be in real - time, so we've created a reporting cube (ASO) with exactly same dimensions and members, created a transparent partition mapping only level 0 members, and expected it work like once the level 0 members are mapped, it'll automatically aggregate to the parent members since its "ASO".
Can you please let me know whether this logic will work or I've to go to replicated partition?
Forgive my ignorance if my judgement is completely wrong.
Regards,
Rajeevan D
Edited by: 865958 on Jun 14, 2011 10:54 PM

Your question jumped from what sounded like data not being replicated in the partition to the outlines getting out of sync. I'm guess the latter is more likely a problem.
Is the partition on ASO? BSO -> ASO partitions need to be manually synchronized.
Regards,
Robb Salzmann

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?

Slower processing in a cube with a transparent partition?

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

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 to BSO Transparent Partition problem

Hi,
I am doing a partition from ASO(Source) to BSO(Target). Outlines are same except one dimension:
Aso cube
dimension has 10 Level 0 members in Level 1.
BSO cube
Same dimension has 2 level 0 members(these 2 members are same as in ASo) in Level 1.
Do rest 8 members be available while retrieving data in BSo cube? [Right now when i connect can only see 2 members]
Was wondering with Transparent partition is it possible to see the additional outline members in BS ?.
Any help to clarify would help thanks.

I think i am understanding your question.
A user will only "see" what members/dimensions are in the Target cube. You would need to add the other 8 members to the target outline to be able to pull the data for them from the source cube.

Issue in ASO to BSO TRANSPARENT PARTITION

Hi Techies,
We are facing issue in ASO to BSO Transparent Partition. Please see below details and suggest.
1. we are having a ASO cube transparently partitioned on to BSO cube.
2. In ASO cube, we have a dimension with 3 hierarchies under it which are strored hierarchies. when we retrieve data for this hierarchies from BSO cube we are getting data.
3. Now we were asked to add one more stored hierarchy under the same dimension, we built the dimension and built aggregations based on the queries. After creating the partition we are not able to retrieve the data from BSO cube for the newly added stored hierarchy everything else is working fine as before. The following is the error am getting when I tried to retrieve data for the newly built stored hierarchy.
1012704 Dynamic Calc processor cannot lock more than number ESM blocks during the calculation, please increase CalcLockBlock setting and then retry (a small data cache setting could also cause this problem, please check the data cache size setting).
I increased CALCLOCKBLOCK in .cfg file , increased data cache size and bounced the server. Even now am getting the same error. Please suggest what else we can do with this kind of error

Did the number of blocks that couldn't be locked decrease when you increased the data cache if so try increasing the data cache some more, make sure you restart the db after each change.
Cheers
John
http://john-goodwin.blogspot.com/

Transparent Partition

Similar Messages

Maybe you are looking for