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

Announcements
See why IDC MarketScape names Qlik a 2025 Leader! Read more
cancel
Showing results for 
Search instead for 
Did you mean: 
Anonymous
Not applicable

Continue job execution after a connection fail

Hi all,
I have to build a job with the following scenario:
Connect in 15 different MYSQL databases, with different IP's, after connect on each one, it will retrive some informations from MySQL and store in a table inside an oracle database. The problem is sometimes the origin (mysql database) can be offline and if this situation happens I need that the kob continues the execution with te other databases but I don't know how to do that. If the connection is successfull retrieve data from mysql and store in oracle table but if the connection failled, go to the next myql database and continue the job. And i have to add this exception for every mysql connection attempt. How can I do that? Using a run if? But I don't know how to implement that in the job. A picture of the job is attached.

 

Ps: Im using talend open studio (free version).

 

please, can someone help me with this? Thanks in advance.

Labels (4)
1 Solution

Accepted Solutions
Jesperrekuh
Specialist
Specialist

first of all take a closer look on the documentation and :
1 - OnComponentError and Ok

2 - OnSubJobError and Ok

 

Next use tMySQL<input> right mouse: based on 1 or 2 (mentioned above) you could start a different branch in your current job flow. look at the pictures.
And finally what @fdenis suggest also use a tlogCatcher (only need it once), this one you use to process and check wether you need re-run your job.

 

0683p000009LzTZ.png

 

View solution in original post

3 Replies
fdenis
Master
Master

your solution is tLogCatcher.
reply if you need more help.
Jesperrekuh
Specialist
Specialist

first of all take a closer look on the documentation and :
1 - OnComponentError and Ok

2 - OnSubJobError and Ok

 

Next use tMySQL<input> right mouse: based on 1 or 2 (mentioned above) you could start a different branch in your current job flow. look at the pictures.
And finally what @fdenis suggest also use a tlogCatcher (only need it once), this one you use to process and check wether you need re-run your job.

 

0683p000009LzTZ.png

 

Anonymous
Not applicable
Author

Hi Dijke,

 

Thank you so much for your help.

With your explanation I was able to configure the job and it was executed correctly.

 

Thanls a lot!