Load data from flat file to Oracle table using ODI

Hello everyone!

My today’s tutorial will focus on migrating data from a flat file to an Oracle table. I would be creating a simple text file (.txt). Using Oracle Data Integrator, I will load the source file data into my target table in Oracle.

Pre-requisites: Oracle 10g Express Edition with *SQL Plus, Oracle Data Integrator 11g (Build Version 11.1.1.7.0)

Create a flat file named file_data.txt that contains the following:

Id Name
1 Karan
2 Mahesh
3 Prasad
4 Hanif

Create a table named KARAN_FILE in the Oracle database.

create table KARAN_FILE(custid int primary key, custname varchar2(30));

Open ODI Studio. Connect to your work repository and follow below steps!

Step 1: Create data server and physical schema for table

Step 2: Create logical schema for table

create logical schema for table

Note: Make sure you test your connection by clicking on the Test Connection button while creating your data server!

Step 3: Create data server and physical schema for flat file

create data server and physical schema for file

Step 4: Create logical schema for flat file

create logical schema for file

Note: Make sure you test your connection by clicking on the Test Connection button while creating your data server!

Step 5: Create new model folders to contain table and file data models respectively

Under the Designer tab, go to Models and create a new model folder named customer_data. Add a new model with same name to that folder by reverse engineering your target table.

create data model for table

Similarly, create a new model for file named file_data under folder namedfile_model as follows:

create data model for file

Right click the created Model –> New Datastore. Add details to the data store.

Reverse engineer the file and add the appropriate column names and data types.

Step 6: Create a new interface named file_to_table

Perform Mapping between source i.e flat file and target i.e oracle table. Select LKM as File to SQL and IKM as Oracle Incremental Update underFlow.

create new interface

Make sure no errors are present. Now, run the interface and check the status of the operation under the Operator tab.

If the operation is successful the data from your file is now successfully inserted in the target table!

Output

That completes this tutorial. Keep visiting for more tutorials on ODI

Comments

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

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 in Oracle. You can use any existing ta

Running Count in Talend Open Studio

Most Talend components keep a count of the records processed using variables like NB_LINE or NB_LINE_OK. But these are only available after all processing is completed. Define your own counter variable to keep a running count for use in a tMap. Variables like tFilterRow.NB_LINE or tAccessOutput.NB_LINE_INSERTED can be used to report the number of affected lines after a subjob's processing. However, it may be of use to get the current line index for use in a tMap. The index variables used to form NB_LINE aren't available during processing; they're only written out the globalMap at the end of processing. In this example, staging records are loaded from Excel to Access. The order in which the Excel records are read is preserved in a database column called DISPLAY_SEQ_NB. Note that there is an auto-increment column used for record ID in the Access table. This could be used to infer a loading order, but this job uses a separate column to keep the ID as a meaningless surr

TechWare

Search This Blog