GCP Qlikview Server To On Prem DB Slowness Issues

[ryanfoster84]

Hi,

Was wondering if anyone could assist with the issues we are currently facing. We are building out a GCP server located in US East and its hitting an on prem db server in central US. We are running qlikview 12.70.20200.0 and running Oracle 19C. Issue is when running an extract script with a fetch connection property of 200k it is taking forever to return all records. 

current on prem db returns the total 13m records in 2 mins and is running oracle 12c. Our DBA monitored and said it starts fast but then qlikview seems to be causing the slowness like it is waiting for a minute or so before doing the next fetch (so not a DB issue), has anyone else experienced this? 

Would the Qlikview ODBC connector help with this issue?

Thanks,

Ryan

[Jay_Brown]

Hello @ryanfoster84 ,

If you can test the ODBC driver from the same server that will let you know if it is a driver issue or if it is a locality issue.  Sometimes we do see performance differences across versions so trying with the ODBC driver from the correct versions Client package can be a good way to isolate it.  

If you find a performance issue with the driver with all other things being equal, please report that along with version information.  You can find the driver information from the connectors that ship with Qlik by looking at the .dll > Details in C:\Program Files\Common Files\Qlik\Custom Data\QvOdbcConnectorPackage ...

For example for Oracle: 
C:\Program Files\Common Files\Qlik\Custom Data\QvOdbcConnectorPackage\oracle\lib\OracleODBC_sb64.dll

You could test the OLE DB driver as well for an additional data point. Hope that helps.

[venkatr]

Hi Ryan,

Checking if you were able to find a solve for this issue? We are facing the similar issue as you described above. Appreciate your feedback.

Thanks, Venkat

[ryanfoster84]

Hi,

We downloaded the OCBC Connector from the downloads page of Qlikview and recreated the connections. Works perfectly although its not as fast as on prem to on prem. We have a script that ran in 35 minutes on prem to on prem and now runs in about 58 minutes but this is due to bandwidth in the pipe i guess and other team using the same pipe. 

Thanks,

Ryan