Skip to main content
cancel
Showing results for 
Search instead for 
Did you mean: 
enricocamerin
Creator
Creator

Oracle Driver unstable. Not all the rows are loaded

Hello we are using the release  June 2018

Regarding the connection we are using  the oracle driver.

When I load the script each time I have a different number.

I isolated a fragment of the sql script with only the select  removing the load .

So the problem is somehow in the connector.

if I run the query in toad I have for example 400000 row

The same sql loaded  in qliksense gives only 35000 rows, but sometime( 10 second later) it gives the correct number 400000.

then if I add a field in the select the number change again.

The behaviour is very weird and unstable.

in the previous release we used the Qlik odbc connector package with no problem

thanks in advance for your suggestion

Enrico

1 Solution

Accepted Solutions
bi_licenze
Contributor II
Contributor II

I had the same issue. If you look in the event viewer you'll see a crash of Qvodbcpackageconnector.

As a workaround you have to rename the folder

C:\Program Files\Common Files\Qlik\Custom Data\QvOdbcConnectorPackage

in _OLD and copy the folder of Qlik Sense April2018.

Oracle connector in June 2018 is not working fine.

Bye,

Simone.

View solution in original post

12 Replies
ZDonn
Contributor II
Contributor II

PabloTrevisan
Partner - Creator II
Partner - Creator II

If the problem is instability, you can parallelize the select since you are making the connection between qliksense and oracle without eg sap connector ...


the command:

SET StripComments =0;

EKKOtab:

SQL SELECT /*+ PARALLEL(VBRK 😎 */ FIELD1,FIELD2

FROM VBRK;

SET StripComments=1;

or

EKKOtab:

SQL SELECT --+ PARALLEL(VBRK 😎  FIELD1,FIELD2

FROM VBRK;

Godd lucky !

enricocamerin
Creator
Creator
Author

Thanks Pablo I tried but it didn't solve the problem  I still have weird result.

bi_licenze
Contributor II
Contributor II

I had the same issue. If you look in the event viewer you'll see a crash of Qvodbcpackageconnector.

As a workaround you have to rename the folder

C:\Program Files\Common Files\Qlik\Custom Data\QvOdbcConnectorPackage

in _OLD and copy the folder of Qlik Sense April2018.

Oracle connector in June 2018 is not working fine.

Bye,

Simone.

ZDonn
Contributor II
Contributor II

This actually works! Easier than going through the whole Oracle ODAC thing. I used the oracle package (~\AppData\Local\Programs\Common Files\Qlik\Custom Data\QvOdbcConnectorPackage\oracle) from Qlik Sense Desktop April 2018 release, as attached, to replace the one in the new Qlik Sense June 2018 under the similar folder C:\Program Files\Common Files\Qlik\Custom Data\QvOdbcConnectorPackage.

enricocamerin
Creator
Creator
Author


Thanks Simone I have sent the procedure to the IT department

I'll let you know

enricocamerin
Creator
Creator
Author

Thanks for the Driver I'll let you know as soon as we carry out the process

enricocamerin
Creator
Creator
Author

thanks it Works !!

pietvanduijn198
Partner - Contributor
Partner - Contributor

Do you need any other actions after the replacements, because i had NO oracle driver now.

Unkown connection type "QvOdbcConnectorPackage"  is mentionned within data connection.