Categories
- All Categories
- 15 Oracle Analytics Sharing Center
- 15 Oracle Analytics Lounge
- 214 Oracle Analytics News
- 42 Oracle Analytics Videos
- 15.7K Oracle Analytics Forums
- 6.1K Oracle Analytics Idea Labs
- Oracle Analytics User Groups
- 78 Oracle Analytics Trainings
- 14 Oracle Analytics Data Visualizations Challenge
- Find Partners
- For Partners
12c Data Issue

Hi All.
We are experiencing this weird behavior on our 12c (12.2.1.2.0 (Build BIPS-20160923092103 64-bit)) environments.
There is an analysis with a pivot table that has a prompt with only two values (for example YES and NO, YES being default). Now, when the the analysis is run, the results are incorrect with the prompt value YES.
When we change the prompt value from YES to NO, results are correct for NO. Now, once we change back from NO to YES, results are correct. So, essentially, when the analysis is run, first set of results are wrong. But changing the prompts produces correct results.
An example to make more sense-
First run (wrong results):-
Prompt changed (correct results):-
Prompt is changed back to initial value (correct results, at last):-
Source is TImesTen. On 11g there is no issue. Both 11g and 12c have same model and both have common TimesTen source.
Anyone any idea? Thanks.
Comments
-
Hi,
Did you looked at the generated queries in the 3 cases and compared them? First the logical one and then the physical one?
Did you manage correctly the default value in your analysis for when the prompt isn't set?
Is your cache on or off?
0 -
Just to add to @Gianni Ceresaresponse above, I'd check the query log files to check whether the filters are being correctly set for each of the scenarios.
0 -
24506898
One-off patch. You're welcome. Next question.
0 -
Thanks a lot Christian. Not sure if we have the same problem as I could not read the complete bug description. Sounds pretty similar though.
Requested Bug could not be displayed. Possible reasons are:
- The bug id was entered incorrectly. Please check and try again.
- The bug id does not exist (was referenced incorrectly).
- The bug is not classified as publicly accessible ("non-public").
- The content is being updated and it is temporarily unavailable but will be made available again soon.
If you still have questions about why you could not access this article or bug, please use Contact Us.
Should I create an SR to know more?
0 -
It's pretty certainly that bug. Never saw anything else cause this in 12. Just download the patch and patch one of your environment's. It's 700KB and costs you exactly one shutdown, one opatch apply, one startup.
And a rollback is easily done.
0 -
Hi,
We tried to apply the patch, but it complains that a more recent patch has already been updated.
Any suggestion? Thanks
0 -
Err what patch did you install? One of the BPs?
0