Querying multiple namespaces results in error in dynamic cube

[danii64]

Hello All,


I'm new to dynamic cube report building i have run in to bit of a trouble that i cant seem to figure out if it is at report level or cube.

I have simple cross tab, where the equipment key is exists in two namespaces, N_equipment  and N_Customer, while the customer info is only in Customer namespace.

i created two queries one from each namespace and and joined them on Equipment_key and when i run the report it gives me the follow error message.
XQE-GEN-0010
Found an internal error: 'Cube 'Equipment' in the current RolapContext not in the sharing set from shared dimension 'Customer'.'.

when i bring everything i need into a single query, no joins. and i get the following error:
XQE-PLN-0307 
Reference to multiple cubes/namespaces in the same query is not supported.

I didn't develop the cube i'm just working on the report building. Any help will be greatly appreciated.

Thanks!

[MFGF]

Hello All,


I'm new to dynamic cube report building i have run in to bit of a trouble that i cant seem to figure out if it is at report level or cube.

I have simple cross tab, where the equipment key is exists in two namespaces, N_equipment  and N_Customer, while the customer info is only in Customer namespace.

i created two queries one from each namespace and and joined them on Equipment_key and when i run the report it gives me the follow error message.
XQE-GEN-0010
Found an internal error: 'Cube 'Equipment' in the current RolapContext not in the sharing set from shared dimension 'Customer'.'.

when i bring everything i need into a single query, no joins. and i get the following error:
XQE-PLN-0307 
Reference to multiple cubes/namespaces in the same query is not supported.

I didn't develop the cube i'm just working on the report building. Any help will be greatly appreciated.

Thanks!

Hi,

I assume that when you refer to multiple namespaces you mean you have multiple Dynamic Cubes published to the same package?

If so, you're not going to be able to join them (joining is a relational concept) and you're not going to be able to build a single query/crosstab containing the contents of both cubes. The best option is to create a single cube with all the data you require - either a "real" cube or a virtual cube - in Cube Designer. Plan B is to link the two crosstabs via a Master/Detail relationship - possibly by embedding them both into a list in your report. It's messy but it should be do-able.

MF.

[bus_pass_man]

You'd want to use the virtual cube approach.

Even if building a join between your queries worked and the query engine didn't complain about the query coming from multiple cubes you would need to worry about the query results being wrong because of what you've done.

Lumping all your facts into one big fact table will only work if all your facts are at the same grain and all of your dimensions have scope to all of the facts.  It also violates the Kimball data warehouse design principle of a fact table for every process.

http://www.kimballgroup.com/2009/05/the-10-essential-rules-of-dimensional-modeling/

http://www.kimballgroup.com/wp-content/uploads/2013/08/2013.09-Kimball-Dimensional-Modeling-Techniques11.pdf