Skip to main content
Announcements
Introducing Qlik Answers: A plug-and-play, Generative AI powered RAG solution. READ ALL ABOUT IT!
cancel
Showing results for 
Search instead for 
Did you mean: 
Not applicable

Direct Discovery + QlikView 11.2 SR 5 + Error: Database Connection Failed/Direct Query Failed on making a selection in the Dimension

Am trying to implement direct discovery on qlikview 11.2 sr5. My underlying table is in Oracle and am connecting via ODBC connection.

The direct query loads fine and after the reload, when I try to make a selection to see D/D in action, it fails saying Direct query failed(table box) and database connection failed(for a chart with dimension and expression as count(measure))..as shown in the attached image

I ran a trace on the ODBC and see this statement as a SQL ERROR and another statement as shown below with a invalid identifier message, when selecting a value in the dimension..

X ODBC          9b0-2420ENTER SQLSetStmtAttrW
SQLHSTMT            0x0000000005BCF3F0
SQLINTEGER                   4 <SQL_ATTR_ASYNC_ENABLE>
SQLPOINTER                 1 <SQL_ASYNC_ENABLE_ON>
SQLINTEGER                  -6

X ODBC          9b0-2420EXIT  SQLSetStmtAttrW  with return code -1 (SQL_ERROR)
SQLHSTMT            0x0000000005BCF3F0
SQLINTEGER                   4 <SQL_ATTR_ASYNC_ENABLE>
SQLPOINTER                 1 <SQL_ASYNC_ENABLE_ON>
SQLINTEGER                  -6

DIAG [S1C00] [Oracle][ODBC]Driver not capable. (0)

Also, this is the logged text when I make a selection..

X ODBC          2a58-2024 ENTER SQLExecDirectW

  HSTMT               0x0000000005D8F3F0

  WCHAR *             0x000000000246ED18 [      -3] "SELECT COUNT("EVENT") FROM "TEMP" WHERE "MONITORING_TYPE" IN ( "a" )\ 0"

  SDWORD                    -3

X ODBC          910-24c4 EXIT  SQLErrorW  with return code 0 (SQL_SUCCESS)

  HENV                0x00000000008E89E0

  HDBC                0x00000000008E8AB0

  HSTMT               0x0000000005C9F3F0

  WCHAR *             0x0000000002502C18 [       5] "S0022"

  SDWORD *            0x000000000012EA68 (904)

  WCHAR *             0x00000000025DC458 [     158] "[Oracle][ODBC][Ora]ORA-00904: "a": invalid identifier\ a\ 0\ 0\ 0\ 0\ 0\ 0\ 0\ 0\ 0\ 0\ 0\ 0\ 0\ 0\ 0\ 0\ 0\ 0\ 0\ 0\ 0\ 0\ 0\ 0\ 0\ 0\ 0\ 0\ 0\ 0\ 0\ 0\ 0\ 0\ 0\ 0\ 0\ 0\ 0\ 0\ 0\ 0\ 0\ 0\ 0\ 0\ 0\ 0\ 0\ 0\ 0\ 0\ 0\ 0\ 0\ 0\ 0\ 0\ 0\ 0\ 0\ 0\ 0\ 0\ 0\ 0\ 0\ 0\ 0\ 0\ 0\ 0\ 0\ 0\ 0\ 0\ 0\ 0\ 0"

  SWORD                     2047

  SWORD *             0x000000000012EA00 (158)

X ODBC          2a58-2024 EXIT  SQLExecDirectW  with return code -1 (SQL_ERROR)

  HSTMT               0x0000000005D8F3F0

  WCHAR *             0x000000000246ED18 [      -3] "SELECT COUNT("EVENT") FROM "TEMP" WHERE "MONITORING_TYPE" IN ( "a" )\ 0"

  SDWORD                    -3

  DIAG [S0022] [Oracle][ODBC][Ora]ORA-00904: "a": invalid identifier

(904)

Any thoughts...?? Ideas?? to make this thing work..

Message was edited by: Sagar Addepalli

1 Solution

Accepted Solutions
Not applicable
Author

Thanks for the reply Filippo...However, it wasn't really an odbc or data issue..

I believe it was more of some server setup-the 64bit 32 bit, connect32 and connect64 statements that I had to look into to get my problem fixed.

View solution in original post

4 Replies
oknotsen
Master III
Master III

I hope you are making a typo, but in case you do not:

Are we talking about QlikView 11 SR5 or QlikView 11.2 SR5?

Direct Discovery does not exist in 11.0 only in 11.2, but again: Hoping that is just a typo.

If not, that is your problem.

May you live in interesting times!
Not applicable
Author

Onno

No. Its not 11.0. Sorry for that.

Am talking QlikView 11.2 SR 5.

Filippo_Nicolussi_P

Do you start checking from ORA-00904 invalid identifier tips

Help users find answers! Don't forget to mark a solution that worked for you! If already marked, give it a thumbs up!
Not applicable
Author

Thanks for the reply Filippo...However, it wasn't really an odbc or data issue..

I believe it was more of some server setup-the 64bit 32 bit, connect32 and connect64 statements that I had to look into to get my problem fixed.