Skip to main content

Synchronous and Asynchronous execution in ODI

In data warehouse designing, an important step is to deciding which step is before/after. Newly added packages and required DW data must be analyzed carefully. Synchronous addings can lengthen ETL duration.


Interfaces, procedures without generated scenario cannot be executed in parallel. Only scenario executions can be parallel in ODI. Default scenario execution is synch in ODI. If you want to set a scenario to executed in parallel then you will write “-SYNC_MODE=2″ on command tab or select Synchronous / Asynchronous option Asynchronous in General tab.


I have created a package as interfaces executes as;
  • INT_JOBS parallel 
  • INT_REGIONS synch 
  • INT_REGIONS synch 
  • INT_COUNTRIES synch 
  • INT_LOCATIONS parallel 
  • INT_EMPLOYEES parallel
(Interfaces are independent.)


Selecting beginning and ending times and durations from repository tables as ODI 11g operator is not calculating these values. It is obvious in ODI 10g operator.

SELECT   sess_no || '-' || sess_name sess_no_sess_name,
         CASE
            WHEN synchro = 1
               THEN 'SYNCH'
            ELSE 'ASYNCH'
         END "SYNCH/ASYNCH", sess_beg, sess_end,
         ROUND ((sess_end - sess_beg) * 24 * 60 * 60, 2) DURATION
    FROM snpw1.snp_session
   WHERE sess_beg >= TO_DATE ('20110630', 'yyyymmdd') AND sess_no > 214001
ORDER BY sess_beg, sess_no, sess_end;
Sess_no 215001, 216001, 217001 scenarios are executed as first group, after this group is finished scenarios sess_no 218001, 219001 is executing.
  • Sess_no 215001, 216001, 217001 duration: 58 secs 
  • Sess_no 218001, 219001 duration: 48 secs
Package duration is 106 secs. As you can see from repository tables like this.

SELECT   parent_sess_no, MIN (sess_beg), MAX (sess_end),
         ROUND ((MAX (sess_end) - MIN (sess_beg)) * 24 * 60 * 60, 2) sess_dur
    FROM snpw1.snp_session
   WHERE sess_beg >= TO_DATE ('20110630', 'yyyymmdd')
     AND parent_sess_no = 214001
GROUP BY parent_sess_no


PARENT_SESS_NO       MIN(SESS_BEG)            MAX(SESS_END)        SESS_DUR
214001             30.06.2011 22:39:50       30.06.2011 22:41:36       106

INT_JOBS (parallel) is executing parallel with follow-up scenarios. Package duration is due to INT_jobs is the longest.

In this case, when first scenario execution is finished, package execution status will show you done. But other scenarios is still executing, so you can add ODI WAIT FOR CHILD SESSION (OWFCS) in the end of package to see status is done when all scenarios are finished executing. Add OdiWaitForChildSession with “-POLL_INT=1″ “-MAX_CHILD_ERROR=1″ options. Also if one of scenarios will be fail, you will get package error with this case.

After OWFCS, you can see first group execution is done, then, second group is executing.

SELECT   sess_no || '-' || sess_name sess_no_sess_name,
         CASE
            WHEN synchro = 1
               THEN 'SYNCH'
            ELSE 'ASYNCH'
         END "SYNCH/ASYNCH", sess_beg, sess_end,
         ROUND ((sess_end - sess_beg) * 24 * 60 * 60, 2) DURATION
    FROM snpw1.snp_session
   WHERE sess_beg >= TO_DATE ('20110630', 'yyyymmdd') AND sess_no > 214001
ORDER BY sess_beg, sess_no, sess_end



SELECT   parent_sess_no, MIN (sess_beg), MAX (sess_end),
         ROUND ((MAX (sess_end) - MIN (sess_beg)) * 24 * 60 * 60, 2) sess_dur
    FROM snpw1.snp_session
   WHERE sess_beg >= TO_DATE ('20110630', 'yyyymmdd')
     AND parent_sess_no = 264001
GROUP BY parent_sess_no

PARENT_SESS_NO MIN(SESS_BEG) MAX(SESS_END) SESS_DUR
264001 04.07.2011 23:10:27 04.07.2011 23:13:41 194
Labels:

Comments

Post a Comment

Popular posts from this blog

ODI KM Adding Order by Option

You can add Order by statement to queries by editing KM.I have edited IKM SQL Control Append to provide Order by.  1) Add an option to KM named USE_ORDER_BY, its type is Checkbox and default value is False. This option determines you want an order by statement at your query. 2)Add second option to KM named ORDER_BY, type is Text. You will get order by values to your query by this option. 3) Editing Insert New Rows detail of KM. Adding below three line code after having clause. That's it! <% if (odiRef.getOption("USE_ORDER_ BY").equals("1")) { %> ORDER BY <%=odiRef.getOption("ORDER_BY" )%> <%} %>  If USE_ORDER_BY option is not used, empty value of ORDER_BY option get error. And executions of KM appears as such below; At this execution, I checked the KM to not get errors if ORDER_BY option value is null. There is no prove of ORDER BY I'm glad.  Second execution to get  Ord...
132 comments
Read more

Creating Yellow Interface in ODI

Hello everyone! In Oracle data integrator (ODI), an  interface  is an object which populates one datastore, called the  target , with data coming from one or more other datastores, known as  sources . The fields of the source datastore are linked to those in the target datastore using the concept of  Mapping . Temporary interfaces used in ODI are popularly known as  Yellow Interfaces . It is because ODI generates a yellow icon at the time of creation of a yellow interface as opposed to the blue icon of a regular interface. The advantage of using a yellow interface is to avoid the creation of  Models each time you need to use it in an interface. Since they are temporary, they are not a part of the data model and hence don’t need to be in the Model. So let’s begin and start creating our yellow interface! Pre-requisites : Oracle 10g Express Edition with *SQL Plus, Oracle Data Integrator 11g. Open *SQL Plus and create a new table  Sales ...
Post a Comment
Read more