Moving Objects Between Projects in ODI

4
About White Papers Contact Posted by Uli Bethke on Sep 18, 2012 in Oracle Data Integrator (ODI) One of the really annoying things about ODI is that it is not easily possible to move or copy objects between projects. Below is a step by step guide you can follow to copy or move objects between projects. We will take the object of type package as an example as this is the most complicated and covers off any of the others as well. The method shown uses Duplication mode import. While this method is not recommended by Oracle support. I never had any issues with it. So let’s get started: 1. Migrate any of the variables used inside the package using Export and Import (Duplication Mode). A variable with the same name may already exist in the target project. This means you have to rename the variable and fix any references to it in interfaces, procedures, packages, and the Topology (the details on this follow below). 2. Migrate any of the project functions and project Knowledge Modules used using Export and Import (Duplication Mode) For the KMs consider using global KMs instead 3. Export the root folder (with child components) of where the package is located. The reason for this is how Duplication mode import in ODI works. Basically it does not recreate internal IDs for objects that are part of the export XML. This strategy is used to minimise the number of missing references and as a result the amount of work we need to do. 4. Next we import the exported folder into our new project. Note the import needs to be made in Duplication Mode. 5. Next we move (drag and drop) the object(s) we need from our imported folder to our target folder in the new project. 6. Next we can delete the imported folder 7. Any missing references to Knowledge Modules need to be recreated for all of the interfaces used in the Copying and moving objects between projects in ODI | BI-Quotient http://www.business-intelligence-quotient.com/?p=1549 1 of 4 7/19/2013 10:35 AM

description

Moving Objects Between Projects in ODI

Transcript of Moving Objects Between Projects in ODI

Page 1: Moving Objects Between Projects in ODI

AboutWhite PapersContact

Posted by Uli Bethke on Sep 18, 2012 in Oracle Data Integrator (ODI)

One of the really annoying things about ODI is that it is not easily possible to move or copy objects betweenprojects. Below is a step by step guide you can follow to copy or move objects between projects. We will takethe object of type package as an example as this is the most complicated and covers off any of the others aswell. The method shown uses Duplication mode import. While this method is not recommended by Oraclesupport. I never had any issues with it.

So let’s get started:

1. Migrate any of the variables used inside the package using Export and Import (Duplication Mode). Avariable with the same name may already exist in the target project. This means you have to rename thevariable and fix any references to it in interfaces, procedures, packages, and the Topology (the details on thisfollow below).

2. Migrate any of the project functions and project Knowledge Modules used using Export and Import(Duplication Mode)

For the KMs consider using global KMs instead

3. Export the root folder (with child components) of where the package is located. The reason for this is howDuplication mode import in ODI works. Basically it does not recreate internal IDs for objects that are part ofthe export XML. This strategy is used to minimise the number of missing references and as a result theamount of work we need to do.

4. Next we import the exported folder into our new project.

Note the import needs to be made in Duplication Mode.

5. Next we move (drag and drop) the object(s) we need from our imported folder to our target folder in thenew project.

6. Next we can delete the imported folder

7. Any missing references to Knowledge Modules need to be recreated for all of the interfaces used in the

Copying and moving objects between projects in ODI | BI-Quotient http://www.business-intelligence-quotient.com/?p=1549

1 of 4 7/19/2013 10:35 AM

Page 2: Moving Objects Between Projects in ODI

package

Note: This also applies to all of the options for each KM.

If variables are referenced using the old project code in any of the KMs or you had to rename a variableduring import then these need to be updated as well

8. Update references to any variables or project functions used in procedures

If variables are referenced using the old project code in any of the Procedures or you had to rename a variableduring import then these need to be updated as well

9. Update references to any variables or project functions used in other variables

If variables are referenced using the old project code in any of the Variables or you had to rename a variableduring import then these need to be updated as well

10. Update references to any variables used in the Topology, e.g. as part of physical data servers

11. Update references to any variables or project functions used in other project functions

12. Next we need to replace any missing references inside the package

These are typically only references to variables unless your package also references procedures etc. fromoutside the root folder that we exported/imported

We need to recreate those links by deleting the variables in the package and adding them again. Make surethat you select the correct Variable Type when recreating the variable in the diagram (Refresh Variable,Declare Variable etc.).

Open the legacy package for a side by side comparison to minimise mistakes.

13. If you reference scenarios in your package and you pass variables to these scenarios you will also need torepoint the variables in the Additional Variables tab for this scenario

14. Replace and fix references to new markers

15. Delete any scenarios for the legacy object(s) and then for the migrated object(s) if applicable.

16. Generate scenario for the migrated object(s)

17. Export legacy objects for backup (optional, if you are the cautious type)

18. And finally: Delete any of the legacy objects you migrated.

Related posts

October 22, 2012 -- How to query a whole schema or even database?! This tip will save you hours andhours of boring work.I really like this tip especially its simplicity. It has saved me hours and hours of mind numbing wo...

Copying and moving objects between projects in ODI | BI-Quotient http://www.business-intelligence-quotient.com/?p=1549

2 of 4 7/19/2013 10:35 AM

Page 3: Moving Objects Between Projects in ODI

September 9, 2010 -- Subselect, derived tables, and subqueries in ODI 11GI think one of the best new features in ODI 11G is the subselect/subquery feature. In ODI 10 this co...

January 7, 2013 -- Extreme re-usability in ODI 11g (I can’t believe I am giving away this trick).Another Christmas and a second baby under my belt it’s time to get back to blogging. There were r...

December 12, 2012 -- How you can launch an ODI scenario through a web service call?ODI and Jetty The ODI 11g standalone agent now ships with its own lightweight application server (J...

October 30, 2012 -- ODI Snippets: What is the Optimization Context in ODI?There are a lot of confusing messages out there on what the Optimization Context in ODI is used for....

Leave Reply

Name: E-Mail: Website: Comment:

Looking for ODI developers in Dublin.

ODI developers required for contracts in Dublin. EU work permit needed. Get in touch if you areinterested!

About Me

Hi! I'm Uli Bethke. Data warehouse super hero and evangelist. I am based in Ireland.Nerdy stuff I am good at includes: anything data warehouse, data integration, dataquality, and ODI. Read more...

Recent Posts

ODI 11g Cookbook – The leading ETL tool now also has the best ETL book Jun 15, 2013

Copying and moving objects between projects in ODI | BI-Quotient http://www.business-intelligence-quotient.com/?p=1549

3 of 4 7/19/2013 10:35 AM

Page 4: Moving Objects Between Projects in ODI

Using ODI user functions to dynamically inject SQL into Interfaces May 19, 2013

Endeca text enrichment. Entities extraction, sentiment analysis, and text tagging withLexalytics customer defined lists. I love this one! Apr 18, 2013

Endeca text tagging: Tagging unstructured IT jobs data against a whitelist of LinkedInskills Apr 01, 2013

Oracle User Group Dublin, 12 March 2013. It’s FREE. Feb 14, 2013

Extreme re-usability in ODI 11g (I can’t believe I am giving away this trick). Jan 07, 2013

How you can launch an ODI scenario through a web service call? Dec 12, 2012

Search Blog

Blogroll

Data Warehousing BooksODI Experts

Tags

Amazon EC2 analytic functions Business Intelligence Business Intelligence Books CDC data warehouse books examples of data mining

google hsqldb jdbc lexalytics OBIEE odi 11g book odi api odi beginners odi best practice odi best practice

resources odi book odi documentation odi getting started odi jython ODI performance ODI performance tuning odi resource odi tutorials odi web

services ODM 11gR2 ODM 11g R2 Oracle Oracle Asynchronous Change Data Capture CDC Streams

oracle data integrator beginners oracle data integrator documentation oracle data integrator getting started oracle data integrator

resources Oracle Data Mining Book Oracle Data Mining links oracle odi Oracle Warehouse Builder sql Sunopsis Memory Engine text

mining web scraping

© 2012 BI-Quotient - All rights reserved.

Copying and moving objects between projects in ODI | BI-Quotient http://www.business-intelligence-quotient.com/?p=1549

4 of 4 7/19/2013 10:35 AM