nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Oracle Communities

Oracle Analytics and AI

Child Item

OBIEE Reports throws error but after clicking "Refresh" button it works

KBabu

Hi All

Few OBIEE Reports in our system throws error but after clicking "Refresh" button it works.

Check1:

Try to change something in report and resave the report, this should solve problem if not, try to get same report from previous release,code base or from backup using Catalog Manager bring the report to new development by Export/Import report.

Check2:

Try set parameter in NQSConfig.INI file as below :

WORK_FILE_COMPRESSION_LEVEL = 0 ;

Check1 works well at that time only but breaks next day. However user is not interested to click "Refresh" button always to get the report. Not sure where its missing and any suggestions/fixes will be really helpful

We use 12.2.2.0.0 (Build BIPS-20170417212246 64-bit)

Find more posts tagged with

Accepted answers

All comments

Joel Acha

Have these reports been recently migrated from 11g to 12c? If so, how were they migrated?

KBabu

Hi Joel

Thanks for replying.Yes They migrated couple of months back from 11g to 12c.

migrated some reports through catalog manager and some reports through Archive & Unarchive approach across environments.

Not all reports throws error but few reports are behaving like this

ArijitC

I am wondering if this is related to cache setting. Can you check what value being present in the OBIEE instanceconfig.xml (location = $DOMAIN/config/fmwconfig/biconfig/OBIPS) file.

make sure the "RefreshIncludeBIServerCache" variable is true in the OBIEE instanceconfig.xml file

...

<Cache>

<Query>

</Query>

</Cache>

....

</ServerInstance>

</WebConfig>

Thanks

Arijit

ArijitC

More on this you can read here Doc ID 2352581.1

KBabu

Hi Arijit

Thanks for replying.

The Doc ID 2352581.1 tells report is not refreshed after clicking the "Refresh" link on an existing dashboard within OBIEE does not dynamically add "OBIS_REFRESH_CACHE=1;" to the analysis preventing the OBIS to execute the SQL from DB.

but our OBIEE reports throws "View display error" and its gone after you click "refresh" link.

However let me check my settings once

Robert Angel

If cache does not clear your issue you might want to try making a trivial change, save, unmake a trivial change, save - i.e. regenerate the report on the current version.

Btw - you also do not say what the error is that manifests?

KBabu

Hi Robert

Error
	View Display Error
	State: HY000. Code: 10058. [NQODBC] [SQL_STATE: HY000] [nQSError: 10058] A general error has occurred. Please have your System Administrator look at the log for more details on this error. (HY000) State: HY000. Code: 43113. [nQSError: 43113] Message returned from OBIS. Please have your System Administrator look at the log for more details on this error. (HY000) State: HY000. Code: 43119. [nQSError: 43119] Query Failed: Please have your System Administrator look at the log for more details on this error. (HY000) State: HY000. Code: 46036. [nQSError: 46036] Internal Assertion: Condition pColumn->GetExpr()->IsTargetColumn(), file server/Query/Optimizer/ServiceInterfaceMgr/Src/SQOIGeneratorCache.cpp, line 78. Please have your System Administrator look at the log for more details on this error. (HY000) The above is the error which we are getting. After clicking "Refresh" link in the report, the error gone. However, i am yet to get my admin password to check which @Arijith suggested and will surely let you both know about this issue is fixed or not after adding the HTML Tag <RefreshIncludeBIServerCache>true</RefreshIncludeBIServerCache> Thanks All

Ebin Cherian

Hi,

I faced similar issue with a report in OBI 12 C. Not remembering the exact error message, but it was similar to what you have described. I tried lot of MOS document, but nothing helped. Started looking at the report in detail and found that in one of report column formula 'NULL' was used. This was used to introduce some empty space for report formatting. Removing that column resolved the issue. Not sure if that applies to you, but sharing my experience on this issue.

Thanks

Ebin