alias table result in incompatible objects

[Former Member]

Hello,

using alias to mange loops (instead of contextes, ... lots of different date "contextes" with

an oracle date-organisation Table ) results in incompatible objects (webi: only to use in different blocks)

checking "multible selects " in univers will supress error and work with (two) non synchronised "selects"

but I get no join

(direkt join in sql developer over datefield works fine !)

i even have found an article on this subject that postulates "synchronisation" in the selects

How to force join in this situation (what may the error reason be..)

kgs-ks

[Former Member]

solution: missing path to alias -Table in context definition

[Former Member]

hallo to all readers ( writers) of this thread:

I am soory to tell, that the resaon for te problems was just

an context with a needed path missing:

The proble arrised because - not me but a college - put context to

that universe and in this contex we added the missing pass my table

an all works fine.

(it was my aim to avid definig contextes ... collaboration

without talking / version management leads to this

Thank to all helpers trying to understand that subject...

Karl

(kgs-ks)

[Former Member]

Hi,

Alias tables just gives you the flexibility to use the same table with different names.

I don't think there is any relation between Alias Tables and incompatible objects. (Experts can correct me if I am wrong)

I think you either might have missed some join in the universe which needs to be created due to which BO query is splitting in two SQLs or you have missed 1 or 2 joins to include in the contexts.

I would suggest to check the universe once. Hope it helps you.

Reagrds,

Rohit

[anupkumar_rai]

Hi Carl,

Check if you still have some context defined in your uiverse. If at all there is a context defined in the universe, then each and every table in the universe should be part of any of the context. Otherwise we get the error of incompatible objects.

Thanks

-Anup-

[Former Member]

Thanks for tyring to help:

the thing is: I do not define real Contexts in universe but just have alias Tables (just to manage the different dates

without "Contexts" to avoid always to difine right context in Query: just take the column from correct ALIAS (e.g. on "tabDates"))

where join is set in universe on the fact-column:

select Tab1.dateCol1 xx (e.g. xMonth = month(fact.xDate )),

Tab2.dateCol1 yy (e.g. yMonth = month(fact.yDate ))

....

from tabDates Tab1, tabDates Tab2

where fact.xDate = Tab1.date and

fact.yDate = Tab2.date.....

but webi does not create a combined select with that join ....

that - i thought should mean - aliasX = Tab1, aliasY = Tab2...

instead creats two selects with "synchronisation" Feature but no sychronisation set

Any idea ?

Edited by: Karl Gust-Stiehl on Sep 11, 2009 12:04 PM

[Former Member]

Hi,

This can be solved by defining context having the two joins. But anyways you have not defined them....

As I see your query I noticed that the from clause doesn't contain any fact table.. This is reason why Web-I is generating the two queries.

from tabDates Tab1, tabDates Tab2
where fact.xDate = Tab1.date and
fact.yDate = Tab2.date.....

i thought should mean - aliasX = Tab1, aliasY = Tab2...

This statement is contradictory to above quote as I gues Tab1 and Tab2 are the aliases of date tables. And you are joining them again with the Alias X and Alias Y, which I am not able to understand.

Ideally this should be the case for 3 tables:

Select atleast 1 object 1from each table

Select Tab1.DateA, Tab2.DateB, Fact.Object
From tabDates Tab1, tabDates Tab2, Fact
where Fact.KeyA = Tab1.KeyA and Fact.KeyB = Tab2.KeyB 

Hope this solves your problem

Regards,

Rohit

[Former Member]

Hi,

In where class try to use fact table for joins and not their aliases. And also try to have 1:1 join for your original fact tables and aliased tablesin universe level.

Cheers,

Suresh Aluri.