TechWare

When you run an ODI ETL Load plan, it takes certain time. At times, customers would like to understand a split of the time taken by the load plan and analyze the top running maps to see if they can be optimized to run faster. In the first part in this series, we help you understand how you can easily analyze the time taken by the load plan and  identify the top running maps . Using ODI Studio, a customer can load at the Load Plan logs and see the time taken by each phase or if required, each step in the load plan. However since there is no easy option to sort by the time taken, it can sometimes be painful to look at the complete logs from ODI Studio to easily identify the top running maps. The following backend queries(to be run against the ODI repository schema) can help you see the same details that you see in ODI studio and yet analyze them better. Query to get the overall load plan run timings for an instance --List of Load Plan runs for a load plan instance i...

DROP USER SDEV CASCADE; DROP USER STEST CASCADE; DROP USER SPROD CASCADE; DROP USER TDEV CASCADE; DROP USER TTEST CASCADE; DROP USER TPROD CASCADE; CREATE USER SDEV IDENTIFIED by welcome; CREATE USER STEST IDENTIFIED BY welcome; CREATE USER SPROD IDENTIFIED BY welcome; GRANT ALL PRIVILEGES TO SDEV,STEST,SPROD; CREATE USER TDEV IDENTIFIED by welcome; CREATE USER TTEST IDENTIFIED BY welcome; CREATE USER TPROD IDENTIFIED BY welcome; GRANT ALL PRIVILEGES TO TDEV,TTEST,TPROD; CREATE TABLE SDEV.BONUS         (ENAME VARCHAR2(10),          JOB   VARCHAR2(9),          SAL   NUMBER,          COMM  NUMBER); CREATE TABLE SDEV.EMP        (EMPNO NUMBER(4) NOT NULL,         ENAME VARCHAR2(10),         J...