Setup Target -Done

Renumbering ODI Repository -Done

2.3) Migrating Customizations to the Target ODI Repository Using Export/Import

--Backup target ODI Repo
--Export Security

===========================

2.3.1) On the Target

-- Export Global Context from Topology

2.3.2) On the Source

Export all below:

1.TaskFolders:Project Folder
Leaf folders in BI Apps Project that directly contains the interfaces, package
and Scenario. Exporting the folder ensures all the components are exported at the
same time.
2.DataStores - Individual data stores, either as customizations to an existing data
store, or entirely new custom data stores. Note: if the TaskFolder is being export
and has a dependency on the data store the datastore doesn't need to be explicitly
added using smart export.
3.Load Plan Components
4.Variables
5.Sequences
6.User Defined Functions (UDF)
7.Knowledge Modules (KM)

Note: Since the smart export automatically includes the dependencies, the total
objects exported may be considerably greater than the objects selected. As
calculating the dependencies is time and resource intensive, it's recommended that
this approach is used for a maximum of 50 task folders or other first class objects
(i.e. excluding dependencies) per export. If there are more than 50 objects, use
multiple smart exports and give each export filename a sequential number in order
to know the order to import on the target.

2.3.4) On Target Environment: Copy the export files to a drive on the target
machine. Log in to the ODI repository in target environment from ODI Studio. Invoke
the �Import� -> �Smart Import� option by clicking on the same icon on the top right
of the Designer tab. Select the file to be imported; in case of multiple files to
be imported, select the files one at a time in the same sequence as they were
exported.

2.3.6) Now, you need to import the topology settings from the backup taken in
step#3.1. For this, click on �Import� from topology navigator and then �Smart
Import�. Select the xml file that was created in step#2.3.1 and complete the
import.

2.4) Migrating Customizations to the Target Business Analytics Warehouse

As part of your customizations, you might have done some data model changes to the
data warehouse schema, such as creating new columns to existing tables or creating
whole new tables. In this section, we will see how to migrate these data model
changes into the data warehouse schema on the target environment

As part of moving the ODI repository customizations in step#2.3, the model changes
done in the �Oracle BI Applications� model in the ODI repository would have been
moved to the target ODI repository. Now, we will use this model in the target ODI
repository to generate a sql file that will contain all the data model changes and
later apply it onto the target data warehouse schema.

2.4.1. Make sure the �BIAPPS_DW� physical data server in the Topology navigator is
pointing to the target data warehouse schema

2.4.2. From the Designer navigator, under Projects, navigate to : BI Apps Project
-> Components -> DW -> Oracle -> Generate DW DDL -> Packages -> Generate DW DDL ->
Scenarios -> GENERATE_DW_DDL Version 001. Right click on this scenario and click
Execute.

2.4.3. Set the context, agent and log level and click OK.

2.4.4. Ensure to supply the value to the following variables in the popup dialog
box and click OK.

2.4.5. There will be a confirmation box that the session has started. From Operator
navigator, you can monitor the execution status of the procedure. Verify that it
executes successfully.

2.4.6. Once the session completes successfully, look for sql file with name
BIA_DW_Schema_DDL_<session#>.sql in the directory specified by the parameter value
UTIL_GENDDL_SCRIPT_LOCATION. Review the sql file to verify it has the necessary DDL
statements to reflect all the data model changes performed.
2.4.7. Execute this sql file on the data warehouse schema using any sql tool such
as Oracle SQL Developer or Oracle SQL Plus.

2.5 Migrating Customized Load Plan Dev Components to the Target ODI Repository.

2.6 Migrating Customizations to the Target RPD and Presentation Catalog

2.7 Defining, Generating and Executing Domains Load Plan in the Target Environment

2.8 Migrating Functional Setup Data to Configuration Manager in the Target

Environment

2.9 Defining, Generating and Executing Load Plans in the Target Environment

(Doc ID 1970123.1 Trimming BI Apps ODI Repository)

When attempting to perform a smart export of a large project folders errors may be
encountered refer Doc ID 1909012.1 for details and fix
Business Intelligence Applications ETL Guide
https://docs.oracle.com/cd/E51479_01/doc.111181/e51481/toc.htm