Skip to main content

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 Modelseach 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 in Oracle. You can use any existing table as well for this tutorial. Insert some dummy data in the table as well.
create table Sales(saleid int primary key, saleperson varchar(30), quantity int);
Sample data inside the table:
final_output
Open ODI Studio and perform the following steps!
Step 1: Create new data server, logical and physical schemas for your table. Skip to step 2 if already created.
Step 2: Create Model folder and reverse engineer your table. Skip to step 3 if already created.
Step 3: Create new interface
Make a new interface called test_yellow_interface. Make sure you select the correct logical schema. IKM used in this case is Oracle Incremental Update.
interface_1
interface_2
Under options set Flow Control to false and Create_Targ_Table to true.
create yellow interface
create yellow interface
Run the interface. If no errors occur, your yellow interface will work! Now, you can use this temporary interface instead of importing the Sales modelover and over again.
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

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