Skip to main content

Getting ODI Packages running time


Sometimes we need to find out times taken by certain packages for certain reasons.
For this we can make use of ODI repository table SNP_SESSION.
So for that we can use following query which you can run on your work repository schema.

 select  sess_name Package_Name,SESS_BEG Start_Time,SESS_END End_TIme, (SESS_DUR/60) Time_in_Minutes from SNP_SESSION
where 
(sess_name='PKG_A_VERSION_2' or
sess_name='PKG_B_VERSION_2' or
sess_name='PKG_C_VERSION_2' or
sess_name='PKG_D_VERSION2' or
sess_name='PKG_E_VERSION_2' or
sess_name='PKG_F' or
sess_name='PKG_G' or
sess_name='PKG_H')
and sess_beg > sysdate-1
order by SESS_BEG;

 Here we will get result in following format.
PACKAGE_NAME
START_TIME
END_TIME
TIME_IN_MINUTES
PKG_A_VERSION_2
13-06-13 23:44
13-06-13 23:54
9.783333333
PKG_B_VERSION_2
13-06-13 23:54
14-06-13 0:11
16.8
PKG_C_VERSION2
14-06-13 0:11
14-06-13 0:18
7.266666667
PKG_D_VERSION_2
14-06-13 0:18
14-06-13 0:33
14.31666667
PKG_E_VERSION_2
14-06-13 0:33
14-06-13 1:18
44.93333333
PKG_F
14-06-13 1:18
14-06-13 1:27
9.45
PKG_G
14-06-13 1:27
14-06-13 1:33
5.583333333

This can mainly be used in analysis of packages for performance purpose.



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

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...
Post a Comment
Read more