| Oracle® Warehouse Builder Installation and Configuration Guide 10g Release 1 (10.1) Part Number B12150-02 |
|
|
View PDF |
| Oracle® Warehouse Builder Installation and Configuration Guide 10g Release 1 (10.1) Part Number B12150-02 |
|
|
View PDF |
This chapter provides instructions for upgrading an existing system that was built using a prior version of Warehouse Builder to Oracle Warehouse Builder 10g Release 1 (10.1). Upgrading to the current version consists of upgrading your Oracle Database environment, upgrading your Warehouse Builder software, migrating your design metadata, and migrating your runtime system. Test the new installation before you deinstall the previous Warehouse Builder version and its repositories. The upgrade consists of the following high-level steps:
Why Upgrade to Warehouse Builder 10g Release 1 (10.1)?
The following are reasons to upgrade to Warehouse Builder 10g Release 1 (10.1):
You must upgrade to Warehouse Builder 10g Release 1 (10.1) if any of your data sources are on Oracle Database 10g, or if you plan to use Oracle Database 10g for any of your data targets.
If you are upgrading from Warehouse Builder Release 9.0.4.x or earlier, the process for upgrading to Warehouse Builder 10g Release 1 (10.1) is simpler than the process for upgrading to Warehouse Builder 9.2.0.2.8 with the required 9.2.0.4.0 patches.
Warehouse Builder 9.2.x will not be supported with any additional patches after 9.2.0.4.0.
Warehouse Builder 10g Release 1 (10.1) is supported on more operating systems than its predecessor. Refer to Chapter1, "Operating System Information" for more information.
Using This Chapter
Begin by reading the Oracle Warehouse Builder Release Notes for this new release. The section entitled "Upgrade" provides useful information that is not in this manual.
In this chapter, the process of upgrading to Oracle Warehouse Builder 10g Release 1 (10.1) has been divided into seven sections, which you must complete in the order presented in this document. Depending on the specifics of your upgrade scenario, you will be instructed to skip some sections, procedures, or steps because they do not apply to your platform, software version, or upgrade choice. If you are instructed to skip any section, proceed to the next section.
Without deinstalling your current Warehouse Builder software, follow the installation instructions in Chapter2 to install the Warehouse Builder 10g Release 1 (10.1) software in a new, separate Oracle home directory.
If you are moving the Oracle Database instance hosting your Target Schemas to another computer as part of your upgrade, you must install Warehouse Builder on that new computer.
Warehouse Builder 10g Release 1 (10.1) is compatible with the following versions of Oracle Database:
Oracle8i Release 3 (8.1.7.4.x)
Oracle9i Release 2 (9.2.x)
Oracle Database 10g Release 1 (10.1)
If you are currently using a version of Oracle Database that is compatible with Warehouse Builder, you can choose to upgrade to a higher compatible version of the database, or you can choose to keep your current version. You can migrate your Oracle environment to a different instance of Oracle Database, or you can continue with your work on the same instance.
Keeping the Same Version and Instance of Oracle Database
If you are not upgrading to a higher version of Oracle Database, and if you are not changing the database instance, skip the rest of Chapter3 and continue to Chapter3.
Upgrading Oracle Database
Chapter3 is for users upgrading to Oracle9i Release 2 (9.2.x) or to Oracle Database 10g Release 1 (10.1).
Note:
Before you upgrade Oracle Database, stop the Warehouse Builder Runtime Platform Service if it is running.To stop the Runtime Platform Service:
Log on to the Runtime Platform as the Runtime Repository owner.
Run the ORACLE_HOME\owb\rtp\sql\stop_service.sql script.
If you are upgrading to Oracle Database 10g (recommended), refer to the Oracle Database 10g Upgrade Guide (Part Number B10763-01) for instructions on upgrading and migrating your Oracle Database environment. If you are upgrading to Oracle9i Release 2 (9.2), refer to the Oracle9i Database Migration guide (Part Number A96530-02).
You can migrate your Oracle Database environment in one of three ways:
Full Database Export/Import if Moving to a New Database Instance
Database Migration Utility if Keeping the Same Database Instance
Use this option if you are moving to a new Oracle Database instance as you upgrade. Refer to the upgrade documentation for Oracle Database 10g for detailed instructions.
When you have successfully completed the database import, proceed to Chapter3, "Upgrading Design Metadata".
If Oracle Workflow is Installed on the Oracle Database Instance Being Moved
After you move the Oracle Database instance and upgrade Warehouse Builder, your process flows remain registered to the Oracle Workflow installed on your old Oracle Database instance. To re-register them to the new database instance, take the following precautions prior to running the RT_Upgrade_to_10_1 script discussed in Chapter3 of this chapter.
To register a Process Flow to the Oracle Workflow on your new Oracle Database instance:
Before following the instructions in Chapter3, run the Oracle Workflow assistant in Upgrade mode on your new database instance to upgrade the workflow schema.
Make sure that the old instance is still running.
Continue with the instructions in Chapter3.
Your workflow locations are now upgraded, but they remain registered to your old instance of Oracle Workflow. Manually re-register the workflow locations and redeploy the process flow packages.
Use this option if you are upgrading to Oracle Database 10g, but staying on the same database instance. Refer to the upgrade documentation for Oracle Database 10g for detailed instructions.
When you have successfully completed the database migration, proceed to Chapter3, "Upgrading Design Metadata".
You can only use Partial Database Export/Import if your prior version of Warehouse Builder was 9.0.4.x or 9.2.x. If your prior version of Warehouse Builder was 9.0.3.x or earlier, you must use the Full Database Ex2port/Import or the Database Migration Utility and skip Chapter3.
When you have successfully completed the database import, proceed to Chapter3, "Upgrading Design Metadata".
Considerations
This option is for users upgrading to Oracle Database 10g who want to be selective about what is moved from the prior version of Oracle Database to the new version. Do not use the Partial Database Export/Import if either the Full Database Export/Import or the Database Migration Utility can meet your needs. If you choose the Partial Database Export/Import, you must:
Pre-create the tablespaces in your Oracle Database 10g environment to exactly match the tablespaces in your prior version of Oracle Database.
Whenever an upgrade instruction in this chapter requires creating a Warehouse Builder user, create the user with the identical schema name and default tablespaces as its prior counterpart in Warehouse Builder 9.0.4.x or 9.2.x.
Migrating your design metadata involves:
Exporting your design metadata
Importing your design metadata
After you have completed these two procedures on your design metadata, continue with the rest of this chapter. Make sure to follow the instructions in Chapter3, "Automatic Upgrade Script for Warehouse Builder Design Metadata" to complete your design metadata upgrade.
To export and import your design metadata, perform this procedure for each Target Schema owned by the Runtime Repository you are migrating:
Use Oracle Export in your Oracle8i Release 3 (8.1.7.4.x) or Oracle9i Release 2 (9.2.x) database to export your old Design Repository into a DMP file by entering:
exp OldOWBDesignUserName/OldOWBDesignUserPassword@Old_DBTNSConnection owner=OWBDesignUserName FILE=OWBDesignUserName.dmp LOG=OWBDesignUserName.log
OldOWBDesignUser stands for your prior Warehouse Builder Design Repository user.
For example, enter:
exp owb_design/owb_design owner=owb_design FILE=owb_design.dmp LOG=owb_design.log
Identify all the tablespaces for your old Warehouse Builder Design Repository schema user.
Connect to SQL*Plus in your Oracle8i Release 3 (8.1.7.4.x) or Oracle9i Release 2 (9.2.x) database as the Warehouse Builder Design Repository user, and enter the following command:
select distinct TABLESPACE_NAME from user_segments;
Enter the following to check the default and temporary tablespaces for your old Warehouse Builder Design Repository schema user:
select DEFAULT_TABLESPACE, TEMPORARY_TABLESPACE from user_users;
In your Oracle Database 10g database instance, create the tablespaces you listed from your prior instance in Step 2.
In your Oracle Database 10g database instance, connect as the SYS user and create the new Warehouse Builder Design Repository user with the same name, the same default data tablespace, and the same temporary tablespace as your old Design Repository. For example, in SQL*PLus, type:
connect SYS/SYS as sysdba;
create user owb_design identified by owb_design default tablespace users temporary tablespace temp;
In your Oracle Database 10g database instance, connect as the SYS user in SQL*Plus and grant privileges to the Warehouse Builder Design Repository user.
You can obtain a list of the required privileges in OWB_ORACLE_HOME\owb\reposasst\grantpriv.sql
Use the following command in SQL*PLus:
connect SYS/SYS as sysdba;
SET DEFINE %
define user=OWBDesignRepositoryUser
@OWB_ORACLE_HOME\owb\reposasst\grantpriv.sql
Create two roles under the Warehouse Builder Design Repository user: the OWB_OWBDesignRepositoryUser role and the OWBR_OWBDesignRepositoryUser role. For example, in SQL*PLus, type:
connect owb_design/owb_design;
create role OWB_owb_design;
create role OWBR_owb_design;
Use Oracle Import to import the old design metadata DMP file into the new Warehouse Builder Design Repository user as follows:
imp OWBDesignUserName/OWBDesignUserPassword @New_dbTNSConnection FILE=OWBDesignUserName.dmp LOG=OWBDesignUserName.log
For example, in SQL*PLus, enter:
imp owb_design/owb_design@old_server FILE=owb_design.dmp LOG=owb_design.imp.log
Migrating the runtime environment involves:
Exporting the Target Schemas and Creating the New Runtime Environment
Copying External Directory References to Your New Database Instance
After you have completed these three procedures on your runtime environment, continue with the rest of this chapter. Make sure to follow the instructions in Chapter3, "Upgrading Audit Data from Warehouse Builder 9.0.4.x or 9.2.x" to complete your runtime upgrade.
first export your runtime data from your current version of Warehouse Builder and import it into your new Warehouse Builder Runtime Repository.
To export and import your runtime data:
Use Oracle Export in your Oracle8i Release 3 (8.1.7.4.x) or Oracle9i Release 2 (9.2.x) database to export your old 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 your Warehouse Builder Target Schema user from your prior 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 your each of your old Warehouse Builder Target Schema users.
Connect to SQL*Plus in your Oracle8i Release 3 (8.1.7.4.x) or Oracle9i Release 2 (9.2.x) database as the Warehouse Builder Target Schema user, and enter the following command:
select distinct TABLESPACE_NAME from user_segments;
Enter the following to check the default and temporary tablespaces for your old Warehouse Builder Target Schema user:
select DEFAULT_TABLESPACE, TEMPORARY_TABLESPACE from user_users;
In your Oracle Database 10g instance, create the tablespaces you listed from your prior instance in Step 2.
Following the instructions in Chapter2, use the Runtime Assistant in Warehouse Builder 10g Release 1 (10.1) to create the new Runtime Repository and the Runtime Access User.
Make sure the names and tablespaces you specify for your new Runtime Repository and Runtime Access user match the the names and tablespaces from your previous Oracle Database instance. Both default and temporary tablespaces must match the previous version.
In your Oracle Database 10g, connect as a SYS user to SQL*Plus to create each Target Schema and grant privileges to it.
Make sure to assign to each new schema the same name, the same default data tablespace, and the same temporary tablespace as in the previous version of your Warehouse Builder Target Schemas.
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
@NewOWB_ORACLE_HOME\owb\rtasst\warehouse_system_rights.sql
@NewOWB_ORACLE_HOME\owb\rtasst\xmltk_grant.sql
In your Oracle Database 10g, connect to SQL*Plus as a the Warehouse Builder Runtime Repository user and grant privilege on WB_RT_MAPAUDIT to each of the Target Schema users.
Use the following command in SQL*PLus:
grant execute on WB_RT_MAPAUDIT to OldOWBTargetSchemaUserName;
Complete this section if you had external directories in your previous Warehouse Builder environment.
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. The Partial Database Export/Import does not automatically move these references that reside in your current Oracle Database to your new Oracle Database instance. You must move them yourself by following the procedure in this section. The physical element of external directories is addressed later in this chapter, in Chapter3.
If you had external tables in your Warehouse Builder 9.0.4.x or 9.2.0.x environment, follow these instructions to migrate references to external directories to your new instance of Oracle Database:
To migrate the external directories for each of your Target Schema users to the new instance of Oracle Database 10g:
Locate OWB_ORACLE_HOME\owb\mig\gen_ext_dirs.sql and copy the file to a temporary location on the computer hosting your prior version of Oracle Database.
In SQL*Plus, connect as each of the Warehouse Builder Target Schema users, and run TEMP\gen_ext_dirs.sql.
Locate the ext_dirs.sql file generated in the SQL*Plus default directory (typically, this default directory is ORACLE_HOME\bin).
Transfer the ext_dirs.sql file to a temporary location on the computer hosting Oracle Database 10g.
In SQL*Plus, connect as each of your Warehouse Builder 10g Release 1 (10.1) Target Schema users, and execute ext_dirs.sql.
Use Oracle Import to import the Target Schema files into the new user you created.
To import a Target Schema:
Use Oracle Import to import the Target Schema DMP file you exported from your prior version of Warehouse Builder into the new Target Schema user you created in Chapter3. Enter the following command:
imp OldOWBTargetUserName/OldOWBTargetUserPassword@New_DBTNSConnection FILE=OldOWBTarget.dmp LOG=NewOWBTarget.log
OldOWBTargetUser stands for your Warehouse Builder Target Schema user from your prior 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 your import command.
Proceed with the rest of the steps 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 with the rest of the steps.
Repeat these instructions for each Target Schema you are importing.
Create a full database backup before you begin. Additionally, create metadata export (MDL) files for all your Warehouse Builder projects. Keep these backups until you have completed and tested the entire upgrade process.
The steps you follow depend on your existing version of Warehouse Builder:
Upgrading Design Metadata from Warehouse Builder 9.0.3.x or Earlier
Upgrading Design Metadata from Warehouse Builder 9.0.4.x or 9.2.x
Follow these instructions if you are upgrading from Warehouse Builder 9.0.3 or earlier, regardless of whether you have upgraded your Oracle Database. You must export your design metadata from your prior version of Warehouse Builder into an MDL file, then use your new version of Warehouse Builder to create a new Design Repository and import the metadata into it.
Export each project or collection you want to migrate to Metadata Loader (MDL) files. For more information on exporting metadata, see the Oracle Warehouse Builder User's Guide.
Note:
To upgrade, you must export and import your metadata using the Metadata Loader (MDL). 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 you want to export.
From the Project menu, choose Export Metadata.
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.
Create a new Warehouse Builder Design Repository, following the instructions in Chapter2, "Install the Design Repository Using the Repository Assistant".
After having installed the new software, you must import and upgrade your design metadata into the new version of Warehouse Builder. 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 console, select the Project menu, Metadata Import, and File.
Locate the path and file name to the exported data from your former repository. Select Import.
If the file is from the current version of Warehouse Builder, the Metadata Import Progress panel displays. This dialog displays the object types and the number of each type that were imported or skipped. For a detailed view of the import process, click View Log File.
If Warehouse Builder detects that the file is from a prior version of Warehouse Builder, the Metadata Upgrade Confirmation dialog displays. In this case, Warehouse Builder automatically upgrades the MDL file to the current version and then imports it.
Click OK to automatically upgrade the file to the current version and import it into Warehouse Builder. The Metadata Loader Upgrade Utility dialog displays for you to enter a file and a log name.
Migrated File Name: Specify the path and name of the new, upgraded MDL file. Use the Browse button to specify the destination of the file.
Log File: Specify the path and name of the log that MDL creates during the upgrade process. Use the Browse button to specify the destination of the file.
Click OK to continue the upgrade and import.
You can click Cancel to stop the upgrade and import of the file. You can upgrade the file manually by using the MDL File Upgrade utility. For more information, refer to Appendix D, "Upgrading Metadata with the MDL File Upgrade Utility".
Note:
You must import the metadata using Universal Identifier as your Match by option.If you are upgrading from Oracle Warehouse Builder Release 9.0.4.x or 9.2.x to the current release, you can upgrade your Oracle Database if you have decided to do so. Note that Oracle highly recommends upgrading to Oracle Database 10g if you upgrade to Warehouse Builder 10g Release 1 (10.1).
Regardless of whether you are upgrading Oracle Database, you must now upgrade your design metadata in one of two ways:
Automatic Upgrade Scripts: You can upgrade your design metadata by running one of the scripts included with this release of Warehouse Builder, as instructed in Chapter3.
Metadata Export and Import: Instead of a scripted upgrade, you can choose to import and export the design metadata as described in Chapter3 for older versions of Warehouse Builder. With this method, you export your design metadata from your prior version of Warehouse Builder into an MDL file, then use your new version of Warehouse Builder to create a new Design Repository and import the metadata into it.
To upgrade your Warehouse Builder 9.0.4.x or 9.2.x design metadata:
Run the automatic upgrade script. The script you use depends on the version of Warehouse Builder from which you are upgrading.
If you are upgrading from Warehouse Builder 9.0.4.x, run the following script:
For Windows, navigate to OWB_ORACLE_HOME\owb\bin\win32 and run DTupg904to10g.bat.
For UNIX, navigate to OWB_ORACLE_HOME/owb/bin/unix and run DTupg904to10g.sh.
If you are upgrading from Warehouse Builder 9.2.x, run the following script:
For Windows, navigate to OWB_ORACLE_HOME\owb\bin\win32 and run DTupg92to10g.bat.
For UNIX, navigate to OWB_ORACLE_HOME/owb/bin/unix and run DTupg92to10g.sh.
The script prompts you for seven parameters describing your new Warehouse Builder 10g Release 1 (10.1) environment.
Host Name, Port Number, and Service Name: If you are not migrating to a new Oracle Database instance, the first three parameters are the connect string to your current Design Repository. If you are migrating, enter the connection information to your newly created Design Repository.
SYS User Name and Password: Your SYS account information.
User Name and Password: These last two parameters are for your new Design Repository.
Tablespace for Indexes: If you are upgrading from Warehouse Builder 9.0.4.x, the script prompts you for the name of the tablespace for indexes.
Examine the log file for any errors.
For Windows, examine OWB_ORACLE_HOME\owb\reposasst\upg\LOG.TXT.
For UNIX, examine OWB_ORACLE_HOME/owb/reposasst/upg/LOG.TXT.
In this step you upgrade your runtime data so that your new Runtime Repository shows the correct status, history, location details, and version numbers for deployed and executed objects.
The steps you follow depend on your existing version of Warehouse Builder:
Upgrading Runtime Data from Warehouse Builder 9.0.3.x or Earlier
Upgrading Runtime Data from Warehouse Builder 9.0.4.x or 9.2.x
If you are upgrading from Warehouse Builder 9.0.3.x or earlier, you must migrate data from your old Target Schemas or to the Target Schemas of the current release.
First, follow the instructions in Chapter2 to install a Runtime Repository and one or more Target Schemas. Then, choose from three methods to migrate data from your old runtime environment to the new Target Schemas you created:
Option 1. Regenerate Database Objects Using Warehouse Builder
Option 2. Export and Import Database Objects in the Oracle Database Server
Option 3. Create Synonyms for Original Objects in the New Target Schema
Once you have selected a method, repeat that procedure for each Target Schema you are migrating.
In this method, consider using the Warehouse Builder interface for a one-time migration. This method is recommended for beginning and intermediate users of Warehouse Builder, if your old Warehouse Builder environment does not stray from the recommended setup.
Table 3-1 describes the advantages and drawbacks of this method.
Table 3-1 Advantages and Drawbacks of Migrating in the Warehouse Builder Interface
| Outcome | Description |
|---|---|
|
Advantages |
|
|
Drawbacks |
|
To migrate data using the Warehouse Builder interface:
In the Deployment Manager of your upgraded Warehouse Builder client, register the new locations for your database objects.
One at a time, select each Target module and click Default Action. Because the objects are new to this version, the default action is creation.
Click Generate/Deploy. You are ready to migrate your data following Steps 4 through 7.
Create a Source module pointing to your old Target Schema.
Create simple mappings that extract from your old Target Schema as a source and load to your new Target Schema objects.
Deploy these migration mappings and run them only once. Test to ensure that a 1-to-1 migration occurred.
When you are satisfied with the results, delete the one-time migration mappings and the Source modules you created that point to the old Target Schema.
For more instructions on registering locations, creating source and target modules, and creating and executing mappings, refer to the Oracle Warehouse Builder User's Guide.
This method is recommended for advanced users of Warehouse Builder. You perform the data migration in the back end by exporting and importing the appropriate Warehouse Builder database objects.
Table 3-2 describes the advantages and drawbacks of this method.
Table 3-2 Advantages and Drawbacks of Migrating Using Oracle Database
| Outcome | Description |
|---|---|
|
Advantages |
|
|
Drawbacks |
|
To migrate by exporting and importing database objects in the back end:
Follow instructions in the Oracle Database Server documentation to export and import database objects.
Make sure that you are only working with database objects that you created, and not with Warehouse Builder objects generated by Warehouse Builder. To this end, consider migrating the data and then regenerating the constraints, indexes, dimensions, and other objects you can generate in the database.
Examples of objects you should not export or import follow:
Do not export or import runtime audit tables or packages. If your old Warehouse Builder environment does not stray from the standard, then the tables and packages related to audit data are in your Runtime Schema.
Do not export or import objects whose names begin with WB. These objects are generated by Warehouse Builder.
After the data migration, regenerate all mappings.
This method is a shortcut in which you create synonyms pointing to your original database objects in your new Target Schema. Instead of actual data, your new Target Schema will contain only the regenerated mappings and the pointers to the database objects containing the data.
Table 3-3 describes the advantages and drawbacks of this method.
Table 3-3 Advantages and Drawbacks of Migrating by Using Synonyms
| Outcome | Description |
|---|---|
|
Advantages |
|
|
Drawbacks |
|
To migrate by creating synonyms to existing objects:
Follow instructions in the Oracle Database Server documentation to create synonyms in your new Target Schema that point to existing database objects in your old environment.
Make sure that you are only working with database objects that you created yourself, and not with Warehouse Builder objects generated by Warehouse Builder. To this end, simply create synonyms for the data objects and then regenerate the mappings.
For example, do not create synonyms for audit tables or packages. If your old Warehouse Builder environment does not stray from the standard, then the tables and packages related to audit data are in your Runtime Schema.
To upgrade your runtime data from Warehouse Builder 9.0.4.x or 9.2.x, the script you run depends on whether you are changing the database instance for your new Runtime Repository and Target Schemas.
The steps you complete to upgrade your audit data depend on whether you are keeping the same database instance, whether you are upgrading to Oracle Database 10g, and on the version of Oracle Database from which you upgraded.
To upgrade audit data from Warehouse Builder 9.0.4.x or 9.2.x:
Run the automatic upgrade script. The script you run depends on whether you are keeping the same database connection (that is, the host:port:servicename does not change) or changing to a new database instance or computer.
If you are keeping the same database instance, OR if you used either the the Full Database Export/Import (Chapter3) or the Database Migration Utility (Chapter3) to migrate to Oracle Database 10g, run this upgrade script:
For Windows, navigate to OWB_ORACLE_HOME\owb\bin\win32 and run RT_upgrade_to_10_1.bat.
For UNIX, navigate to OWB_ORACLE_HOME/owb/bin/unix and run RT_upgrade_to_10_1.sh.
The RT_upgrade_to_10_1 script prompts you for several parameters: the database connection string for your Runtime Repository schema (host:port:servicename) and the SYS User Name and Password for the Oracle Database instance. You must then choose which Runtime Repository you want to upgrade from a list of your existing Runtime Repositories.
If you are changing the database instance or the computer hosting the database, AND if you migrated your runtime environment as described in Chapter3, "Migrating the Runtime Environment", then run the migration script:
For Windows, navigate to OWB_ORACLE_HOME\owb\bin\win32 and run RT_migrate_to_10_1.bat.
For UNIX, navigate to OWB_ORACLE_HOME/owb/bin/unix and run RT_migrate_to_10_1.sh.
The RT_migrate_to_10_1 script prompts you for several parameters: the User Name and Password of your original Runtime Repository schema, the database connection string for your original Runtime Repository (in the form of host:port:servicename), the User Name and Password for your new Runtime Repository schema (whose values should match the original Runtime Repository), and the database connection string for the new Runtime Repository (also in the form of host:port:servicename).
Additionally, as it runs, the script prompts you for SYS User Names and Passwords for the Oracle Database instances for any Target Schemas and Oracle Workflows being upgraded.
Skip this step if you are not upgrading to Oracle Database 10g.
If you upgraded to Oracle Database 10g, connect to SQL*Plus as the Design Repository user and run the following script to update your location definitions:
OWB_ORACLE_HOME\owb\repoasst\upg\dt_upgrade_locs_RUNTIME_REPOSITORY_USER_NAME.sql
Examine the log file for any errors.
For Windows, examine OWB_ORACLE_HOME\owb\bin\admin\rtupgrade.log.xx
For UNIX, examine OWB_ORACLE_HOME/owb/bin/admin/rtupgrade.log.xx
Skip this step if you ran the upgrade script (RT_upgrade_to_10_1).
If you ran the migrate script (RT_migrate_to_10_1), you must now start the Warehouse Builder client and edit your Runtime Repository connections to refer to your upgraded runtime connection information.
If you upgraded from Oracle8i Release 3 (8.1.7.4) to Oracle Database 10g, you must re-register your locations in the Deployment Manager of the Warehouse Builder client.
For more information on working with Runtime Repository connections or registering locations, 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 moved your Oracle Database 10g from the computer hosting your prior version of Oracle Database to a different computer
AND
If you had flat files or external tables in your previous Warehouse Builder environment
If both of these points are true, you must copy the following objects from the computer hosting your previous instance of Oracle Database to the computer hosting your new instance:
Flat Files: Copy any flat files used by SQL*Loader from the computer hosting your previous instance of Oracle Database to the computer hosting your new instance.
External Directories: You must also copy all external directories from the computer hosting your previous instance of Oracle Database to the computer on which Oracle Database 10g resides. Make sure to recreate identical file system directories.
External directories have two elements: the logical, and the physical. Chapter3 addressed the logical element, and was only required of users who chose the Partial Database Export/Import option to move their database. In this section, you copy the physical directory structure from the computer hosting your previous instance of Oracle Database computer to the computer hosting your new instance.
If you are upgrading from Oracle Warehouse Builder Release 9.0.4.x or 9.2.x and followed the instructions in Chapter3, "Upgrading Runtime Data", you can choose to skip this step.
If you are upgrading from Oracle Warehouse Builder Release 9.0.3 or earlier, you must redeploy your mappings. With the upgraded version of Warehouse Builder, the runtime architecture has changed. To propagate these changes into your generated code, redeploy your mappings. After you have redeployed your mappings, do not use the old mappings again.
For example, redeployment ensures that your mappings refer to the correct auditing packages. Additionally, redeploying enables you to take advantage of new code generation features available in the new version of Warehouse Builder.
For instructions on deploying mappings, refer to the Oracle Warehouse Builder User's Guide. After redeploying, test your mappings to ensure that they still work.
After redeploying your 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 Warehouse Builder Release 9.0.3 or earlier, you must follow the instructions in this section.
If you are upgrading from Release 9.0.4.x or 9.2.x, you only need to follow these instructions if you migrated from an earlier release to Release 9.0.4.x or 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 your 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 your 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.
You can gradually phase out your old system once your upgrade has been tested and is working. You can perform this step in parallel with Chapter3, "Updating Mapping Configuration to Benefit from New Features".
Note:
Be selective in removing your old system if you followed Chapter3, "Option 3. Create Synonyms for Original Objects in the New Target Schema" when you upgraded your audit data. Do not remove the database objects to which the synonyms you created are pointing.To phase out your old system:
Remove the database objects you created in the back end. For more information, refer to the Oracle Database Server documentation.
Remove the old version of the Warehouse Builder software. Use the deinstallation instructions provided with the version of Warehouse Builder you are removing.
