Qlik Community

QlikView App Dev

Discussion Board for collaboration related to QlikView App Development.

Announcements
QlikWorld 2022, LIVE in Denver CO., May 16-19, 2022. REGISTER NOW TO RECEIVE EARLY BIRD PRICING
cancel
Showing results for 
Search instead for 
Did you mean: 
Not applicable

"Direct Query Failed" Error using Direct Discovery

Hi

I am using QV 11.2 SR7 version client. Using the Direct Discovery feature, I am trying to fetch data from SAP HANA database(Calculation View) using ODBC connection.

So my script reads like below:


ODBC CONNECT32 TO HDB;


DIRECT QUERY

DIMENSION

SALESMANNAME,

COUNTRYNAME,

REGIONNAME,

AREANAME,

OUTLETGRPNAME,

TEOUTLETTYPECODE,

OUTLETTYPENAME

MEASURE

CALLFREQ,

NO_STORES

FROM

"_SYS_BIC"."CPG.dra/Z_CA_DIST_OUTLET_COUNT";

This all works fine.

However when I create a bar chart or straight table with any of the above mentioned Dimensions and Expressions,

it just displays an error message saying "Database connection failed" or if I create a table box with any of the Dimension,

it gives error as "Direct Query Failed".

Has anyone come across similar errors?
Your help and inputs are highly appreciated.

Thanks in advance

Sabal

10 Replies
Not applicable
Author

Hi All,

Any idea about this?

Thanks
Sabal

alvinford
Contributor III
Contributor III

Dear Sabal,

Did you able to find the solution for this. Facing the same issue.

Regards,

Alvin.

aaroncouran
Creator III
Creator III

bump.  Same issue here.  Connecting to SQL.

Vegar
MVP
MVP

Did you ever solve this issue?

Do anyone else have a suggestion for a solution?

I ran into the same problem yesterday when trying to connect an Oracle database with ODBC. Reading data in the script works fine, but 'Database connection failed' shoes on all objects where I try calculate a measure.

I'll update this post if I find something that solves this issue.

Cheers

Vegar

Plees ekskuse my Swenglish and or Norweglish spelling misstakes
hirenp0904
Contributor
Contributor

Did you get reply on this? Could you share the response.

Vegar
MVP
MVP

In  my case the issue disappeared when I changed my where statement. I had a date in it, nu when I changed it to a  Char I had no problem with it anymore.

The strange part  is that the original query worked if I ran it as a SQL select statement, but not direct query.

Plees ekskuse my Swenglish and or Norweglish spelling misstakes
Not applicable
Author

Sorry guys...
I still did not find the solution for this.

alec1982
Specialist II
Specialist II

I have the same issue.. anyone got a fix?

Not applicable
Author

The same problem here.

QV version - 11.20.12904.0 SR12 x64

Cloudera ODBC Driver for Hive - 2.05.16.1005