topic Oracle reload problem with missing data records in QlikView

Oracle reload problem with missing data records

Thu, 21 Jul 2011 14:56:00 GMT

We are running Qlikview Server (with Publisher) against an Oracle datasource, and have had 3 instances over 10 weeks where QV says the script has reloaded successfully but when we look at the loaded data some of it is missing. If the script is executed again it returns the full dataset.

This is a major concern for us because we need to rely on the scripts loading all the data every time. If there is a problem it should error, not say it was successful. Alarmingly we are talking about relatively small datasets (e.g. 120,000).

For now we are monitoring the datasets each day for obvious discrepencies, but it's far from ideal.

We are on QV10.2, Our data source is Oracle 11gR2, connecting with 64 BIT ODBC drivers.

The issue has been logged with Qliktech but all they have suggested so far is to try OLEDB. We are trying this but because the fault is intermittent it might not be conclusive. Has anyone had a similar problem or have any suggestions on what else to investigate

Thanks

Andrew

Oracle reload problem with missing data records

ashfaq_haseeb — Sat, 23 Jul 2011 07:57:30 GMT

Hi,

I face the same problem with v10 sr2.

The work around for this is.

Delete that specific reload task, add now task with some other name.

Also alter the dependent tasks.

Restart the services.

Then run schedule.

Hopefully this will resolve your problem

Regards

ASHFAQ

Re: Oracle reload problem with missing data records

Thu, 28 Jul 2011 11:05:10 GMT

Hi Ashfaq

Thank you for your suggestion.

The problem we have seen is intermittent and randomly affects different tasks at different times.

When you had this problem was it affecting the same task all the time?

Which drivers were you using to connect to Oracle?

Andrew

Re: Oracle reload problem with missing data records

Thu, 14 Jun 2012 14:01:37 GMT

It was a long time coming but QlikTech have finally recognised this as a fault and are working on a fix. See my posts on this separate thread - http://community.qlik.com/message/215900?tstart=0#215900