Categories
- All Categories
- 15 Oracle Analytics Sharing Center
- 15 Oracle Analytics Lounge
- 215 Oracle Analytics News
- 43 Oracle Analytics Videos
- 15.7K Oracle Analytics Forums
- 6.1K Oracle Analytics Idea Labs
- Oracle Analytics User Groups
- 78 Oracle Analytics Trainings
- 15 Oracle Analytics Data Visualizations Challenge
- Find Partners
- For Partners
AGO function issue in OBIEE 12c
Answers
-
On another note, the report does work fine for other levels of the time dimension like Quarter or Year. Its just the Monthly distribution is causing the issue in the report.
0 -
The query is for sure not a simple 1 line query but a bit more, so it takes some time to read it but still ...
Actually I have a hint for you on how to find the issue ...
For the analysis with the monthly figures vs the same month 1 year ago, try to divide the year ago number by the real number you got (so Jan 2018 Year ago / Jan 2017 Spend). Do it for all the month ....
Surprise: the result is always 31 !
So that tell you something, your "year ago" monthly spend is always multiplied by 31.
Now I don't have access to your system, so can't give you more, but I guess that this is already enough to put you in the right direction.
0 -
Thank you Gianni - This direction is what I was looking for... So happy to find you guys here.. will keep you posted on why this is happening...
0 -
Hello Everybody,
I checked all the design and could not find any issue. So finally we reached out to Oracle on this as a SR and they accepted it as a bug in some environments and provided an alternative solution to fix this. After applying the fix the issue is resolved now. Just wanted to keep all of you updated as you have spent time on this for me.
Thanks again for all your valuable inputs.@Gianni Ceresa@Christian Berg@Joel Acha@Thomas Dodds@ArijitC
Bug 26642083 : OBIEE 12C AGO FUNCTION IS NOT WORKING AS EXPECTED
@ There is some performance enhancement in 9.x and later versions to optimize
@ unnecessary DISTINCT in the physical sql generated based on the table keys in
@ the RPD. It seems it has some side effects causing issue for this customer
@ even
@ though there is no key defined in physical table DWD_ZN_SBRP_SUMM_MO.
@ .
@ There is a compatibility flag to disable the DISTINCT optimization that was
@ added in 11.1.1.9.0 and later versions.
@ .
@ Please use any of these flag in customer env and check if you getting correct
@ results.
@ .
@ set variable OBIS_REDUNDANT_DISTINCT_OPTIMIZATION = 'DISABLED'
@ set variable OBIS_REDUNDANT_DISTINCT_OPTIMIZATION = 'LEAF_ONLY'
0 -
Thanks for the update!
0
