<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic Re: Restart Job in Talend Studio</title>
    <link>https://community.qlik.com/t5/Talend-Studio/Restart-Job/m-p/2279983#M54976</link>
    <description>&lt;P&gt;Thank you!&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;With this, at what point would the automatic restart of the job in case of database failure?&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;The component that you called "Connection Failure" is a tDie?&lt;/P&gt;</description>
    <pubDate>Thu, 10 Jan 2019 16:01:14 GMT</pubDate>
    <dc:creator>Anonymous</dc:creator>
    <dc:date>2019-01-10T16:01:14Z</dc:date>
    <item>
      <title>Restart Job</title>
      <link>https://community.qlik.com/t5/Talend-Studio/Restart-Job/m-p/2279981#M54974</link>
      <description>&lt;P&gt;Hi!&lt;/P&gt; 
&lt;P&gt;&amp;nbsp;&lt;/P&gt; 
&lt;P&gt;I use an Oracle database engine, I would like to know how I can manage the exceptions due to the lack of availability of the database (restarts, connection, blocking of tables, among others), since the database has failed, the work (Talend) will stop automatically, but I want it to start again automatically when the database becomes available again.&lt;BR /&gt;How can I do this?&lt;/P&gt; 
&lt;P&gt;&amp;nbsp;&lt;/P&gt; 
&lt;P&gt;Thanks!&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Sat, 16 Nov 2024 06:52:54 GMT</pubDate>
      <guid>https://community.qlik.com/t5/Talend-Studio/Restart-Job/m-p/2279981#M54974</guid>
      <dc:creator>Anonymous</dc:creator>
      <dc:date>2024-11-16T06:52:54Z</dc:date>
    </item>
    <item>
      <title>Re: Restart Job</title>
      <link>https://community.qlik.com/t5/Talend-Studio/Restart-Job/m-p/2279982#M54975</link>
      <description>&lt;P&gt;Hi Fred,&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;While using DB Components, best way is to implement using &lt;STRONG&gt;prejob&lt;/STRONG&gt; and &lt;STRONG&gt;postjob&lt;/STRONG&gt;. we have used prejob for DB connections on either success or failure (ex. connection may fail because of invalid credentials or network issue) and postjob for commit and close connections. These DB connections we trigger through onComponentError/onComponentOK with the global variable message error. we capture it through tWarn or tDie components by adding the connection variables.&lt;/P&gt;&lt;P&gt;&lt;BR /&gt;&lt;STRONG&gt;Error Message (tDie):&lt;/STRONG&gt;&lt;/P&gt;&lt;P&gt;"Error in Oracle Connection"+((String)globalMap.get("tDBConnection_1_ERROR_MESSAGE"))&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt;Success Message (tWarn):&lt;/STRONG&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;"Connection is Successful"+((String)globalMap.get("tDBConnection_1_ERROR_MESSAGE"))&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;Use Commit and Rollback functionality for each subjob at the output component, which helps to save the transaction only if it completes.&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Additionally,&amp;nbsp;&lt;/P&gt;&lt;P&gt;we have used Error Recovery Check point for each subjob, while helps to recover the last failed job and it will continue the process&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Adding the screenshot for your reference.&lt;/P&gt;&lt;BR /&gt;&lt;A href="https://community.qlik.com/legacyfs/online/tlnd_dw_files/0683p000009Lubh"&gt;DB_BestPractice.JPG&lt;/A&gt;</description>
      <pubDate>Thu, 10 Jan 2019 14:33:35 GMT</pubDate>
      <guid>https://community.qlik.com/t5/Talend-Studio/Restart-Job/m-p/2279982#M54975</guid>
      <dc:creator>avinashbasetty</dc:creator>
      <dc:date>2019-01-10T14:33:35Z</dc:date>
    </item>
    <item>
      <title>Re: Restart Job</title>
      <link>https://community.qlik.com/t5/Talend-Studio/Restart-Job/m-p/2279983#M54976</link>
      <description>&lt;P&gt;Thank you!&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;With this, at what point would the automatic restart of the job in case of database failure?&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;The component that you called "Connection Failure" is a tDie?&lt;/P&gt;</description>
      <pubDate>Thu, 10 Jan 2019 16:01:14 GMT</pubDate>
      <guid>https://community.qlik.com/t5/Talend-Studio/Restart-Job/m-p/2279983#M54976</guid>
      <dc:creator>Anonymous</dc:creator>
      <dc:date>2019-01-10T16:01:14Z</dc:date>
    </item>
    <item>
      <title>Re: Restart Job</title>
      <link>https://community.qlik.com/t5/Talend-Studio/Restart-Job/m-p/2279984#M54977</link>
      <description>&lt;P&gt;yes, the main intention of using tDie is to exit the JVM Immediately. see the advanced settings in a tDie component.&lt;/P&gt;</description>
      <pubDate>Tue, 05 Feb 2019 06:00:50 GMT</pubDate>
      <guid>https://community.qlik.com/t5/Talend-Studio/Restart-Job/m-p/2279984#M54977</guid>
      <dc:creator>avinashbasetty</dc:creator>
      <dc:date>2019-02-05T06:00:50Z</dc:date>
    </item>
  </channel>
</rss>

