topic Re: Qvw error in QMC in Management & Governance

Qvw error in QMC

lucasx15 — Mon, 02 May 2022 13:32:46 GMT

Hi, everyone!

I'm having a problem updating a QVW file in QMC (and on my machine too). I use it as an Oracle database. It always returns the error: QVX_UNEXPECTED_END_OF_DATA on the line specifies 57200, when I use the string OLEDB CONNECT . But when using the string OLEDB CONNECT32, it only loads half of the lines. However, my database has more than 123000 rows.

Re: Qvw error in QMC

rohitk1609 — Mon, 02 May 2022 14:58:52 GMT

Please share more information about the issue. What exact code fails? Is there any restriction of data download from Oracle database for service or connecting user?

What if you download lessthan 57200 records? is code run fine?

Re: Qvw error in QMC

Chip_Matejowsky — Mon, 02 May 2022 15:14:34 GMT

Hi @lucasx15,

Is this issue occurring in QlikView or Qlik Sense. If QlikView, we'll move your thread to the appropriate forum so that it is seen by the correct audience.

Can you post the full error(s) taken from the QVW task and document logs?

The difference in the data looks to be expected as you're comparing 64bit and 32bit processes. See the Qlik Help entry on Connect.

Connect32

This statement is used the same way as the CONNECT statement, but forces a 64-bit system to use a 32-bit ODBC/OLE DB provider. Not applicable for custom connect.

Connect64

This statement is used the same way as the as the CONNECT statement, but forces use of a 64-bit provider. Not applicable for custom connect.

Best Regards

Re: Qvw error in QMC

Anders_Eriksson — Mon, 02 May 2022 15:14:30 GMT

Does sound like you have some erroneous data in the Oracle database that prematurely terminates the SQL data transfer.
Both QVX_UNEXPECTED_END_OF_DATA and that you only get half the data when loading through ODBC points to this.
You need to somehow identify which row in the database is causing the problem.
It's the next one after the last one you receive correctly.
Something on that row causes the problem, you need to investigate all columns for that row and try to identify which one holds the problematic data.
Often it can be a character field of some type with strange data pasted into it.