How to fix the query getting cancelled in OBIEE?

Modified on Fri, 6 Sep, 2019 at 4:44 AM

A query that has not been executed before a specified time (set in 'UnaccessedRunningTimeoutMinutes') in OBIEE, is considered as unattended and it is cancelled by OBIEE.

As per the oracle OBI documentation the default time for a running query (UnaccessedRunningTimeoutMinutes) is 2 minutes. Without updating this setting, the long running query will be consistently cancelled by the OBIEE.

Changes to be done in OBIEE Server:

Step-1: Add <UnaccessedRunningTimeoutMinutes>60</UnaccessedRunningTimeoutMinutes> under <ODBC> tag in instanceconfig.xml of Oracle BI Presentation Services instances.

The instanceconfig.xml will be located under "ORACLE_INSTANCE\config\OracleBIPresentationServicesComponent\coreapplication_obipsn"
For example: "\instances\instance1\config\OracleBIPresentationServicesComponent\coreapplication_obips1"

Instanceconfig.xml

Step-2: Once you added the UnaccessedRunningTimeoutMinutes, restart the server.

Here is an OBIEE document link for your reference.

Changes to be done in BI Connector Server and Desktop Edition:

Now change the custom HTTP timeout under Advanced setting of BI Connector DSN to 60 minutes or higher (Please refer this article).

Note:

We believe that setting a timeout of 60 minutes at the OBI and BI Connector side would be optimal, assuming that the query execution and data extraction from the OBI side is complete within 60 minutes. Also, reducing the number of columns in the query will likely avoid the query getting cancelled on the OBI side.

If you have any questions or comments, we are just a click away. Contact us at support@biconnector.com or file a ticket at our support portal.