Friday, December 1, 2017

BICS report execution result in "the user request exceeded the maximum query governing execution time"

Some of the reports in BICS results in following error but same report in on-premise OBIEE run successfully against the same Datawarehouse.

Odbc driver returned an error (SQLExecDirectW).
 Error Details
Error Codes: OPR4ONWY:U9IM8TAC:U9IM8TAC:U9IM8TAC:U9IM8TAC:OI2DL65P
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: 60009. [nQSError: 60009] The user request exceeded the maximum query governing execution time.
Please have your System Administrator look at the log for more details on this error. (HY000)
Please have your System Administrator look at the log for more details on this error. 


This is due to the Query governor set in BICS.  Given that BICS is a cloud service and in cloud,  user query need to be controlled in order to make sure environment is stable and can scale.  This is done by introducing the query governors.  Query execution timeout is set to 600 seconds and this is hard limit.  Customer cannot request to change this hard limit for their BICS instance so report need to be re-design so that DB query runs within 600 seconds.

This limitation will not be there in OAC since OAC is external PaaS and customer will be able to change the limit as per their own requirement. 





No comments: