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

Announcements
Join us in Bucharest on Sept 18th for Qlik's AI Reality Tour! Register Now
cancel
Showing results for 
Search instead for 
Did you mean: 
Tool_Tip
Creator III
Creator III

Oracle issue

Dear all 

 

LOAD*;
SQL SELECT YEAR
FROM TABLE ( SC1.pkg1.get_period@dblink1(2) );

 

We have already created and tested dblink between two database. select * from table1@@dblink1 is working fine. we are getting below error while running package  with single argument as number passed from dblink.

Tool_Tip_0-1734414717352.png

 

Labels (1)
6 Replies
sbaro_bd
Creator III
Creator III

Hi @Tool_Tip ,

I think the format doesn't work with Qlik. Try the classic synthax like this  : 

<server>.<database>.<schema>.<table>

For example : DatabaseServer1.db1.dbo.table1

Regards.

henrikalmen
Specialist II
Specialist II

Insert a blank space between "LOAD" and "*" like this: LOAD *;

Tool_Tip
Creator III
Creator III
Author

Not working

henrikalmen
Specialist II
Specialist II

Try removing "Load *;" completely, it's not necessary. But add a table name for the resulting table, like this:

[loadedTable:]
SQL SELECT YEAR
FROM TABLE ( SC1.pkg1.get_period@dblink1(2) );

If it still doesn't work, try the sql statement in a sql client (not inside qlik) directly against the database. If the query works there, maybe Qlik has a problem with the (kind of strange) table name you are trying to select from. I don't recall exactly how the sql syntax is in oracle, but maybe you could add something like ` ... ` around the table name?

vuan
Partner - Contributor II
Partner - Contributor II

Hi,

just try to create a new DB Connection to the instance from the dblink in Qlik Sense instead of using a dblink over Qlik Sense.

KR

marcus_sommer

It's not a Qlik issue because Qlik doesn't execute any sql else transferred only the statement per driver to the data-base and get the return on the same way back.

Assuming that your data-bases are appropriate configured to support dblink it's likely that the driver doesn't - in general or missing some configurations or needing a specific syntax. I think looking on the help-sites/communities from the data-base/driver should give valuable hints.