Do not input private or sensitive data. View Qlik Privacy & Cookie Policy.
Skip to main content

Announcements
Qlik Open Lakehouse is Now Generally Available! Discover the key highlights and partner resources here.
cancel
Showing results for 
Search instead for 
Did you mean: 
Not applicable

Loading from DB error

Hi everybody.

I'm facing a strange behaviour in loading tables from an Oracle DB via OLE DB driver.

I run the same script for different tables of the same DB but I get two different results.

First run:

OLEDB CONNECT TO [Provider=MSDAORA.1;User ID=QLICKVIEW;Data Source=3VM] (XPassword is cHOMRYRNJbYWWPJGQJMEDSYU);

SQL

SELECT *

FROM CLARIV.INV_INVESTMENTS;

It gives back

"ErrorSource: (null), ErrorMsg: Unspecified error

SQL

SELECT *

FROM CLARIV.INV_INVESTMENTS"

Second run:

OLEDB CONNECT TO [Provider=MSDAORA.1;User ID=QLICKVIEW;Data Source=3VM] (XPassword is cHOMRYRNJbYWWPJGQJMEDSYU);

SQL

SELECT *

FROM CLARIV.ODF_CA_PROJECT;

It gives back

ODF_CA_PROJECT 550 lines fetched

The only difference is the table that I use but I tried the first script directly via SQL Developer and it works perfectly.

Do you have any hint for that?

Thanks a lot

Manlio

4 Replies
fernandotoledo
Partner - Specialist
Partner - Specialist

Have you tried to use INV_INVESTMENTS instead CLARIV.INV_INVESTMENTS

It seems that your user doesn't have access to this table/view.

Not applicable
Author

Withour CLARIV, the table owner, the query doesn't work.

Anyway, I use it in any table and only 3 of them give this error.

Not applicable
Author

Even I am facing the same problem. Were you able to find a solution?

I get the following error while trying to load the data from a table:

ErrorSource: Microsoft OLE DB Provider for Oracle, ErrorMsg: Unspecified error

SQL SELECT *

FROM COLBI."PRODUCTS_DIM"

Not applicable
Author

I have had the same problem..

A colleague noticed that it worked with only selecting ONE column so i kept adding columns until i got he error.

It turns out for me the "Unspecified error" was that qlikview did not like a Qracle date column format. So i converted this to_char in the SQL and it resolved the issue.