QVW reload takes much longer through QMC than when run manually

[Anonymous]

Hello all,

I have a weird issue with a scheduled reload task. The document takes around 3 minutes to reload when completed manually - i.e. by opening the qvw and relaoding. Through the QMC and a scheduled reload, the same document takes 6 hours!!! It's a very simple document that concatenates 2 x simple SQL selects and then stores in a QVD - the reload is hanging during the first SQL select statement.

Has anyone experienced this before - any ideas how I can fix the problem?

Currently using Qlikview version 11.2 SR5 64-bit.

Thanks in advance!

[#2]

Jo, I have the same scenario, but 6 hours is too long. You need to check.

[Anonymous]

Hello,

Unfortunately it is definitely taking around 5.75 - 6 hours on a daily basis - I have the logs to prove it....

18/08/2014 01:00:03.4128414	Information	18/08/2014 01:00:02: 0066  OLEDB CONNECT*Provider*XPassword*
18/08/2014 01:00:03.4128414	Information	18/08/2014 01:00:03: 0069  IBTMachines2:
18/08/2014 01:00:03.4128414	Information	18/08/2014 01:00:03: 0070  LOAD MACHINE
18/08/2014 06:59:34.6258529	Information	18/08/2014 01:00:03: 0071  SQL	SELECT DISTINCT MACHINE
18/08/2014 06:59:34.6258529	Information	18/08/2014 01:00:03: 0072		FROM xxx.dbo."GENERIC_EVENT"
18/08/2014 06:59:34.6258529	Information	18/08/2014 06:59:34:	1 fields found: MACHINE, 477 lines fetched
18/08/2014 06:59:34.8445986	Information	18/08/2014 06:59:34: 0075  Concatenate(IBTMachines2)
18/08/2014 06:59:34.8445986	Information	18/08/2014 06:59:34: 0076  LOAD MACHINE
18/08/2014 06:59:37.4708888	Information	18/08/2014 06:59:34: 0077  SQL	SELECT DISTINCT MACHINE
18/08/2014 06:59:37.4708888	Information	18/08/2014 06:59:34: 0078		FROM xxx.dbo.TIMESTAMP
18/08/2014 06:59:37.4708888	Information	18/08/2014 06:59:37:	1 fields found: MACHINE, 1,050 lines fetched

[ergustafsson]

Hi Jo,

Clearly, something is wrong with the database connection. I recommend you to double check that you are using a System DSN and not a User DSN for database connector, and that all credentials are identical, and the connection string still is valid.

Regards,

Erik

[Colin-Albert]

Could the delay be due to a backup or other task that is running during the night and locks the database / tables until complete?

How long does the task take on the server when started manually?

Does the task take 6 hours when running at a different time of day?

[Giuseppe_Novello]

Jo,

check the Task log/ document logs, check were the actual delay occurs. If you have publisher, maybe the issue is during the distribution process not the reload process.

gio

[Colin-Albert]

Perhaps you could add a "nolock" hint to your database query

[Anonymous]

After further testing, I've determined that it does appear to run without issue at other times of the day whether manually started or via the scheduler. It turns out that there was a job scheduled to run at the same time on the SQL database that I wasn't aware of. It looks likely that this is the culprit so have disabled it for now and will see tonight whether the Qlikview task runs successfully.

Thanks everyone for the replies and pointing me in the right direction!!