This content has been marked as final. Show 3 replies
I understand that your star is spread across two different sources.... Fact in Teradata and dimensions in Oracle.
Hhhmm, In this case you may want to use the driving tables for these inter database joins. In the BMM, on the logical join between the dimension and the fact, set the driving tables as dimension. The BI Server would then send to the Fact, the dimension values as parameters.
Ex: select amount from fact where month in ('201201','201202') .
So, this would take off the overhead on the BIServer to get the fact data and dimension data and do a join by itself.
Hope this helps.
first of all thank you for your reply.
Yes you centered my problem, but I tried your suggestion and I'm still having this problem...
I saw in the nqquery.log file the physical query and I've noticed a massive use of the ORDER BY clause in logical query, also in the subqueries. I uncheked the voice in the DB function (in RPD) but nothing changed.
Could be this the problem? How can I remove the order by clause in the logical query? could be usefull?
I don't want to believe that OBIEE cannot manage multi-database simple inner join... and I've no time to develop other ETL procedure.
In anyway I solved my issue implementing other ETL procedures to have dimensions and facts in the same DB (Teradata).
Using the moving table in the logical join, gave me a problem exceeding the MAX_QUERIES_PER_DRIVE_JOIN parameter value and increasing this value the performance get worse.
Edited by: ITom on 15-mag-2012 7.21