Categories
- All Categories
- 89 Oracle Analytics News
- 7 Oracle Analytics Videos
- 14.1K Oracle Analytics Forums
- 5.3K Oracle Analytics Idea Labs
- Oracle Analytics User Groups
- 51 Oracle Analytics Trainings
- 59 Oracle Analytics Data Visualizations Gallery
- 2 Oracle Analytics Data Visualizations Challenge
- 4 Oracle Analytics Career
- 4 Oracle Analytics Industry
- Find Partners
- For Partners
nQSError: 14023 Error Coming In OAC
Hi Team,
I am facing below issue when one column added into criteria..
Could you please help me to understand what could be the issue from above error message.
Regards
Saroj
Best Answers
-
Hi,
You are probably using attributes and measures coming from various dimensions and fact tables, and not all of them are connected or have the right content level defined.
The column you added comes from something (dimension or fact table) that doesn't have any connection with something else that is already part of your analysis.
The answer to this is inside your RPD.
0 -
Hi,
Thanks for all responses. There are joins missing actually in multiple LTS available in BMM layer. Now i have properly done joins. So that nQSError: 14023 not coming.
But we are facing "No Results" coming in OAC Report.
Attached snapshot .
Snapshot 1,2,3 working fine as per RPD design.
But when we add column from Snapshot 4 it's showing No Results data.
Can you help us to understand this issue.
0
Answers
-
+1 to Gianni. Your dimensional model isn't configured in a way which supports your combination of dimensions and facts.
Most likely your business model was set up to contain all those logical tables you're selecting from but has not been properly configured with regard to conformed / non-conformed dimensions as well as the necessary logical table source content levels in order to make the combinations work.
You have to investigate inside your RPD and resolve the issue there. The engine does as it is instructed. If the instructions are wrong then it can't work with them.
0 -
To add, if you had some incorrect syntax in a column formula. In OBIEE, it would replace with a null and keep querying; wherein, OAC/OAS returns an error (as it properly should).
0 -
@SteveF-Oracle true. We can't see the whole list of referenced columns but from what is visible it looks just like an extremely wide list of attribute columns. I.e. a pure dimension-only listing of dozens of attributes without a fact table specified. Or if there is a fact it's one that can't serve those dims due to missing nonconformed dimension resolution.
1 -
Now i have properly done joins. So that nQSError: 14023 not coming.
These joins define what comes back. If you get no data you need to verify what SQL your new model now produces.
Again it's all in the model. Creating joins is one thing. Creating the correct joins which combine the correct data is the other thing.
1 -
Can you help us to understand this issue.
The only truth is the physical query executed against your data source. You have "no results" when adding a new column in an analysis? Open the logs, find the physical query generated and that's how you fill find out why no data can be found for that query.
OAC doesn't do any magic, it only generate queries based on the model in the RPD. You can easily model something that looks right for you, but that then generate queries with no results.
But here again the only way to understand what is going on is by looking at the queries generated, run them on your database directly and start "debugging" the query to find out what join is generating the "no results".
And also, "no results" is not an error, it can be a perfectly valid result, it all depends what you try to do, what you model, what OAC is trying to do. But the query is the only you need to look at.
1 -
i agree with @Gianni Ceresa best way get the physical query from log session and try to execute in your DB side using SQl Developer or any other tool engage your DBA to make sure all of your joins correct plus data validation in sample group of data in your DB Tables
0