Comments on: Oracle Data Integrator Article on OTN http://www.rittmanmead.com/2007/05/25/oracle-data-integrator-article-on-otn/ Delivered Intelligence Fri, 30 Jul 2010 17:54:00 -0400 http://wordpress.org/?v=2.8.4 hourly 1 By: Mark Rittman http://www.rittmanmead.com/2007/05/25/oracle-data-integrator-article-on-otn/comment-page-1/#comment-2809 Mark Rittman Tue, 12 Jun 2007 20:25:21 +0000 http://www.rittmanmead.com/wp2/2007/05/25/oracle-data-integrator-article-on-otn/#comment-2809 Hi Mark, good to hear from you. The reason I'd still advocate OWB as the main Oracle DW tool, with ODI being used to provide heterogenous connectivity, CDC, SOA integration and so on, is that ODI doesn't come with any of the OLAP and DW data modeling features that OWB has. You can't define dimensions, cubes and so on in ODI, you can't interface directly with Discoverer, and so on, which is why OWB is still an essential tool. As you say though, the requirement to have two sets of skills, two repositories and so on is a not insignificant overhead, hence I'll be pleased when the two tools become increasingly merged and/or integrated over the next couple of years. regards Mark Hi Mark, good to hear from you. The reason I’d still advocate OWB as the main Oracle DW tool, with ODI being used to provide heterogenous connectivity, CDC, SOA integration and so on, is that ODI doesn’t come with any of the OLAP and DW data modeling features that OWB has. You can’t define dimensions, cubes and so on in ODI, you can’t interface directly with Discoverer, and so on, which is why OWB is still an essential tool.

As you say though, the requirement to have two sets of skills, two repositories and so on is a not insignificant overhead, hence I’ll be pleased when the two tools become increasingly merged and/or integrated over the next couple of years.

regards

Mark

]]> By: Mark Clewett http://www.rittmanmead.com/2007/05/25/oracle-data-integrator-article-on-otn/comment-page-1/#comment-2810 Mark Clewett Fri, 08 Jun 2007 08:33:50 +0000 http://www.rittmanmead.com/wp2/2007/05/25/oracle-data-integrator-article-on-otn/#comment-2810 In the ODI article you recommend using ODI for gathering information from disparate data sources to the staging area of your Oracle data warehouse, then using OWB to populate the ODS and analytic layers inside the warehouse. SInce this would mean having to maintain two skill sets for ETL development, what advantages does this approach have over just using ODI throughout? In the ODI article you recommend using ODI for gathering information from disparate data sources to the staging area of your Oracle data warehouse, then using OWB to populate the ODS and analytic layers inside the warehouse. SInce this would mean having to maintain two skill sets for ETL development, what advantages does this approach have over just using ODI throughout?

]]>