Discussion Board for collaboration on QlikView Scripting.
I have installed QV11 SR2 on our Test Server .
The Dataload via ODBC from our iSeries takes ~ 3 Times longer than with SR1 ...
from 50 Minutes to over 3 Hours !
... does anyone make the same experiences?!
Solved! Go to Solution.
This is the reply I got from Qlikview. Havent test it yet
This email contains download links for the installation files for your customer patch which fixes defect from case 00132430. Bug 53037: Upgrading from v11 SR1 to v11 SR2 slows down reloading, is now therefor considered solved.
Please make sure that all sensitive data is backed up before deploying this patch. By accepting the patch terms and conditions, the end user agrees to install and provide QlikTech with confirmation by email that the patch fixes the associated defect.
QlikTech support always recommends customers running a customer patch to update to the next service release when available.
64 bit Server MSP
64 bit Desktop MSP
I have experience the same issue when upgraded from IR to SR2.
I use System i Access for Windows ODBC data source.
Result was that I revert back to IR
We also have "similar problem", but after diagnostics. the problem on our end is the distribution engine.
We use the standard server license and we limit to the distribution engine to 4 concurrent reloads. After a period of time (# of hours) that we see normal behavior we get into a situation that we see more than 4 qvb.exe processes and pending tasks are stuck.
It looks like the tasks have finished their run, the process is not closed and the distribution engine still counts the task are running, so new tasks cannot be run.
we reverted to qv11 sr1
Our Service Partner opened a Ticket, but they don't receive an usefull answer from QlikTech... they will confirm the bug but don't have a solution yet.
Maybe all of us have to report the Problem to QlikTech to increase the presure ...
Here is the answer I received from QT:
"It is a conflict between the new features and how QlikView works against this database. It will be fixed Q1 next year, but we can not establish an absolute date. The bug has top priority. We highly recommend users to use the previous version.”