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: 
Anonymous
Not applicable

[resolved] tOracleInput to tOracleOutput very slow

Hi folks,
I'm suffering from the problem that a simple copy from one table to another is very slow. The tables are on different schemas but on the same database. The Oracle Input is a select-query with a simple WHERE clause.
I'm connected to the database server via VPN. Maybe this is the limiting factor? But still the operation should be faster than ~5 rows per second....
See attached Screenshot.
0683p000009MDbb.png
Labels (2)
1 Solution

Accepted Solutions
Anonymous
Not applicable
Author

assuming your database is healthy this is probably a limitation of the network throughput between the database and where talend is running. Some options are to avoid transferring data across the network are:
* tOracleRow - if you can write your process as a single sql statement ( insert into ... select from )
* tOracleSP - put your process in a stored procedure and call it
* use ELT components - tELTOracleInput, tELTOracleMap, tELTOracleMap
there is a bit of a learning curve with the ELT components as they work quite differently than other components. This is because they primarily for generating SQL.

View solution in original post

3 Replies
Anonymous
Not applicable
Author

assuming your database is healthy this is probably a limitation of the network throughput between the database and where talend is running. Some options are to avoid transferring data across the network are:
* tOracleRow - if you can write your process as a single sql statement ( insert into ... select from )
* tOracleSP - put your process in a stored procedure and call it
* use ELT components - tELTOracleInput, tELTOracleMap, tELTOracleMap
there is a bit of a learning curve with the ELT components as they work quite differently than other components. This is because they primarily for generating SQL.
Anonymous
Not applicable
Author

assuming your database is healthy this is probably a limitation of the network throughput between the database and where talend is running. Some options are to avoid transferring data across the network are:
* tOracleRow - if you can write your process as a single sql statement ( insert into ... select from )
* tOracleSP - put your process in a stored procedure and call it
* use ELT components - tELTOracleInput, tELTOracleMap, tELTOracleMap
there is a bit of a learning curve with the ELT components as they work quite differently than other components. This is because they primarily for generating SQL.

Mike, you are right, I run the job at a machine which is on the same subnet as the database and the throughput was much better.
I already tried ELT but gave up to quick maybe ^^ Will take a look at it again, thanks anyway!
willm1
Creator
Creator

In addition to that, check your jvm settings for your Studio - they may be low.... https://help.talend.com/search/all?query=Allocating+more+memory+to+the+Talend+Studio&content-lang=en