Skip to main content

Oracle Data Integrator Tools:OdiSqlUnload, OdiFileCopy ,OdiZip

Hi friends!
Oracle Data Integrator includes a number of tools that have their own specific function. The OdiSqlUnload tool is mainly used for unloading as well as generating a data file based on the SQL query provided for a specific data server connection. The file is written to the path defined by parameter -FILE.
Through this post, I will explain how to configure and use the OdiSqlUnload tool inside a Procedure.
Pre-requisites: Oracle Data Integrator 11g (build version 11.1.1.7.0)
Step 1: Create a new Procedure
Create a new procedure inside any of your existing Projects namedtest_sqlunload. Click on Details and then add a new entry as follows!
Select Target Technology as ODI Tools. The -PASS field contains the encoded password for your schema. You can encode the password using the encode tool present in the [ODI_HOME]\oracledi\agent\bin folder.
Usage: encode your-schema-password
procedure_1
create procedure
Command
OdiSqlUnload "-FILE=D:\programs\sample2.csv" "-DRIVER=oracle.jdbc.OracleDriver" "-URL=jdbc:oracle:thin:@localhost:1521:orcl" "-USER=system" "-PASS=aIya5uUlQXGMLmIzPj.f" "-FIELD_SEP=;" "-DATE_FORMAT=dd/MM/yyyy hh:mm:ss" "-QUERY=select empid, empname, city from system.karan_employee"
Step 2: Run the Procedure
Once you run the procedure, navigate to the file path that you have mentioned as a part of your command. You should see a .csv file containing the results of the query.
Output
Output
output_1
---------------------------------------------------------------------------------------------------
I will talk about yet another simple and user friendly ODI tool calledOdiFileCopy.
The OdiFileCopy tool copies files or a folder into files or a folder on the machine of the execution agent. One can also overwrite and detect case sensitive files while copying.
Usage of OdiFileCopy tool
OdiFileCopy -DIR=<dir> -TODIR=<dest_dir> [-OVERWRITE=<yes|no>] [-RECURSE=<yes|no>] [-CASESENS=<yes|no>]
OdiFileCopy -FILE=<file> -TOFILE=<dest_file>|-TODIR=<dest_dir> [-OVERWRITE=<yes|no>] [-RECURSE=<yes|no>] [-CASESENS=<yes|no>]
Pre-requisites: Oracle Data Integrator 11g (build version 11.1.1.7.0)
Through this post, I will copy a text file from one location to another. Create a new text file named transfer1.txt and add the following content!
D:\programs\transfer1.txt
"I have been transferred using OdiFileCopy tool"
Now,using OdiFileCopy tool I will copy this text file to location D:\odi_workand name the file as transferred.txt.
Now, let’s put this tool to practice with a short demo. Open ODI Studio. Create a new package named odifilecopy_demo and drag the OdiFileCopytool in the vacant area. Connect it to the OdiBeep tool using an arrow.
create new package
package_1
Command
OdiFileCopy "-FILE=D:\programs\transfer1.txt" "-TOFILE=D:\odi_work\transferred.txt" "-RECURSE=YES" "-OVERWRITE=YES" "-CASESENS=NO"
Note: In order to transfer multiple files of same type (for example: .csv), you can use the following command.
Copy all *.csv files from source directory to target and overwrite.
OdiFileCopy -FILE=D:\your_source_directory\*.csv -TODIR=D:\your_target_directory -OVERWRITE=yes
Run the package. Check the status of the operation under the Operatortab. If the operation was successful, you will hear a sound due to theOdiBeep tool and your file will be copied to the specified location!
Output
--------------------------------------------------------------------------------------------
As the name suggests, the OdiZip tool is used to create ZIP files from a directory or several files.
Usage of OdiZip
OdiZip -DIR=<dir> -FILE=<file> -TOFILE=<dest_file> [-OVERWRITE=<yes|no>] [-RECURSE=<yes|no>] [-CASESENS=<yes|no>] [-ENCODING=<file_name_encoding>]
OdiZip is useful when you have files of smaller size because the zipping operation is done by an Agent and the traffic between the agent and the target directory can cause a lot of problems.
Pre-requisites: Oracle Data Integrator 11g (build version 11.1.1.7.0)
Now, let’s put this tool into practice using ODI. Open ODI Studio and create a new Package named odizip_demo in any of your existingProjects.
Drag the OdiZip tool in the vacant area. Connect it to the OdiBeep tool using an arrow.
create package
package_1
Command
OdiZip "-DIR=D:\odi_work" "-FILE=*.*" "-TOFILE=D:\odi_work\odi_work.zip" "-OVERWRITE=YES" "-RECURSE=YES" "-CASESENS=NO"
Finally, run the package. Check the status of the operation under theOperator tab. If the operation was successful, you should see your zip file in the target directory!
Output
-----------------------------------------------------------


Comments

  1. Oracle Data Integrator Online Training, ONLINE TRAINING – IT SUPPORT – CORPORATE TRAINING http://www.21cssindia.com/courses/oracle-data-integrator-online-training-125.html The 21st Century Software Solutions of India offers one of the Largest conglomerations of Software Training, IT Support, Corporate Training institute in India - +919000444287 - +917386622889 - Visakhapatnam,Hyderabad Oracle Data Integrator Online Training, Oracle Data Integrator Training, Oracle Data Integrator, Oracle Data Integrator Online Training| Oracle Data Integrator Training| Oracle Data Integrator| "Courses at 21st Century Software Solutions
    Talend Online Training -Hyperion Online Training - IBM Unica Online Training - Siteminder Online Training - SharePoint Online Training - Informatica Online Training - SalesForce Online Training - Many more… | Call Us +917386622889 - +919000444287 - contact@21cssindia.com
    Visit: http://www.21cssindia.com/courses.html"

    ReplyDelete

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

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