Oracle Database Connectivity

[#1]

Hey guys,

I have a pretty basic connection.

In the Qlikview Edit Script, I'm trying to connect to an Oracle DB data source using an ODBC connection

When I go to look for a list of drivers on my Windows machine (Control Panel -> Administrative Tools -> Data Sources (ODBC), I only see SQL Server.

Any ideas as how I can get Oracle ODBC driver show up here? I tried installing many Oracle Driver programs but none of them is helping to get the Oracle driver show up in the list of drivers.

Thanks for your help.

[biester]

Usually you have to install an Oracle client (even today I needed an Oracle ODBC - not for QlikView but for another reason and installed - or rather copy - the Instant client 10 with ODBC - see
http://www.oracle.com/technology/tech/oci/instantclient/index.html).

Anyhow, I would prefer OLEDB for Oracle for QlikView which also needs an Oracle Client, but as far as I remember a "grown up" Client, Instant Client is not sufficient. Usually OLEDB comes with the client, see
http://www.oracle.com/technology/tech/oci/instantclient/index.html
for details.

I have had an issue with QlikView and Oracle ODBC (don't remember the versions) where e. g. a value of 200 in the database resulted in 200,0000000001 in QlikView - but only in QlikView. When reading the value via ODBC e.g. by a simple VBScript, the correct value of 200 was returned. Since then I ain't used ODBC for Oracle for QlikView any more (besides, OLEDB should actually be faster and should be the better choice anyhow).

Rgds,
Joachim

[#3]

Hi,

A quick thought - I had a similar issue. None of the oracle ODBCs were showing up for me in th QW client installed in the server. Finally, when I installed Client64 bit insted of the other one, issue got solved.

Something like this? See the version detals in the help and if not 64, try this.

Good luck,

-Arun

[biester]

That's correct, the 64/32 bit problem is also a known issue. AFAIR you need to call odbcad32 if installing a 32 bit ODBC on a 64 bit machine or something like that. Nevertheless I seriously recommend OLEDB.

Rgds,
Joachim

[Anonymous]

Even with OLEDB, you need 64-bit Oracle client for QV 64-bit, and 32 for 32. QV doesn't see "wrong" client.
Warning - I was never able to make Publisher 32 to reload from Oracle (neither ODBC nor OLEDB), although QV Developer on the same machine was fine. Didn't have this problem with Publisher 32. Version 8.01 and 8.50. Apprciate if anyone can share positive experience.

[biester]

Michael is of course right. I was suggesting to prefer OLEDB for the mentioned reasons, not because you don't have to worry about 64 or 32 bit ...

Rgds,
Joachim