Categories
Dashboard sometimes loads in ODBC error state

Hi everyone,
So i've been dealing with a very strange phenomenon with our dashboards. We are on 11.1.1.7.150120 and hitting a sql server db, heres our setup:
We have a dashboard that is automatically triggered by agents which send out via email to run at 4:30am daily.
Sometimes theres no issues but sometimes the email contains odbc errors.
So what i would do is id log into the dashboard and see its in that error state. The weird thing now is if i click refresh, it goes away and the data i expect to see shows up. Then if i manually run the agents, the email gets delivered without errors.
Heres the full error msg:
Odbc driver returned an error (SQLExecDirectW).
Error Details
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: 43119] Query Failed: Please have your System Administrator look at the log for more details on this error. (HY000)
Ive looked at the nqserver log via enterprise manager log viewer and i see this:
This is not the error i see on the dashboard or in the agent email. Does anyone have any ideas that i could try out or have you seen this behavior in a dashboard? I have never seen dashboards load up in an error state then errors go away if i click refresh. Seems like some sort of initial connection issue which gets resolved if i were to click refresh.
Any help is greatly appreciated. Thank you!!
Answers
-
What is the data source? Are you using caching?
0 -
Hi christian,
Thanks for your response. The data source is sql server 2008 and we are not using caching. I've got the cacheable checkbox unchecked in the RPD as well as cache enabled checkbox unchecked in the EM.
0 -
Check the analysis construction in detail. What queries get fired, is it maybe some direct DB request that's involved, does it use opaque views in the RPD etc.
Simplest way would be to recreate the analysis in question manually again and re-test with that. Maybe it's some left-over bad config.
0