Has anyone run into the error message "XQE-PLN...can not be pushed to any fact streams of the query"?
This happens when I use multi-fact querying where one fact table has non-conformed dimension. Example, I have a Fact 1 and Fact 2 tables with Fact 1 joined to say Dim1, Dim2 while Fact 2 joins to Dim1 alone. When Fact1 and Fact2 are queried against Dim1 data comes out correct but when queried against Dim 2 it throws an error only the 1st time the report runs.
Re-running the report brings back incorrect data but no errors.
This is on 10.2, DMR, DQM using only mdx expressions in the query.
Quote from: eliza_jane on 21 Aug 2013 07:00:26 AM
Has anyone run into the error message "XQE-PLN...can not be pushed to any fact streams of the query"?
This happens when I use multi-fact querying where one fact table has non-conformed dimension. Example, I have a Fact 1 and Fact 2 tables with Fact 1 joined to say Dim1, Dim2 while Fact 2 joins to Dim1 alone. When Fact1 and Fact2 are queried against Dim1 data comes out correct but when queried against Dim 2 it throws an error only the 1st time the report runs.
Re-running the report brings back incorrect data but no errors.
This is on 10.2, DMR, DQM using only mdx expressions in the query.
Well I think in your question you have an answer. If second fact does not have any join with dim 2 how it would produce correct results?
I guess you need to set dimensional scope relationship so any measures from fact 2 would not have any relasionship to dim2.
Forgot to mention, I am pulling in Dim 1, Dim 2 and a calculated member from Fact 1, Fact 2. That is when I run into the strange behaviour.
Ideally I would expect Cognos to get data against Dim 1, Dim2 and Fact 1 and then Dim1 and Fact 2 and then do a full outer join and then calculate the required data item.
Unfortunately that does not seem to be happening here. Whats weird is it throws error and re-running the report a couple of times gets back incorrect data. More strange a list gets me the right result but crosstab against the same query does not.
This is against 10.2.1, DMR, DQM.