Oracle Transactional Business Intelligence

Products Banner

Scheduler Issues

131
Views
7
Comments

Summary

Experiencing intermittent errors with scheduled reports

Content

Is anyone else experiencing any issues with scheduled reports? In the last 24 hours, a couple of our reports came through with the error below, but I re-ran them without any problems. I haven't submitted an SR but will if it continues. In the meantime, just wanted to see if others were seeing the same.

Odbc driver returned an error (SQLExecDirectW). Error Codes: OPR4ONWY:U9IM8TAC:OI2DL65P State: HY000. Code: 10058. [NQODBC] [SQL_STATE: HY000] [nQSError: 10058] A general error has occurred. [nQSError: 43113] Message returned from OBIS. [nQSError: 23006] The session variable, NQ_SESSION.OBIEE_SYSTEM_SECURED_zone_conn_str, has no value definition.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. 

Comments

  • We have not experienced this but I appreciate you sharing this type of information.  Often it's very helpful to know what other cloud clients are experiencing.  Thanks, Wendy

  • I've been seeing this error today, not with scheduling agents, but just trying to generate an analysis within OBI.  I tried a few different ones, all with the same results.  I went in to Edit and got the same message.

  • Hi,

     We have seen this intermittent error while running an OBI Analysis in past. However, it has not occurred since a long time.  As a workaround to get rid of this error, Oracle had suggested to signout, clear browser cache/history, and try login again to access. This had helped us in the past.

    Thanks and Regards,

    Reena Trangri

  • Hi Andy,

    Please update us on this issue as we are facing the same.

     

     

  • Hi Sakshi,

      Have you tried the workaround suggested by Oracle in general for such kind of error? Pls. refer my post above. Is this workaround not helping ?

    ----------------------------------------------------------------------------------------------------------------------

    As a workaround to get rid of this error, Oracle had suggested to signout, clear browser cache/history, and try login again to access. This had helped us in the past.

    ---------------------------------------------------------------------

    Thanks and Regards,

    Reena Trangri

     

  • Over the past couple months, we've experienced this only a couple more times. In each case, the reports ran without issue on the next scheduled instance. I have not logged an SR. We've also seen this occasionally when manually running analyses and Reena's workaround has helped, but the scheduled reports seem to be a different issue.

  • This got resolved for us as well.