This tutorial shows you how to migrate your OWB 10gR1 project into the OWB 10gR2 repository. In this tutorial, you will use Warehouse Builder's MDL utility to export and import the metadata to OWB 10gR2.
Approximately 30 minutes
This tutorial covers the following topics:
|
Overview | |
|
Prerequisites | |
|
||
|
||
|
Examining the Imported Objects in the OWB_DEMO Project | |
|
Summary | |
Place the cursor over this icon to load and view all
the screenshots for this tutorial. (Caution: This action loads all screenshots
simultaneously, so response time may be slow depending on your Internet connection.)
Note: Alternatively, you can place the cursor over each individual icon in the following steps to load and view only the screenshot associated with that step.
You can export the metadata from a previous Warehouse Builder version to a file and then import the file into a newer version of Warehouse Builder. This is commonly done when upgrading to a newer version of Warehouse Builder. The Metadata Loader (MDL) enables you to copy or move metadata objects between repositories, even if those repositories reside on platforms with different operating systems. You can use the Warehouse Builder Design Center to run the MDL utility. The Metadata Loader consists of the following two utilities:
Metadata Export Utility: You use the Metadata Export Utility to export metadata from a Warehouse Builder repository. You can export an entire project, collections, public objects, locations, or any subset of objects. If you export a subset of objects, the MDL exports definitions for each object you have selected and the parent objects to which the subset belongs. This enables the MDL to maintain the tree relationships for those objects during metadata import. It creates an MDL file.
Metadata Import Utility: The metadata import utility
reads the metadata information from an exported MDL file and creates, replaces,
or merges the metadata objects into a repository. You can use the MDL import
utility to import objects into a project or a collection. The metadata import
utility only reads files created by the metadata export utility. The MDL imports
information belonging to exported metadata objects such as table columns and
their constraints, data loading configuration parameters, and named attribute
sets.
While importing metadata, the MDL Import utility automatically upgrades metadata created using previous versions of Warehouse Builder to OWB 10gR2. You do not need to manually upgrade your metadata from a previous version of Warehouse Builder.
In this tutorial, you will export the OWB_DEMO project that you deployed in a OWB 10gR1 repository into an mdl file. Then you will import the exported MDL file into the OWB 10gR2 repository. Because the exported mdl file will be created using OWB 10gR1, the MDL import utility in OWB 10gR2 will automatically upgrade the metadata.
Before starting this tutorial, you should have completed tutorial "Setting Up the Environment for Migration".
You can use Warehouse Builder Design Center to export objects from a Warehouse Builder repository into an MDL file. The information related to these objects such as table columns and their constraints, data loading configuration parameters, and named attribute sets are also exported.
To export the OWB_DEMO project, perform the following steps:
|
1. |
Select Start > Programs > {your Oracle - OWB10gR1clientHome}
> Warehouse Builder > OWB Client. In the Warehouse Builder Logon
window, enter design_client/design_client as the username/password. Expand the OWB_DEMO project. Ensure the OWB_DEMO project is selected. From the Project menu, select Metadata Export > File, as shown in the screenshot.
The Metadata Export Confirmation window displays. Click Commit. The Metadata Export dialog box displays.
|
|
2. |
In the Metadata Export dialog box, rename the Filename to OWB_DEMO_migrate.mdl and save it in c:\owb_demo_setup or the folder where you extracted the owb_demo_files.zip file. Note this is not a mandatory requirement, but only for better organization have all the mdl files in one place. Note the location of the log file, in case you need to refer to it later.
Click Export. The Metadata Export progress bar displays.
In the Metadata Export Results window, verify the export details. You can also click View Log File to view a detailed log of the export.
Click OK. Click Close to close the Metadata Export Results window. From the Project menu, select Exit to quit the OWB 10gR1 client. In Exit Confirmation window, click Yes to save the changes. You have exported the OWB_DEMO project metadata into an mdl file.
|
You can use the Warehouse Builder Design Center to import metadata. The Metadata Import Utility also automatically upgrades metadata that was created using an earlier release of Warehouse Builder to the current release.
To import objects from the OWB_DEMO_migrate.mdl export file into OWB 10gR2, follow the steps below:
| 1. |
If you have not already logged in, log in to the OWB Design Center. Select Start > Programs > [Oracle - OWB10gR2clientHome] > Warehouse Builder > Design Center. The Design Center Logon window displays. Enter rep_owner as username and password. In the Project Explorer panel, you will see the default project, MY_PROJECT. From the Design menu, select Import > Warehouse Builder Metadata.
The Metadata Import window displays. Note: If you had made changes to the repository metadata before running the import utility, the Warehouse Builder Warning dialog will be displayed. Click Save to save changes or Rollback to revert to the previously saved version. If you have not made any changes to the repository metadata after last saving the design, Warehouse Builder displays the Metadata Import dialog.
|
| 2. |
Click Browse to specify the filename for the metadata file. In the Open dialog box, select the OWB_DEMO_migrate.mdl file from c:\owb_demo_setup\ or from the location you saved the file during the export process. Note or modify the path of the Log file in case you need to review the log later. Note: Whenever you export or import repository metadata, the MDL writes diagnostic and statistical information to a log file. You can specify the location of the log file when you invoke MDL using the Metadata Loader utility. The log file enables you to monitor and troubleshoot export and import activities in detail. The import log file contains information about the object types imported, and displays the total number of objects added, replaced, skipped, or deleted.
|
| 3. |
The Metadata Upgrade dialog box displays. This dialog is displayed automatically when Warehouse Builder detects that an MDL file being imported is from an earlier version of Warehouse Builder. You can use the File Name field to specify the name of the file that stores the upgraded MDL file. As for now, accept the default name. Click Upgrade to upgrade the MDL file to the current version
of Warehouse Builder.
The Metadata Import Progress window displays.
|
| 4. |
After the import is completed, click Show Details. It shows the message log of the upgrade and the import. Scroll in the window to verify that there is no error reported. You can also click Show Statistics to view how many objects of each type was imported or skipped. In the screenshot, you see the statistics of the Import done.
Click Close.
|
| 5. |
The migrated project OWB_DEMO is added in the Project Explorer panel.
From Design Menu, select Save All to commit the changes. |
After you have migrated the project from OWB 10gR1 to OWB 10gR2, examine the objects that were imported. The upgrade utility makes a few changes to the objects. Many of the objects are represented differently as compared to OWB 10gR1.
You will now examine the changes to the repository objects after upgrading to OWB 10gR2.
| 1. |
Expand OWB_DEMO > Databases > Oracle > TGT.
|
| 2. |
Expand Dimensions. Expand Cubes. You can see all the four dimensions: BCHANNEL, BGEOGRAPHY, BPRODUCT, BT_TIME and the cube BSALES. Note: For Dimensions, an associated dimension table is created with the same name as the dimension. The table contains the columns, constraints, and attribute sets defined in the Dimension Editor Table Properties of the dimension in the previous release. For Cubes also, an associated cube table is created with the same name as the cube. The cube table contains columns, constraints, and attribute sets defined in the Cube Editor Table Properties of the cube in the previous release. Expand Tables to view all the added tables.
|
| 3. |
Expand Mappings. Note that all the mappings are imported.
|
| 4. |
The mapping operators for dimensions and cubes are converted to table operators. These table operators use the physical tables created by the MDL Upgrade Utility for dimensions and cubes. To check this change, right-click MAP_CHANNEL and select Open Editor.
The new Mapping Editor displays. Examine the mapping. The CHANNELS_EXT external table attributes are mapped to the CHANNEL table.
From Mapping menu, select Close to exit the Mapping Editor.
|
| 5. |
Locations and runtime repository connections are moved out of the projects that own them so that they can be shared across the entire repository. All the locations and connectors can be viewed in the Connection Explorer. The runtime repository connection, OWB_RT, is moved in as a Control center.
|
| 6. |
In the Project Explorer, expand Process Flows > Process Flow Modules > PROC_MOD > PFP. The LOAD_WH process flow displays. Also, the process flow location, PROC_LOC, that you registered with Workflow 2.6.4, is imported under Process Flow and Schedules > Oracle Workflow node in the Connection Explorer, as shown in the screenshot.
|
| 7. |
In the Project Explorer, expand Files to view all the imported files. Expand External Tables to view all the imported external tables. In the Connection Explorer, expand Files to view the imported file location.
From Design menu, select Exit. In Warehouse Builder warning dialog box , click Yes to quit the Design Center. |
In this lesson, you learned how to:
|
Export metadata using OWB 10gR1 Design Client | |
|
Import metadata using OWB 10gR2 Design Center | |
|
Examine the imported objects | |
Place the cursor over this icon
to hide all screenshots.