Categories
- All Categories
- Oracle Analytics and AI Learning Hub
- 42 Oracle Analytics and AI Sharing Center
- 20 Oracle Analytics and AI Lounge
- 277 Oracle Analytics and AI News
- 54 Oracle Analytics and AI Videos
- 16.2K Oracle Analytics and AI Forums
- 6.4K Oracle Analytics and AI Idea Labs
- Oracle Analytics and AI User Groups
- 103 Oracle Analytics and AI Trainings
- 19 Oracle Analytics and AI Challenge
- Find Partners
- For Partners
After upgrading to OBIEE12c getting odbc driver error
After OBIEE upgrade I am facing "Odbc driver returned an error (SQLExecDirectW)"
All reports are erroring out
Answers
-
http://catb.org/~esr/faqs/smart-questions.html#beprecise Expand the error message - what's the detailed error message? Check the Presentation Services and BI Server logs. You'll find the error, and probably the cause, directly there.
0 -
Beaten to the punch by Robin. Needs more detail. Needs more analysis.
0 -
2636702 wrote:
After OBIEE upgrade I am facing "Odbc driver returned an error (SQLExecDirectW)"
All reports are erroring out
Not going to repeat what Christian and Rmoff posted, but also opening a thread with a link to a MOSC thread 1 year old ... what's the theory? First a MOSC space is something else and with limited access vs this one being public. And I guess you could at least write your own question
0 -
Its my own question, and I am facing it currently in the upgrade process.
State: HY000. Code: 10058. [NQODBC] [SQL_STATE: HY000] [nQSError: 10058] A general error has occurred. (HY000)
State: HY000. Code: 43113. [nQSError: 43113] Message returned from OBIS. (HY000)
State: HY000. Code: 43119. [nQSError: 43119] Query Failed: (HY000)
State: HY000. Code: 16001. [nQSError: 16001] ODBC error state: IM002 code: 0 message: [DataDirect][ODBC lib] Data source name not found and no default driver specified. (HY000)
0 -
Out of interest, what research have you done so far into the error? On the forum we love to help people out, but it cuts both ways - you need to show you've put in some leg work already. That error is a massively common one. Have you gone to My Oracle Support, for example, to look it up? Or searched the forum history to see common causes, and investigated whether they're applicable to your environment?
0 -
