Getting Started with Oracle Data Integrator 11g: A Hands-On Tutorial

Getting Started with Oracle Data Integrator 11g: A Hands-On Tutorial


View All Available Formats & Editions
Eligible for FREE SHIPPING
  • Want it by Wednesday, October 24?   Order by 12:00 PM Eastern and choose Expedited Shipping at checkout.

Product Details

ISBN-13: 9781849680684
Publisher: Packt Publishing
Publication date: 04/28/2012
Pages: 384
Product dimensions: 7.50(w) x 9.25(h) x 0.79(d)

Customer Reviews

Most Helpful Customer Reviews

See All Customer Reviews

Getting Started with Oracle Data Integrator 11g: A Hands-On Tutorial 4 out of 5 based on 0 ratings. 1 reviews.
Boudville More than 1 year ago
One thing you have to wrap your mind around is that key portions of the book are about metadata. Where you have source and target silos and a separate silo that holds the ODI (Oracle Database Integrator). The book explains how to use the ODI to generate transformations between the source and target. The power lies in the flexibility of the transformations that you can write via the ODI GUI. Considerable effort has been expended by Oracle in making a simple and yet flexible GUI for this ends. XML is quoted extensively as a good use case. Basically, the source silo contains data in XML format, that uses some given schema. But you need to map this into another schema in the target silo. Crucially, the fact that the input data is already structured according to some logic makes it much easier to write a programmatic transformation. ODI also has some ability to reverse engineer the extraction of data from a flat file. ODI comes with what Oracle calls wizards, that have knowledge of typical low level formatting structures in a flat file. Like whether the file has column or delimiter boundaries. Interestingly, though the book is primarily about ODI that uses 11g, there are numerous examples involving MySql. This is freeware that is owned by Oracle. Naturally Oracle would prefer you to pony up to their expensive 11g. So I was somewhat surprised to see those mentions of MySql. The authors are clearly acknowledging the market reality that many users will indeed have source silos stored in MySql. Taking this further, the text also says commendably that "MySql is equally suitable as a target or for use as a staging area". Very good. There are the occasional jarring phrases, like the oxymoronic "some ETL tools all have the ability". Do your best to ignore those if you can.