Skip to main content

Load MS Excel data in Oracle using ODI

Hello friends!
I have been working on ODI since time now and I feel the tool has a lot to offer to developers out there. Each day I learn something new that I like to share with everyone, hoping that someday it helps you in your work! :)
So here’s one more tutorial adding to my series of ODI tutorials. Through this post, you will learn how to transfer your Microsoft Excel spreadsheet data into a table in Oracle.
Pre-requisites: Microsoft Excel, Oracle 10g Express Edition with *SQLPlus, Oracle Data Integrator 11g.
First of all you need to create a new excel sheet! I have named my excel sheet as my_data.
my_data.xlsx
my_data.xlsx
Now, you need to add a new ODBC data source. Go to Control Panel–>Administrative Tools–> Data sources. Click on Add. Give any data source name and then select your workbook. Click on Ok.
Adding data source
Adding data source
Once this is done, you now need to create a table called Karan_Employeein your Oracle database. The data for the table will be populated using the MS Excel sheet.
create table Karan_Employee(Empid int primary key, EmpName varchar2(30), EmpCity varchar2(30));
Now, follow the below steps for handling the ODI part!
Step 1: Create logical and physical schema for Karan_Employee table.
Step 2: Create schema for MS Excel
Under Topology navigator, go to Physical Architecture, right clickMicrosoft Excel and select new data server. Enter the DSN name which is same as the name of the data source and click on test connection.
snap1
create data server for excel
create data server for excel
Create new physical and logical schema for the Excel file as well.
Step 3: Create new project and model folders
Once creation of schemas is done both for the table and the excel sheet, you can now create a new Project under Designer tab.
Right click your Project–>Import–>Import Knowledge modules and select following modules!
1. LKM: SQL to oracle
2. IKM: Oracle Incremental Update
3. CKM: Oracle
You also need to create a new Model folder that will contain the models for table and excel sheet respectively as follows:
snap3
creating models for table and excel
creating models for table and excel
You need to reverse engineer the Karan_Employee table as well as theexcel sheet.
snap5
reverse engineering of models
Step 4: Create new interface
Under your project, there exists a folder called First Folder. Expand that folder, right click Interface–>New Interface.
Inside the interface, select Mapping to map the source to target.
mapping operation
mapping operation
Switch to flow for selecting your IKM,LKM and CKM.
snap7
snap8
snap9
Interface design
Interface design
Now finally run the interface. Check the status of the operation underOperator tab. It should not show any errors. The data of your source excel sheet is now successfully inserted in the target table.
snap11
run interface and view table
run interface and view table
That completes this tutorial. Thanks! :)
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