Categories
- All Categories
- 15 Oracle Analytics Sharing Center
- 14 Oracle Analytics Lounge
- 211 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
Issue Multi union table in SQL Statement when create dataset + OAS 7.0
Hi,
We create a dataset in Oracle Analytics server 6.4 (Dataset A), and create analysis from Dataset A, it works fine when we filter date from analysis.
Here is dataset A.
And here is the analysis, it created from Dataset A.
And it's working fine in result tab.
After it worked well on OAS 6.4. We exported and import to OAS version 7.0, with same Dataset and Analytics. But it has wrong result (Show all date although we have filter date in analysis)
We see the physical query from logs, on version OAS 7.0. It doesn't have date from where statement. That why the result is wrong.
Can you help to explain/provide the reason about different result?
Thank you so much!
Best Answer
-
Hi User_A8TPU,
Could you update your profile with your name, please!
Thanks for the details and screenshots.
It is difficult to say why the difference, in this case without comparing the system configurations.
Was OAS 2023, an in-place upgrade from OAS 2022, or is it a new out-of-place migration?
Have you opened a service request yet?
0
Answers
-
Hello,
Are you saying that you exported the analysis from Analytics Classic and imported in another instance? When you edit the analysis in that target instance, is the filter missing in the Criteria tab?
How did you export/import the analysis?
Here is you migrate catalog content between instances:
Check if following above steps would work for you.
Regards,
Ezequiel.
0 -
Thank you for your answer. We copy XML file from analysis in OAS 6.4 and paste to OAS 7.0. But it does not filter correctly in OAS 7.0.
Here is the filter in analysis.
And here is the result. It does not filter correctly
Thanks you
0 -
Thank you for your answer. We install new OAS 2023, not migration from OAS 6.4. From SR, we see some customers has the same problem as.
But the solution is not good for us because we need to change a lot of things. Do you have any idea to change parameter from system? because it is working well in OAS 6.4.
Thank you!
0 -
@User_A8TPU If you encounter incorrect behavior,which has been working in previous release of OAS (which seems to be exactly your case) ,create SR with Oracle support and insist on providing the fix for it in OAS 2023 .You will need to create reproducible test case, but this should not be a problem, I guess.
0 -
I was attempting to gather some basic contextual information, but I agree with @Michal Zima , it could potentially be a regression, or something already corrected in the latest bundle patches. Please open an SR with a reproducible test case.
0
