Categories
- All Categories
- 15 Oracle Analytics Sharing Center
- 17 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
OBIEE analysis returns [nQSError: 46036] Internal Assertion: Condition pColumn->GetExpr()->IsTarget

Hi all,
on some analysis we get the following error:
Has anyone run into the same problem?
Best regards,
Matej
Answers
-
What is your OBIEE version with complete patch level is it 10g(10.3.x)/11g(11.1.1.X.X)/12c(12.2.1.X.X)?
What is the database source(Oracle, Essbase etc..) for the report which fails with mentioned error?
From the error it looks to be an issue with cache(SQOIGeneratorCache), is simple report/dashboard refresh is resolving the issue or purging the cache resolves the issue?
0 -
OBIEE version: 12.2.1.2.0
Database source is Oracle.
Yes, report refresh (which forces the query to bypass the cache) resolves the issue.
Regards,
Matej
0 -
Check if your report makes use of "IFNULL" in one of the column formulae . Remove it and test.
0 -
That confirms it, that BI Server isn't able to resolve certain piece of code when trying to fetch result for report from cache hence the error(SQOIGeneratorCache), but when cache is not hit then you get your result.
Now it could be of different reason for facing this issue, it can be a product bug or design issue or maybe something else,as far as I know assertion errors occurs when something within the code that should have never happened has happened.
Suggest you to log a ticket with Oracle Support and check with them , whether this issue has been reported before or it's something new that could be bring to there notice.
Did some search on Oracle KM but did not find anything specific to the posted error message.
0 -
Hi Matej,
I faced the same issue in the past. In my case, issue was with the report. There were 'NULL' keyword used in one column formula of the report by the user and removing it resolved the issue.
Thanks
Ebin
0