COGNOiSe.com - The IBM Cognos Community

IBM Cognos 10 Platform => Cognos 10 BI => Active Reports => Topic started by: Deep750 on 17 Feb 2017 04:08:17 AM

Title: AR doesn't complete when aggreating measure with sets
Post by: Deep750 on 17 Feb 2017 04:08:17 AM
Hi,
I have made an active report. The typical calculation is
aggregate([Measure] within set [set1]; [set2])
And the reports has in total around 20 calculations.

[Set1] has one member, which is a year or month. while [Set2] has two members, from a regular dimension.
The issue is that the report wont complete. When I say complete, it really doesn't. I have even let it run over night, and it still doesn't. It doesn't throw any errors, just keeps on running.

But if I change [Set2] to include one member, the report completes within 30 seconds. I have tried every single member, and all runs fine if I include only one.

What I have tried:
Used the same query and added all the calculations to a single list, within an AR. It completes within a couple of seconds.
Used another dimensjon, adding two members. The result is the same - the report doesn't complete.
Does anyone have any suggestions?

source: dynamic cubes
system: I have tested on 10.2.1 FP9 and 10.2.2 FP7
Title: Re: AR doesn't complete when aggreating measure with sets
Post by: AnalyticsWithJay on 17 Feb 2017 07:41:47 AM
Is this behavior reproducible with other dimensions? Or only this one?

Could you capture the native SQL first and check for the differences?
Title: Re: AR doesn't complete when aggreating measure with sets
Post by: Deep750 on 20 Feb 2017 03:17:25 AM
Thank you for your answer, Jay.
I have tried changing dimension, with the same result.



The SQL's seems fine, where the only difference is as expected, where the set creates  WHERE-clause with the two set-members, instead of the one.
As the report-running creates more than 40 SQLs, I have checked just one, and compared. The execution time for both is less than 0,5 seconds, and the difference for the compared SQL is 3 rows, 38 vs. 41

Edit: I tried adding the same calculations in a new AR and an ordinary Report studio-report. The result is the same...which makes me starting wonder...