| Oracle® Warehouse Builder Installation and Administration Guide, 10g Release 2 (10.2.0.2) for Windows and UNIX Part Number B28224-04 |
|
|
View PDF |
| Oracle® Warehouse Builder Installation and Administration Guide, 10g Release 2 (10.2.0.2) for Windows and UNIX Part Number B28224-04 |
|
|
View PDF |
Refer to the following topics to upgrade to Warehouse Builder 10g Release 2 (10.2):
Figure 3-2 depicts the valid paths for upgrading to Warehouse Builder 10g Release 2 (10.2).
Figure 3-1 Valid Upgrade Paths to Warehouse Builder 10g Release 2 (10.2)
Notice that you can upgrade directly from Warehouse Builder 10.1.0.4 but from release 10.1.0.2 you must first upgrade to 10.1.0.4.
To upgrade from Warehouse Builder 9.2 or 10.1.0.5, first install Warehouse Builder 10.2, apply the patch for Warehouse Builder 10.2.0.2, and then proceed to upgrade from Warehouse Builder 9.2 or 10.1.0.5.
To upgrade to Warehouse Builder 10g Release 2 (10.2), refer to the following sections:
Understanding the Installation Requirements
Verify that your environment meets the new minimum requirements for machines hosting client and server components.
Understand changes to the product architecture described in Warehouse Builder Architecture and Components.
Identify and complete any changes necessary to the database environment.
Important: If you make changes to the database environment, maintain the same topology if possible. That is, maintain the same schema names to avoid impairing existing Warehouse Builder processes such as mappings which depend on database connection information. If you must change schema names, after you upgrade Warehouse Builder, take corrective actions to update the affected locations.
If you determine that you must upgrade to a new Oracle Database version, complete the steps in Migrating An Oracle Database Environment.
If you determine that the new control center is to be hosted on a database or server that is different from the existing runtime repository, do not continue with these instructions. Instead, refer to Selectively Migrating a Warehouse Builder Environment to a New Database.
Review the Oracle Warehouse Builder Release Notes.
Any instructions in the Release Notes supersede the instructions in this guide.
Installing the Warehouse Builder Software on the Server
Review the "Checklist: Before You Launch the Universal Installer". Launch the Oracle Universal Installer and follow the prompts to install the Warehouse Builder client software onto the computer you designated as the server.
Install a new repository.
From the Windows Start menu, select Programs and navigate to the Oracle product group. Select Warehouse Builder, Administration, and then Repository Assistant.
On UNIX, locate OWB_ORACLE_HOME/owb/bin/unix and execute reposinst.sh.
Follow the instructions Installing a Repository using the Advanced Setup Options.
Select the advanced set up option. If in the pre-existing repository you created multiple users through the optional PL/SQL package, take note of the instructions for Selecting Repository Users.
Install an additional repository for the runtime environment. (Optional)
In the previous release of Warehouse Builder, a separate runtime repository was required. You have the option to maintain that architecture in this release. Launch the Repository Assistant again to define a separate repository.
Reusing and Redeploying Specific Objects
You may need to take additional steps if you want to reuse certain objects such as Advanced Queues that you designed in a previous release.
Installing Optional Components (Optional)
See Chapter 5 for instructions on installing and configuring optional components.
Installing the Warehouse Builder Software on the Client Machines
Repeat the instructions Installing the Warehouse Builder Software for each computer to be used as a client.
When complete the installation process, you can launch all the Warehouse Builder components as described in Launching Warehouse Builder Components.
Deinstalling Oracle Warehouse Builder (Optional)
You have the option of deinstalling the existing components from the previous release. Or, you can deinstall pre-existing components at a later date.
If your current version of Oracle Database is compatible with Warehouse Builder, you can keep the current version or optionally choose to upgrade to a higher compatible version of the database. You can migrate your Oracle environment to a different instance of Oracle Database, or you can continue on the same instance.
Before You Begin
Before you upgrade the Oracle Database, stop the Warehouse Builder Runtime Platform Service if it is running.
Log on to the Runtime Platform as the runtime repository owner. Run the ORACLE_HOME\owb\rtp\sql\stop_service.sql script.
Upgrading to Oracle Database 10g (10.x)
To upgrade to Oracle Database 10g (10.x), refer to the Oracle Database 10g Upgrade Guide for instructions.
If you intend to upgrade to Oracle Database 10g while maintaining the same database instance, all relevant instructions are detailed in the Oracle Database 10g Upgrade Guide. Continue with step 4 in General Steps for Upgrading to Warehouse Builder 10g Release 2 (10.2).
If you intend to create a new database instance, you must take the additional steps of either Migrating a Complete Database or Selectively Migrating a Warehouse Builder Environment to a New Database.
Upgrading to Oracle9i Database Release 2 (9.2)
To upgrade to Oracle9i Release 2 (9.2), refer to the Oracle9i Database Migration guide (Part Number A96530-02).
In this case you must create a new database instance and therefore you take the additional steps of either Migrating a Complete Database or Selectively Migrating a Warehouse Builder Environment to a New Database.
Follow the instructions in the upgrade documentation for Oracle Database 10g.
If Oracle Workflow is installed on the pre-existing Oracle Database instance, you must take additional steps for Upgrading Oracle Workflow on a New Oracle Database Instance.
Upgrading Oracle Workflow on a New Oracle Database Instance
After you move the Oracle Database instance, Warehouse Builder process flows remain registered to the Oracle Workflow installed on the pre-existing Oracle Database instance. Take the following precautions now, that is, prior to upgrading runtime metadata.
To upgrade Oracle Workflow on a new Oracle Database instance:
Run the Oracle Workflow assistant in Upgrade mode on the new database instance to upgrade the workflow schema.
Your workflow locations are now upgraded. However, they remain registered to the pre-existing instance of Oracle Workflow.
Continue with step 4 in General Steps for Upgrading to Warehouse Builder 10g Release 2 (10.2).
Following the general steps, you install the Warehouse Builder software and then install a repository.
Register the Workflow user in the new repository.
Launch the new Design Client and navigate to the security interface. In the Global Explorer on the lower right window, expand the Security node and right-click the Users node to create a new user. Add a new user with the same name as your workflow user in the pre-existing database from which you are migrating. Deselect the user as target.
Continue with Upgrading a Design Repository followed by Upgrading a Runtime Repository to a Control Center.
To ensure that the pre-existing Workflow instance is still running, from the new Design Center, execute one of the process flows.
The final step is Redeploying Process Flows.
Manually re-register the workflow locations and redeploy the process flow packages from within the new version of Warehouse Builder.
Use this option to selectively move a Warehouse Builder environment from one Oracle Database to another. You must use this option if the new control center is to be hosted on a database or server different from the existing runtime repository.
As this is the most challenging migration and upgrade scenario, avoid this scenario if possible. Do not use this option if you intend to either keep the same database instance or migrate the full database.
Steps for Migrating Warehouse Builder to a New Database
Review the Oracle Warehouse Builder Release Notes.
Any instructions in the Release Notes supersede the instructions in this guide.
Installing the Warehouse Builder Software on the Server
Review the Checklist: Before You Launch the Universal Installer. Launch the Oracle Universal Installer and follow the prompts to install the Warehouse Builder client software onto the computer you designated as the server.
Install a new repository.
From the Windows Start menu, select Programs and navigate to the Oracle product group. Select Warehouse Builder, Administration, and then Repository Assistant.
On UNIX, locate OWB_ORACLE_HOME/owb/bin/unix and execute reposinst.sh.
Select the advanced set up option and follow the instructions Installing a Repository using the Advanced Setup Options.
When creating a new database user, create the user with the identical schema name, default tablespace, and temporary tablespace as its previous counterpart in Warehouse Builder 9.2.x, or 10.1.x.
Exporting Target Schemas from the Existing Runtime Environment
Copying External Directory References to the New Database Instance (Optional)
Registering the Users from the Previous Warehouse Builder Environment
Take manual steps to reuse specific types of objects.
If the existing Warehouse Builder environment included flat files and external tables, complete Reusing Flat Files and External Directories from a Different Database Instance .
See Reusing and Redeploying Specific Objects for additional steps to reuse certain objects such as Advanced Queues that you designed in a previous release.
Installing Optional Components (Optional)
See Chapter 5 for instructions on installing and configuring optional components.
Installing the Warehouse Builder Software on the Client Machines
Repeat the instructions Installing the Warehouse Builder Software for each computer to be used as a client.
When complete the installation process, you can launch all the Warehouse Builder components as described in Launching Warehouse Builder Components.
Deinstalling Oracle Warehouse Builder (Optional)
You have the option of deinstalling the existing components from the previous release. Or, you can deinstall pre-existing components at a later date.
Pre-create the tablespaces in the Oracle Database 10g environment to exactly match the tablespaces in the existing version of Oracle Database.
Use Oracle Export in existing version of the Oracle Database to export the existing target schemas into a DMP file with the following command for each schema:
exp OldOWBTargetUserName/OldOWBTargetUserPassword@Old_DBTNSConnection Owner=OldOWBTargetUserName FILE=OldOWBTarget.dmp LOG=OldOWBTarget.log
OldOWBTargetUser stands for the Warehouse Builder target schema user from the existing version of Warehouse Builder.
For example, type:
exp owb_target/owb_target owner=owb_target FILE=owb_target.dmp LOG=owb_target.log
Identify all the tablespaces for each of the existing Warehouse Builder target schema users.
Connect to SQL*Plus in the existing version of the Oracle Database as the Warehouse Builder target schema user, and then enter the following command:
select distinct TABLESPACE_NAME from user_segments;
Enter the following to check the default and temporary tablespaces for existing Warehouse Builder target schema users:
select DEFAULT_TABLESPACE, TEMPORARY_TABLESPACE from user_users;
In the Oracle Database 10g instance, create the tablespaces you listed from the existing instance in Exporting Target Schemas from the Existing Runtime Environment.
In the Oracle Database 10g, connect as a SYS user to SQL*Plus to create each target schema and grant privileges to it.
For each target schema you create, enter the following command in SQL*PLus:
connect SYS/SYS as sysdba;
create user OldOWBTargetSchemaUser identified by OldOWBTargetSchemaPassword default tablespace users temporary tablespace temp;
SET DEFINE %
define user=OldOWBTargetSchemaUser
@<new OWB_ORACLE_HOME>\owb\rtasst\upgrade\preowb10_2\warehouse_system_rights.sql
@<new OWB_ORACLE_HOME>\owb\rtasst\upgrade\preowb10_2\xmltk_grant.sql
Complete this section if in the pre-existing Warehouse Builder environment includes external directories which are used by external tables and flat files.
External directories have two elements: the logical and the physical. The logical element is the reference residing in the database to a directory located outside the database. These instructions migrate the logical elements. You migrate the physical elements in a later step subsequent to upgrading the runtime environment.
To migrate the external directories for each target schema users:
Create a copy of the script gen_ext_dirs.sql.
Locate OWB_ORACLE_HOME\owb\mig\gen_ext_dirs.sql on the new host, that is, the computer hosting the new Warehouse Builder installation.
Copy the file to a temporary directory on the original host, that is, the computer hosting the pre-existing version of Warehouse Builder from which you are migrating.
In SQL*Plus, connect as a Warehouse Builder target schema user and run TEMP\gen_ext_dirs.sqlon the original host computer.
Locate the ext_dirs.sql file generated in the SQL*Plus default directory.
Typically, this default directory is ORACLE_HOME\bin.
Rename the generated script.
As you complete these instructions, you generate a separate script for each Warehouse Builder target schema use. Consider renaming the file to indicate the target schema.
Transfer the generated and renamed ext_dirs_<TargetUserName>.sql file to a temporary location on the new host.
On the new host, use SQL*Plus to connect as the Warehouse Builder 10g Release 2 (10.2) target schema user and execute ext_dirs.sql.
Repeat steps 2 through 6 for each target schema user you intend to migrate.
Use Oracle Import to import the target schema files into the new user you created.
To import a target schema:
To import the target schema DMP file you created in Exporting Target Schemas from the Existing Runtime Environment, enter the following command:
imp OldOWBTargetUserName/OldOWBTargetUserPassword@New_DBTNSConnection FILE=OldOWBTarget.dmp LOG=NewOWBTarget.log
OldOWBTargetUser stands for the Warehouse Builder target schema user from the existing version of Warehouse Builder.
For example, enter:
imp owb_target/owb_target@New10gConnection FILE=owb_target.dmp LOG=c:\temp\owb_target_import.log
Examine the import log file, whose name and location you specified in the import command.
Proceed to the next step only if the last line of the log file states: "Import terminated successfully without warnings."
If the last line of the log file states: "Import terminated unsuccessfully," you must fix all import errors before proceeding.
Repeat these instructions for each target schema you want to migrate.
Log on to the Design Center as the repository owner that you defined when creating the new repository.
Add and register a user for each target schema you migrated into the new database.
In the Global Explorer on the lower right window, expand the Security node and right-click the Users node to create a new user. Add a new user with the same name as the target schema in the pre-existing database from which migrated.
Repeat the previous step for each user from the previous Warehouse Builder environment that you want to access the new repository. Be sure to consider any Oracle Workflow users from the previous environment.
If you have numerous users to register, consider using the OMB Plus scripting language as an alternative to the security interface. For example, to register a user OWF_MGR, connect to OMB Plus and type commands such as the following:
OMBREGISTER USER 'OWF_MGR' SET PROPERTIES(DESCRIPTION, ISTARGETSCHEMA) VALUES ('remote workflow user', 'false')OMBLIST SYS_PRIVS OF USER 'OWF_MGR'
Note:
This concludes the steps to register users from a previous Warehouse Builder environment into a new database. Continue with the next step in Selectively Migrating a Warehouse Builder Environment to a New Database.Follow these instructions if you want to upgrade only a portion of an existing repository. For example, use these instructions to export and import selected projects or collections.
Create a full database backup before you begin. Additionally, create metadata export (MDL) files for all Warehouse Builder projects. Keep these backups until you have completed and tested the entire upgrade process.
Follow these instructions if you are upgrading to Warehouse Builder 10g Release 2 (10.2), regardless of whether or not you upgraded your Oracle Database.
Export design metadata from the existing version of Warehouse Builder into an MDL file using the Metadata Loader.
Use the new version of Warehouse Builder to create a new repository.
Import design metadata into the new repository.
Export each project, collection, or public transformation you want to migrate to Metadata Loader (MDL) files using the Metadata Loader. If you have created any user-defined definitions, you will need to export these objects too. For more information on exporting metadata, see the Oracle Warehouse Builder User's Guide.
Note:
To upgrade, you must export and import metadata using the Metadata Loader. Warehouse Builder upgrade does not support files that were exported or imported using back end database commands.To export existing metadata into an MDL file:
Use the prior version of the Warehouse Builder client to select the project, collection, or public transformation you want to export.
For information about exporting user-defined definitions, refer to the Oracle Warehouse Builder User's Guide.
From the Project menu, choose Export Metadata, then File.
The Metadata Loader assigns a path and file name to the exported MDL file. Make a note of the path and filename for all data you export. For more information on exporting metadata, refer to the Oracle Warehouse Builder User's Guide.
After having installed the new software, you must import and upgrade design metadata into the new version of Warehouse Builder. Ensure that you first import custom public transformations, if any. Use the Metadata Import utility to import design metadata. For more information on importing metadata, see the Oracle Warehouse Builder User's Guide.
Note:
Warehouse Builder upgrade does not support files that were exported or imported using back end database commands.To import and upgrade metadata into the new Warehouse Builder repository:
From the new Warehouse Builder Design Center, select the Design menu, Import, and Warehouse Builder Metadata.
The Metadata Import dialog is displayed.
In the File Name field, specify the path and file name of the exported data from the former repository.
In the Log File field, specify the path and file name of the log file or click Browse to locate a directory and file name. Warehouse Builder records information about the import in this log file.
In the Import Option section, select the import option used while importing metadata. The options available are:
Create new metadata only: Adds new metadata to a repository.
Update metadata (replace existing objects and create new metadata): Adds new objects and replaces existing objects with those in the MDL file.
Merge metadata (merge existing objects and create new metadata): Adds new objects and overwrites existing objects only if they are different from those in the MDL file. Existing objects are not deleted.
Replace existing objects only: Replaces existing objects in the repository.
In the Match By section, select Universal Identifier.
(Optional) If the MDL file contains additional languages or user-defined definitions, click the Advanced button to select the options that include them in the import.
Since the MDL file being imported was created using an earlier version of Warehouse Builder, the Metadata Upgrade dialog is displayed. Click Upgrade to upgrade the MDL file to the current version. Click Cancel if you do not want to upgrade the MDL file.
If the MDL file is upgraded, the Import Advanced Options dialog is displayed. Use this dialog to import the following:
Additional language metadata
User-defined definitions
Click OK to save your selections and close the Import Advanced dialog. For more information about the advanced import options, refer Oracle Warehouse Builder User's Guide.
(Optional) To view a detailed summary of the contents of the export MDL file, click Show Summary.
Since the MDL file being imported was created using an earlier version of Warehouse Builder, the Metadata Upgrade dialog is displayed. Click Upgrade to upgrade the export MDL file to the current version. Click Cancel if you do not want to upgrade the MDL file.
If the MDL file is upgraded, the Show Summary dialog is displayed. This dialog provides a brief summary of the contents of the export MDL file.
Click Import to import the MDL file.
If the MDL file was not previously upgraded in step 6 or step 7, the Metadata Upgrade dialog is displayed. Click Upgrade to upgrade the export MDL file to the current version. Click Cancel if you do not want to upgrade the MDL file.
If you click Upgrade, the Metadata Progress dialog displays the progress of the upgrade and import operation. After the upgrade completes, click Close to return to the Design Center.
In prior versions of Warehouse Builder, locations and runtime repository connections were owned by individual projects. In Oracle Warehouse Builder 10g Release 2 (10.2), locations and runtime repository connections are owned by a project called PUBLIC_PROJECT. If locations or runtime repository connections with the same names as the ones being upgraded exist in the repository, Warehouse Builder generates unique names when they are imported for the upgrade. You may need to manually clean up location associations after the upgrade is complete.
For more information about the changes made to repository objects after an upgrade and import operation, see Oracle Warehouse Builder User's Guide.
In previous releases, runtime repositories were managed by the interface known as the Deployment Manager. Beginning in this release, the Control Center Manager replaces the Deployment Manager. The term runtime repository from previous releases is replaced by the term control center.
To upgrade from a runtime repository to a control center, use the Control Center Upgrade Assistant.
For Windows, launch <oracle_home>\owb\bin\win32\cc_migrate.bat.
For UNIX, launch <oracle_home>\owb\bin\UNIX\cc_migrate.sh.
Use the Control Center Upgrade Assistant to move audit data from a runtime repository that you created in a previous release. After you use the Control Center Upgrade Assistant, use the Control Center to manage runtime repositories, now referred to as control centers.
Before you Begin
If you recently migrated to an Oracle 10g database using the full migration option, ensure that you completed the steps for Upgrading Oracle Workflow on a New Oracle Database Instance.
Supported Upgrade Scenarios
Use this assistant to complete any of the scenarios illustrated in Figure 3-2.
Figure 3-2 Valid Upgrade Paths to Oracle Warehouse Builder 10g Release 2 (10.2)
Notice that you can upgrade directly from Warehouse Builder 10.1.0.4 but from release 10.1.0.2 you must first upgrade to 10.1.0.4.
To upgrade from Warehouse Builder 9.2, first install Warehouse Builder 10.2, apply the patch for Warehouse Builder 10.2.02, and then proceed to upgrade from Warehouse Builder 9.2.
Connect to the Warehouse Builder 10gR2 repository you newly defined for the runtime environment. This can be the same repository or a separate repository from the design environment, as described in step 6 and 7 of General Steps for Upgrading to Warehouse Builder 10g Release 2 (10.2).
Connect to the repository as the repository owner.
As you use the Control Center Upgrade Assistant, the assistant prompts you to connect to a runtime repository. This repository refers to the pre-existing runtime repository created in a previous release of Warehouse Builder.
By default, the assistant assumes that the new control center and existing runtime repository share the same host name, port number, and Oracle service name. This is the case for the most common upgrade scenarios including the following scenarios:
Since the time you created the runtime repository, you did not upgrade the Oracle Database to a new version.
You did upgrade the Oracle Database but performed a full database migration such as described in Migrating a Complete Database.
If you want to upgrade to a control center on a different host or database than the existing runtime repository, then you should first complete the steps in Selectively Migrating a Warehouse Builder Environment to a New Database, launch the Control Center Upgrade Assistant again, and then enter the correct connection information for the runtime repository.
Use the upgrade operations in the following order:
Select Move to transfer location registration information and audit data from the pre-existing runtime repository to the new control center.
After you successfully move location registration information, you access the other options for Upgrade and Generate.
Select Upgrade to upgrade the locations details that you previously moved for use in the new control center.
Select Generate to create a Tcl script that you can later apply to update a design repository.
Proceed with Upgrading Locations in the Design Repository.
When you select the Move operation, the assistant prompts you to connect to the original runtime repository as a repository owner.
In this step, you upgrade runtime audit data so that the new control center displays the correct status, history, location details, and version numbers for objects you deployed and executed objects in the pre-existing runtime repository from the previous release.
This option is only available if the new control center does not contain any registered locations or audit data.
The assistant lists the locations registered in the new control center and displays whether they are valid or not. Figure 3-3 displays the Upgrade Registered Locations dialog.
Figure 3-3 Upgrade Registered Locations Dialog
Use this button to check and fix locations for possible errors. Ensure that all locations are valid before proceeding. Figure 3-4 displays the Registered Locations Details dialog.
Figure 3-4 Registered Locations Details Dialog
Use this operation to generate a Tcl script that you then must alter to update location information in the design repository.
To generate a Tcl script that updates location information:
Ensure that you previously imported MDL from the previous design repository to the new Warehouse Builder 10g Release 2 (10.2) repository as described in Upgrading a Design Repository.
Click Generate.
Edit the script to change the value of the variable CC_NAME.
Either edit the script in the user interface and select save again. Or edit the script in Notepad.
Set CC_NAME to the name of the control center object in the new design repository. For example, assume that you migrated a runtime repository called MY_DEV_RUNTIME from a previous of Warehouse Builder. Therefore, in the Tcl script, change the line
CC_NAME cc_name
to
CC_NAME MY_DEV_RUNTIME
Save the edited script in a temporary directory.
Click OK in the Generate dialog and complete the Control Center Upgrade Assistant.
Proceed with Upgrading Locations in the Design Repository .
Verify your selections in the assistant before clicking Finish.
On the summary page, control center refers to the new control center to which you are upgrading. Runtime repository refers to the repository from which you are upgrading.
After you generate a Tcl script using the Generate, use an OMB Plus session to connect to the new design repository using the OMBCONNECT command.
For example, enter:
OMBCONNECT <new repo name>/pwd@newhost:port:servicename>
For more information on OMB Plus commands, see the Oracle Warehouse Builder Scripting Reference.
Run the Tcl script against the new design repository.
For example, enter at the OMB Plus prompt:
source/temp_path/my_generated_script.tcl
When you run the script, the details for the control center and the location address are seeded into the design repository. Each location is associated with the control center. The registration details are also added to the logical location since, beginning in Warehouse Builder 10g Release 2 (10.2), these details can be stored in the Design Center.
For each project that you migrated, ensure that a configuration object uses the control center object you specified for the CC_NAME variable previously in these instructions.
In the Design Center, expand the project node, and expand the Configurations node. Right-click DEFAULT_CONFIGURATIONS and select Open Editor.
On the Name page, enable the Set and Save option.
On the Details tab, select the incoming control center which is the same control center you set for CC_NAME.
Save the changes you made in the Design Center by selecting Save All from the Design menu.
To view and re-deploy the migrated objects, launch the Control Center Manager from the Tools menu.
Register all of the locations and provide any passwords.
For security purposes, the location passwords are not saved. In the Control Center Manager, right click each location and select Register. Enter the password and optionally test the connection.
This section includes the following additional instructions for reusing objects you created in a previous release:
Warehouse Builder 10g Release 2 (10.2) introduces significant changes to the logical model for dimensions and cubes. After migration, dimensions and cubes appear as new objects in the Control Center Manager.
New validation rules may cause errors or warnings that did not exist in your previous Warehouse Builder installation. This is expected and does not indicate problems with your migrated data. Validate the cubes and dimensions and fix errors that may prevent you from redeploying the objects. Redeploy the objects as this is necessary for updating the audit history.
In a previous release you may have created a mapping with Advanced Queues. Only if you intend to redeploy such a mapping in this release, you must first create a separate table for each AQ with the following structure:
PAYLOAD SRC_TYPE107,
MSG_ID RAW(16),
CONSUMER_NAME VARCHAR2(30),
MSG_ORDER NUMBER,
CORR_ID VARCHAR2(128),
MSG_PRIORITY NUMBER
If you upgraded the Oracle Database for Oracle 10g and created a new database instance, you should have followed the instructions for Upgrading Oracle Workflow on a New Oracle Database Instance .
Now that you have upgraded runtime metadata through the Control Center Upgrade Assistant, you can re-register the Workflow locations and redeploy the process flow modules and packages.
After redeploying mappings, update the configuration of each mapping to benefit from the new features available in the upgraded version of Warehouse Builder.
Use the following criteria to determine whether you can skip this section:
If you are upgrading from release 9.2.x, you only need to follow these instructions if you migrated from an earlier release to release 9.2.x without updating the mapping configuration at that time.
You can skip this section if release 9.0.4.x or 9.2.x was your first installation of Warehouse Builder, or if you already performed these steps when you migrated to either of those two releases.
You can update the mapping configuration either by using the Warehouse Builder interface, or by running a script to update all the mappings in the Oracle Metabase (OMB) Plus scripting utility.
To update the configuration of each mapping using the Warehouse Builder interface:
In the upgraded Warehouse Builder client, right-click each mapping and select Configure.
In the Configuration Properties box, expand the Sources and Targets node.
In the Sources and Targets node:
Delete the contents of the Schema configuration parameters field.
Delete the contents of the DB Links configuration parameters field.
Redeploy each mapping for which you changed the configuration properties in order to generate new code. For instructions on deploying mappings, refer to the Oracle Warehouse Builder User's Guide.
Alternatively, you can update all mappings by running the script provided for this purpose on the Oracle Technology Network. The update script is called UpdMapConfig.tcl.
To update the configuration of each mapping using a script:
Download the UpdMapConfig.tcl file from http://otn.oracle.com/sample_code/products/warehouse/content.html.
Start Oracle Metabase (OMB) Plus.
Connect to the new design repository.
Change the context in OMB Plus to the correct project and module. You must run this script module by module.
Run the script in OMB Plus.
At the OMB Plus prompt, type source, and then the location of the script surrounded by quotation marks.
For every backward slash, enter a second backward slash to escape the first.
For example, if your script is located in c:\temp, type: source "c:\\temp\\UpdMapConfig.tcl"
Run the following commands in OMB Plus to update the mappings and commit the changes to the design repository:
owb_reset_mapping_conns
OMBCOMMIT
Repeat this step by navigating to other target modules using the OWBCC command and running the owb_reset_mapping_conns command again.
Redeploy each mapping for which you changed the configuration properties in order to generate new code. For instructions on deploying mappings, refer to the Oracle Warehouse Builder User's Guide.
Complete the instructions in this section only if both of the following are true:
If you migrated the Oracle Database by Selectively Migrating a Warehouse Builder Environment to a New Database.
AND
If you had flat files or external tables in the existing Warehouse Builder environment
If both of these points are true, you must copy the following objects from the computer hosting the existing instance of Oracle Database to the computer hosting the new instance:
Flat Files: Copy any flat files used by SQL*Loader from the computer hosting the existing instance of Oracle Database to the computer hosting the new instance.
External Directories: You must also copy all external directories from the computer hosting the existing instance of Oracle Database to the computer on which Oracle Database 10g resides. Make sure to re-create identical file system directories.
|
 Copyright © 2000, 2009, Oracle and/or its affiliates. All rights reserved. Legal Notices |
|
