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.

Comments

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...

Oracle Data Integrator Tools:OdiSqlUnload, OdiFileCopy ,OdiZip

Hi friends! Oracle Data Integrator includes a number of tools that have their own specific function. The OdiSqlUnload tool is mainly used for unloading as well as generating a data file based on the SQL query provided for a specific data server connection. The file is written to the path defined by parameter -FILE . Through this post, I will explain how to configure and use the OdiSqlUnload tool inside a Procedure . Pre-requisites : Oracle Data Integrator 11g (build version 11.1.1.7.0) Step 1 : Create a new Procedure Create a new procedure inside any of your existing Projects named test_sqlunload . Click on Details and then add a new entry as follows! Select Target Technology as ODI Tools . The -PASS field contains the encoded password for your schema. You can encode the password using the encode tool present in the [ODI_HOME]\oracledi\agent\bin folder. Usage : encode yo...

Oracle Data Integrator tools: OdiFileDelete and OdiOutFile

Hello everyone! It’s time for another cool ODI tutorial. Last time, I spoke about the OdiZip tool and how it can be used to create zip files from a directory. Through this post, I will talk about two more tools related to Files namely OdiFileDelete and OdiOutFile . 1. OdiFileDelete The OdiFileDelete is a tool used to delete files present in a directory or a complete directory on the machine running the agent. Usage OdiFileDelete -DIR=<dir> | -FILE=<file> [-RECURSE=<yes|no>] [-CASESENS=<yes|no>] [-NOFILE_ERROR=<yes|no>] [-FROMDATE=<fromdate>] [-TODATE=<todate>] If -FROMDATE is omitted, all files with a modification date earlier than the -TODATE date will be deleted. If -TODATE is omitted, all files with a modification date later than the -FROMDATE date will be deleted. If both parameters are omitted, all files matching the -FILE...

TechWare

Search This Blog