Skip to main content

Load data from one Excel sheet to another in Oracle Data Integrator

Hello friends!
While trying to load data from an Excel sheet to a table in Oracle, many a times ODI developers come across the “Invalid fetch size” or the“ResultSet is closed” errors upon execution of their Interface. This issue has been discussed in many questions on the Oracle Forums website. Good news is that this bug has now been resolved.
In order to resolve these errors, a common solution is as follows!
1. Try using ODI 11g (version 11.1.1.3) or below
2. In case you are using a higher version of ODI say 11.1.1.5, you need apply a Patch 13528165 on top of 11.1.1.5 as mentioned by Rickson Lewis over here
In this tutorial I will explain how data from one Excel spreadsheet is loaded into another using Oracle Data Integrator!
Pre-requisites: ODI 11.1.1.3, MS Excel 2007 software
I will be using two Excel sheets namely source.xlsx and target.xlsxrespectively. The source Excel sheet is populated as follows!
source_excel
Step 1: Create data server, physical & logical schemas for both Excel sheets
Step 2: Create data models and reverse engineer
model_creation
Step 3: Create a new Interface
Create a new Interface in any of existing projects named excel_to_excelas follows!
interface_1
interface_2
interface_3
interface_4
Finally, run the Interface. Check the status of the operation under theOperator tab. You should see the target Excel sheet now populated! :)

target_excel
output

Comments

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

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